WEBVTT

00:00:00.840 --> 00:00:03.779
The opinions expressed are those of the show

00:00:03.779 --> 00:00:08.060
hosts and may not necessarily be of any company

00:00:08.060 --> 00:00:19.719
in which the show hosts may represent. The following

00:00:19.719 --> 00:00:25.820
podcast may contain some strong language. Parental

00:00:25.820 --> 00:00:48.609
discretion is advised. Welcome to the Security

00:00:48.609 --> 00:00:54.009
Box. I'm Jared Reimer. This is program number

00:00:54.009 --> 00:01:03.630
268. Recorded on Wednesday, February 18th, 2026.

00:01:05.269 --> 00:01:11.290
Coming up, why are we changing the podcast a

00:01:11.290 --> 00:01:16.739
little bit? I .e. adding episodes. that include

00:01:16.739 --> 00:01:24.280
A, B, C, etc. Details are in our show notes,

00:01:24.379 --> 00:01:27.939
but we will go ahead and talk about this change

00:01:27.939 --> 00:01:35.739
here on today's podcast. From last Saturday,

00:01:36.120 --> 00:01:51.280
chat GPT and app recommendations. Why did I go

00:01:51.280 --> 00:02:00.099
into this conversation with the AI tool? What

00:02:00.099 --> 00:02:10.620
happened? Also, from Saturday, Terry asked me,

00:02:10.740 --> 00:02:20.080
why can't I train Gemini? To do the same thing

00:02:20.080 --> 00:02:28.659
that ChatGPT is doing already for me? This podcast's

00:02:28.659 --> 00:02:35.800
video is going to be Microsoft's backdoor into

00:02:35.800 --> 00:02:41.599
our encryption. Which I don't think made it into

00:02:41.599 --> 00:02:47.259
Podcast 267. If it did... We're just going to

00:02:47.259 --> 00:02:53.979
go ahead and rerun it. And this week's topic.

00:02:56.300 --> 00:03:02.960
Why Menvy and the JRN have never had a breach.

00:03:04.340 --> 00:03:08.960
We're not saying we're perfect. The JRN, of course,

00:03:08.960 --> 00:03:13.300
has had issues. And you can search post -mortem

00:03:13.300 --> 00:03:18.650
on the blog. but they're few and far between

00:03:18.650 --> 00:03:25.409
and probably minor issues that could be easily

00:03:25.409 --> 00:03:29.830
fixed even when deleting files that actually

00:03:29.830 --> 00:03:34.870
mean something because it ended up fixing a big

00:03:34.870 --> 00:03:42.509
problem. I hope that each and every one of you

00:03:42.509 --> 00:03:48.669
will enjoy the podcast. And I will be talking

00:03:48.669 --> 00:03:58.610
about a change in the way our podcasts are going

00:03:58.610 --> 00:04:05.710
to be. And we've got solid topics coming up.

00:04:07.650 --> 00:04:12.870
I hope that you will enjoy the podcast as we

00:04:12.870 --> 00:04:18.990
have. been bringing it to you. And please stay

00:04:18.990 --> 00:04:48.269
tuned as it is coming up next. As heard on the

00:04:48.269 --> 00:04:52.810
Kim Commando podcast and Digital Minute, as well

00:04:52.810 --> 00:04:59.389
as her national radio shows. Introducing Incogni,

00:04:59.389 --> 00:05:06.810
the personal data removal service. This service

00:05:06.810 --> 00:05:12.350
will remove your personal information from over

00:05:12.350 --> 00:05:20.120
400... data broker websites, some of which you,

00:05:20.339 --> 00:05:25.699
as an average consumer, have probably never heard

00:05:25.699 --> 00:05:30.600
of. They won't touch places like Google or Facebook

00:05:30.600 --> 00:05:35.459
because removing your information from there

00:05:35.459 --> 00:05:39.959
may delete your account, which you may not necessarily

00:05:39.959 --> 00:05:50.259
want. But, They will work with many other services

00:05:50.259 --> 00:05:57.420
and will notify you along the way. The website

00:05:57.420 --> 00:06:02.139
stipulates that you should use the information

00:06:02.139 --> 00:06:07.699
that is more likely to be out there, including

00:06:07.699 --> 00:06:15.920
your main email address and Your main phone number.

00:06:16.300 --> 00:06:20.300
All accounts must go through an email address

00:06:20.300 --> 00:06:28.000
verification process. And the service is not

00:06:28.000 --> 00:06:35.899
free. Pricing starts as little as $12 a month.

00:06:36.639 --> 00:06:40.420
And they also have a yearly option available.

00:06:41.040 --> 00:06:51.379
IN. C -O -G -N -I dot com Get your information

00:06:51.379 --> 00:06:58.879
off the internet today. Find a link to Incogni

00:06:58.879 --> 00:07:03.019
on our website at emailhostsecurity .com under

00:07:03.019 --> 00:07:23.379
our resources page. The Security Box Welcome,

00:07:23.420 --> 00:07:33.040
everybody! Welcome aboard. This is program 268

00:07:33.040 --> 00:07:50.720
of the series. It is February 18th. And, uh...

00:07:56.269 --> 00:07:59.009
We are going to go into a deep dive in a couple

00:07:59.009 --> 00:08:18.970
of items that we talked about on Saturday. And

00:08:18.970 --> 00:08:27.050
our main topic today... Why is Menvee... And

00:08:27.050 --> 00:08:39.929
the J .R .N. More secure than your multi -billion

00:08:39.929 --> 00:09:04.149
dollar company. I'll let people guess on that

00:09:04.149 --> 00:09:16.409
one. I'm not saying I'm 100 % perfect. We have

00:09:16.409 --> 00:09:19.210
had our issues, just like any other company.

00:09:22.909 --> 00:09:29.320
But we've never been breached. where our data

00:09:29.320 --> 00:09:45.940
has been pilfered. I also have been doing a little

00:09:45.940 --> 00:09:50.460
bit of research into some of the emails we've

00:09:50.460 --> 00:09:54.840
been getting that we've talked about here on

00:09:54.840 --> 00:10:01.600
TSB. I'm also going to talk about some structural

00:10:01.600 --> 00:10:13.399
changes coming to TSB that will assist us in

00:10:13.399 --> 00:10:18.379
making sure we get as much as we can out into

00:10:18.379 --> 00:10:27.740
the landscape. We also have a leftover from last

00:10:27.740 --> 00:10:31.299
podcast where I don't think it got aired and

00:10:31.299 --> 00:10:36.100
if it did it'll be repeated and it's the Microsoft

00:10:36.100 --> 00:11:07.700
thing that Mr. Espinoza had Microsoft's backdoor

00:11:07.700 --> 00:11:13.100
into our encryption. Now, I don't know if this

00:11:13.100 --> 00:11:17.559
did get played, so we're just going to play it

00:11:17.559 --> 00:11:24.559
anyway. And, of course, the show notes have the

00:11:24.559 --> 00:11:26.879
difference between what we do on throwback and

00:11:26.879 --> 00:11:37.500
what we do on this program. It's more relaxed

00:11:37.500 --> 00:11:44.639
and conversational, where TSB goes deeper, offering

00:11:44.639 --> 00:12:10.549
detailed analysis and discussion. Okay. Let's

00:12:10.549 --> 00:12:23.370
go ahead and get started by first talking about

00:12:23.370 --> 00:12:28.590
the structure of the program. Preston recently

00:12:28.590 --> 00:12:38.960
gave me 11 videos. I haven't had a chance to

00:12:38.960 --> 00:12:45.220
download them yet, but what we're going to do

00:12:45.220 --> 00:12:50.820
is we're going to start using our ABC format

00:12:50.820 --> 00:12:59.279
in between podcasts. And this will allow us to

00:12:59.279 --> 00:13:09.350
keep TSB within a reasonable time frame. While

00:13:09.350 --> 00:13:20.570
allowing us to have content. So... Well, we are

00:13:20.570 --> 00:13:35.370
going to only have one video today. We... Are

00:13:35.370 --> 00:13:42.039
going to go... and do some of these other videos

00:13:42.039 --> 00:13:45.399
in what we would call intermediate podcasts.

00:13:52.700 --> 00:14:07.460
And that's how I think we are. going to do that.

00:14:20.679 --> 00:14:28.440
You may email or iMessage tech, that's T -E -C

00:14:28.440 --> 00:14:36.960
-H at M -E -N -V -I dot org. Text or WhatsApp

00:14:36.960 --> 00:14:47.820
804 -442 -6975. Or you may call the comment line

00:14:47.820 --> 00:15:35.600
at 888 -405 -7524. So... That is where we are.

00:16:29.550 --> 00:16:36.970
So, let's go ahead and talk a little bit about

00:16:36.970 --> 00:16:41.070
what's coming up. So, on throwback Saturday night,

00:16:43.210 --> 00:16:45.769
Terry asked me an interesting question about

00:16:45.769 --> 00:16:58.850
how come I couldn't train Gemini like I did ChatGPT.

00:17:04.529 --> 00:17:09.150
And it's not that I'm against Gemini or any other

00:17:09.150 --> 00:17:34.230
model. It's that I don't really have the time.

00:17:35.690 --> 00:17:40.430
I need something that I was able to train and

00:17:40.430 --> 00:18:09.200
work with. So, that isn't really going to help

00:18:09.200 --> 00:18:16.940
me. And since the next fifth week is not until

00:18:16.940 --> 00:19:14.029
July. That's really why. But we can go into more

00:19:14.029 --> 00:19:22.529
detail. Next, what happened with my workflow?

00:19:26.490 --> 00:19:56.529
And why did it become a problem? And then, of

00:19:56.529 --> 00:20:12.789
course, our main topic. So, since I have nobody

00:20:12.789 --> 00:20:31.420
here yet on Team Talk... Let's go ahead and play

00:20:31.420 --> 00:20:47.140
one song. And then we'll get right on started.

00:20:55.660 --> 00:20:59.460
hear home free home freeze version from their

00:20:59.460 --> 00:25:31.609
single listen to the music and back. I still

00:25:31.609 --> 00:25:58.240
have nobody on the server. We push on. And by

00:25:58.240 --> 00:26:00.960
the way, we do have plenty of topics coming up.

00:26:08.559 --> 00:26:17.940
And if something breaks, we will... Get it out

00:26:17.940 --> 00:26:54.369
there. Yes, we're just having all kinds of issues

00:26:54.369 --> 00:27:00.470
right now. But it's okay. Let's push along with

00:27:00.470 --> 00:27:08.569
the program. We'll do our topic list toward the

00:27:08.569 --> 00:27:20.180
end. Let's start with... the app recommendations,

00:27:20.240 --> 00:27:26.380
because this is kind of interesting. And I think

00:27:26.380 --> 00:27:29.740
this is more of my computer issues now than anything,

00:27:29.920 --> 00:27:35.099
but I think I can get all of this to work. I

00:27:35.099 --> 00:27:40.160
asked ChatGPT about which mainstream apps were

00:27:40.160 --> 00:27:43.119
talked about within the mainstream media today.

00:27:44.619 --> 00:27:50.339
Here is what it said word for word. And there

00:27:50.339 --> 00:27:56.160
was a trivia question for throwback on what it

00:27:56.160 --> 00:27:58.819
recommended, and nobody did get it right. We're

00:27:58.819 --> 00:28:05.579
not going to do the trivia question today. But

00:28:05.579 --> 00:28:16.480
the text does have the answer. It says... You're

00:28:16.480 --> 00:28:20.240
describing technical debt exactly the way practitioners

00:28:20.240 --> 00:28:26.440
mean it. Not as a buzzword, but as accumulated

00:28:26.440 --> 00:28:31.480
friction caused by disruption. And I was really

00:28:31.480 --> 00:28:37.900
disrupted this week. Well, since my last podcast

00:28:37.900 --> 00:28:48.640
anyway. Being sick, which is what started the

00:28:48.640 --> 00:28:55.259
whole thing back on the 29th. Having to learn

00:28:55.259 --> 00:29:01.220
a new tool, me, in parentheses, and that's because

00:29:01.220 --> 00:29:08.700
I wanted to do symptom evaluation. Apps breaking,

00:29:09.079 --> 00:29:12.400
workflows collapsing, and commitments stacking

00:29:12.400 --> 00:29:17.180
up, i .e., Where's SANS? It hasn't been around

00:29:17.180 --> 00:29:25.720
in a while. That is technical debt. Preston and

00:29:25.720 --> 00:29:30.420
Terry Get It tells me you explained it clearly

00:29:30.420 --> 00:29:33.640
and credibly. Basically, and we'll get into this

00:29:33.640 --> 00:29:39.440
in a longer segment, technical debt basically

00:29:39.440 --> 00:29:43.339
means that you've gotten behind because things

00:29:43.339 --> 00:29:50.759
are broken. And you got to learn new tools. On

00:29:50.759 --> 00:29:56.619
your question about mainstream sources, what

00:29:56.619 --> 00:30:00.859
mainstream sources are recommending right now,

00:30:01.000 --> 00:30:06.779
the stuff that keeps showing up in Google slash

00:30:06.779 --> 00:30:16.549
AI lists blogs and top apps. Here's the usual

00:30:16.549 --> 00:30:28.069
lineup you'll see over and over. And this is

00:30:28.069 --> 00:30:32.849
now going to just talk about what is recommended

00:30:32.849 --> 00:30:42.839
from the mainstream. Current Pattern. These are

00:30:42.839 --> 00:30:46.960
the names that keep resurfacing regardless of

00:30:46.960 --> 00:30:53.099
actual accessibility quality. So ChatGPT understands

00:30:53.099 --> 00:31:00.319
accessibility stuff. I'm not going to say that

00:31:00.319 --> 00:31:06.259
Gemini or any other tool doesn't. But based on

00:31:06.259 --> 00:31:09.220
what I've been able to see, this is what we have.

00:31:11.240 --> 00:31:20.079
The first item is Microsoft OneNote. Still the

00:31:20.079 --> 00:31:25.559
default safe recommendation. Cross -platform,

00:31:25.559 --> 00:31:31.839
enterprise -friendly, uneven but workable with

00:31:31.839 --> 00:31:39.220
screen readers. Okay, so if you used it, I would

00:31:39.220 --> 00:31:46.920
love to hear from you. Let me know how that worked

00:31:46.920 --> 00:32:05.160
for you. I'm curious. Because how are we going

00:32:05.160 --> 00:32:33.839
to know whether it actually works? Okay. Evernote

00:32:33.839 --> 00:32:42.279
is the next item. Constantly mentioned due to

00:32:42.279 --> 00:32:48.119
brand recognition. Heavier subscription. Centric.

00:32:49.230 --> 00:32:53.569
mixed accessibility depending on platform, and

00:32:53.569 --> 00:32:59.490
update. Again, what we want to know is whether

00:32:59.490 --> 00:33:10.970
it's usable for you. I'm not going to say whether

00:33:10.970 --> 00:33:13.630
it does or doesn't because I've not used the

00:33:13.630 --> 00:33:33.230
tool. But I do want to know. Because if I don't

00:33:33.230 --> 00:33:38.789
know, how am I going to decide what works the

00:33:38.789 --> 00:33:55.140
best? Right? So... There we go. Terry actually

00:33:55.140 --> 00:34:08.079
brought this particular item up. And it is titled

00:34:08.079 --> 00:34:19.780
Notion. And Notion I actually never heard of.

00:34:23.309 --> 00:34:27.190
I may have heard of it once, but it's not familiar

00:34:27.190 --> 00:34:37.469
to me. Extremely popular in tech productivity

00:34:37.469 --> 00:34:42.670
circles. Often recommended despite significant

00:34:42.670 --> 00:34:47.110
accessibility issues and cognitive overhead.

00:34:48.190 --> 00:34:53.559
So if you used it... Let me know what you think.

00:35:00.780 --> 00:35:08.940
Google Keep. Now, this sounds pretty good to

00:35:08.940 --> 00:35:19.880
me. But, Google Keep is mainly the notes facility

00:35:19.880 --> 00:35:30.349
of Outlook. Where you get. Basically the. Notepads.

00:35:31.809 --> 00:35:37.070
That are colored. You can basically type into

00:35:37.070 --> 00:35:49.769
them. But. That's really all you can do. A lightweight.

00:35:49.869 --> 00:35:56.280
Simple. Frequently suggested because it's bundled

00:35:56.280 --> 00:36:03.780
and familiar. Not because it's robust. So it's

00:36:03.780 --> 00:36:07.920
mainly a note -taking app. I used it when I had

00:36:07.920 --> 00:36:13.679
Outlook. And people are probably asking, why

00:36:13.679 --> 00:36:29.389
didn't you just use Apple Notes? Well, Apple

00:36:29.389 --> 00:37:12.250
Notes does work. But, has some issues it cannot

00:37:12.250 --> 00:37:23.469
export as plain text so when i wanted to use

00:37:23.469 --> 00:37:30.539
it to export to chat gpt to do log analysis It's

00:37:30.539 --> 00:37:36.659
in HTML. Regularly recommended in Apple -centric

00:37:36.659 --> 00:37:41.519
spaces. Accessibility is decent, but portability

00:37:41.519 --> 00:38:00.960
and exports are limited. The next item, Obsidian.

00:38:03.539 --> 00:38:07.679
Increasingly mainstream in power user articles.

00:38:10.320 --> 00:38:15.719
File -based markdown variable. Accessibility

00:38:15.719 --> 00:38:21.199
depending on setup. It's not saying it is, and

00:38:21.199 --> 00:38:49.980
it's not saying it isn't. So, I've never used

00:38:49.980 --> 00:39:00.119
the tool. If you have, I would love to hear from

00:39:00.119 --> 00:39:45.489
you and you let me know what works for you. Now,

00:39:45.489 --> 00:39:51.789
here's the next one. GoodNotes. Another one I've

00:39:51.789 --> 00:39:55.710
heard of, but I've not used it. Almost always

00:39:55.710 --> 00:40:04.590
included in accessible lists. Even though handwriting

00:40:04.590 --> 00:40:09.329
first tools are hit or miss for blind users.

00:40:13.610 --> 00:40:23.210
I've not used it. But my question would be, if

00:40:23.210 --> 00:40:30.530
you use it, what did you think? Because it says

00:40:30.530 --> 00:40:35.409
it is a handwriting tool. And I know that us

00:40:35.409 --> 00:40:42.130
as blind people, since that's what I seem to

00:40:42.130 --> 00:41:01.739
target, is basically not worth it. I don't know

00:41:01.739 --> 00:41:08.239
if it does standard print. So that's why we're

00:41:08.239 --> 00:41:28.969
talking about it, right? The next item is otter

00:41:28.969 --> 00:41:33.230
.ai, which I've heard of and it is talked about.

00:41:36.650 --> 00:41:43.730
Shows up for transcription in the notes. Well,

00:41:43.789 --> 00:41:46.190
it shows up more for transcription in the notes,

00:41:46.269 --> 00:41:54.900
but it's routinely lumped in. What's telling

00:41:54.900 --> 00:42:04.380
and reinforces your point is that simple notes,

00:42:04.380 --> 00:42:09.199
which is the answer to the question that was

00:42:09.199 --> 00:42:16.820
out there, rarely appears in these lists anymore,

00:42:16.820 --> 00:42:25.679
despite being stable. Being fast, not crashing,

00:42:25.880 --> 00:42:32.059
not demanding constant re -authentication gymnastics,

00:42:32.440 --> 00:42:39.599
and crucially, getting out of the way. Mr. J,

00:42:39.880 --> 00:42:48.900
welcome to TSB. Yep, good to be here. I mean,

00:42:48.920 --> 00:42:51.019
at least for a bit. There's something else I'm

00:42:51.019 --> 00:42:54.400
in the middle of, so... I don't know if I'll

00:42:54.400 --> 00:42:59.260
be here for long, but... Well, we're talking

00:42:59.260 --> 00:43:03.920
app recommendations, and SimpleNote was recommended

00:43:03.920 --> 00:43:07.920
to me when Google Docs crashed and burned during

00:43:07.920 --> 00:43:14.980
actual logging. Since February 2nd, the app version

00:43:14.980 --> 00:43:21.639
of the very good productivity suite, even though...

00:43:22.000 --> 00:43:28.519
You double tap to go to the bottom of the screen.

00:43:31.800 --> 00:43:40.440
It, Mr. J, does not do it anymore. It puts your

00:43:40.440 --> 00:43:49.440
edits at the top. Okay, then. Now, there are...

00:43:51.239 --> 00:43:56.039
Some workarounds. You can set bookmarks and tell

00:43:56.039 --> 00:43:59.860
it to go to the bookmark. You can turn off voiceover,

00:44:00.139 --> 00:44:02.300
scroll to the bottom, tap at the bottom of the

00:44:02.300 --> 00:44:08.159
screen, type a letter or something. Turn on voiceover.

00:44:10.940 --> 00:44:16.320
And it'll work. Until the next time you go out

00:44:16.320 --> 00:44:22.880
of the note. And simple note, it recommended,

00:44:23.159 --> 00:44:32.099
but I found a very serious bug. That is, that

00:44:32.099 --> 00:44:37.400
when I actually do logging, and there are colons

00:44:37.400 --> 00:44:45.000
like 1030 as we do time, it crashes and burns.

00:44:48.260 --> 00:45:12.599
Okay. Exactly. I .E. technical debt. And did

00:45:12.599 --> 00:45:19.480
you know that SimpleNote, even though it's good,

00:45:19.619 --> 00:45:34.789
which is a web -slash -app universe... It's good,

00:45:34.929 --> 00:45:39.590
but you would basically have to use the web interface

00:45:39.590 --> 00:45:46.349
if you were on mobile, which is fine. It's got

00:45:46.349 --> 00:45:50.909
a link interface where you can log in by just

00:45:50.909 --> 00:45:54.369
clicking a link or entering a code or entering

00:45:54.369 --> 00:46:02.530
your credentials. But on February 12th, I had

00:46:02.530 --> 00:46:06.530
to move away from it, even though it works well.

00:46:09.570 --> 00:46:12.909
Right? I mean, it works well. I have notes in

00:46:12.909 --> 00:46:20.730
it, including our upcoming podcast list. And

00:46:20.730 --> 00:46:23.349
I've got other stuff in it, and I've been able

00:46:23.349 --> 00:46:32.340
to log onto the web and clean it up and do. Cannot

00:46:32.340 --> 00:46:35.360
use it for long -term logging. It's good for

00:46:35.360 --> 00:46:42.019
basic document stuff. As my file indicates, and

00:46:42.019 --> 00:46:44.380
you have all of these files, so if you have to

00:46:44.380 --> 00:46:46.639
leave, you can read this and then comment later.

00:46:48.639 --> 00:46:51.900
Right. That's classic invisible reliability.

00:46:53.019 --> 00:46:58.079
It doesn't generate content, hype, or economics.

00:46:58.519 --> 00:47:05.909
So AI summaries... Under rank it. Your simple

00:47:05.909 --> 00:47:10.110
note observation matters. What you notice is

00:47:10.110 --> 00:47:16.909
important and very you. Passwordless email. Magic

00:47:16.909 --> 00:47:21.809
link slash code. Log in on the web. That's great.

00:47:23.630 --> 00:47:27.369
That means you don't technically need your password.

00:47:29.900 --> 00:47:35.039
Traditional credentials in the app. Seamless

00:47:35.039 --> 00:47:41.079
recovery after closing the browser. No crash

00:47:41.079 --> 00:47:48.599
on paste, which it doesn't. No drama. That's

00:47:48.599 --> 00:47:54.000
resilience, not flash. And it directly contrasts

00:47:54.000 --> 00:47:58.739
with Google Docs. which it did. I just described

00:47:58.739 --> 00:48:02.840
that to you. And by the way, we've gone through

00:48:02.840 --> 00:48:09.360
two updates since. Discovery Tools breaking.

00:48:10.400 --> 00:48:15.440
AppleVis in NVDA. It wrote VDA, but it's supposed

00:48:15.440 --> 00:48:18.920
to be NVDA. Basically, I wanted to go search

00:48:18.920 --> 00:48:23.059
and see what the community was recommending these

00:48:23.059 --> 00:48:27.949
days. And the search button on AppleVis doesn't

00:48:27.949 --> 00:48:32.989
work anymore. At least it doesn't work on my

00:48:32.989 --> 00:48:44.909
machine. Uh -oh. Using NVDA. And the time cost

00:48:44.909 --> 00:48:50.070
of relearning workflows while already behind.

00:48:50.750 --> 00:48:54.969
I haven't even issued much of any podcasts, including

00:48:54.969 --> 00:49:08.309
SANS, since I got sick. Yeah, it's bad. So no,

00:49:08.510 --> 00:49:12.769
you weren't wrong to paste the Google list or

00:49:12.769 --> 00:49:15.809
to question my suggestion, which it recommended

00:49:15.809 --> 00:49:19.849
like Notes or one of these other apps. Actually,

00:49:19.869 --> 00:49:23.989
it recommended accessible something, rather,

00:49:24.050 --> 00:49:31.530
from the NFB, but it isn't available anymore.

00:49:34.730 --> 00:49:37.869
You were testing claims against reality, which

00:49:37.869 --> 00:49:42.369
is exactly what technical debt analysis looks

00:49:42.369 --> 00:49:48.230
like. If the trivia app Terry mentioned... Okay,

00:49:48.269 --> 00:49:55.380
so... It was Notion. So I don't need to read

00:49:55.380 --> 00:49:58.780
the rest of this. So Notion was it. And Notion

00:49:58.780 --> 00:50:08.079
really doesn't meet my needs from what it is

00:50:08.079 --> 00:50:15.980
saying. Google Docs is still good on the web.

00:50:19.119 --> 00:50:23.079
But if you ever play with it, at least with the

00:50:23.079 --> 00:50:26.139
latest versions, that's what this discussion

00:50:26.139 --> 00:50:37.340
is going on. So, I'll ask you if you've used

00:50:37.340 --> 00:50:44.719
any of these apps. Microsoft OneNote. I've heard

00:50:44.719 --> 00:50:48.300
of, but I don't think I've ever used. Evernote.

00:50:54.620 --> 00:50:59.760
Nope. Notion? Had only heard of it when you brought

00:50:59.760 --> 00:51:08.960
it up, so no. Okay, alright. Google Keep? Nope.

00:51:11.019 --> 00:51:19.929
Apple Notes? I may... I think so I may have used

00:51:19.929 --> 00:51:24.329
that I've used it and then since it's tied to

00:51:24.329 --> 00:51:32.170
my email I can grab things off the you know off

00:51:32.170 --> 00:51:34.250
the computer and do it that way but it's more

00:51:34.250 --> 00:51:47.230
work than it's worth right um obsidian nope Never

00:51:47.230 --> 00:51:58.510
heard of it. GoodNotes? Nope. And Otter .ai?

00:52:01.030 --> 00:52:04.030
No, just AppleNotes is the only one that I think

00:52:04.030 --> 00:52:14.969
I have actually used once. These are the top

00:52:14.969 --> 00:52:21.760
apps. Even though some may be blind friendly,

00:52:22.039 --> 00:52:29.840
one's handwriting, one is meant for transcription,

00:52:30.219 --> 00:52:49.360
and others may not have good accessibility. Pretty

00:52:49.360 --> 00:52:58.320
bad, huh? Yeah, no kidding. And now that SimpleNote

00:52:58.320 --> 00:53:07.460
can't be used as a reliable app for metro logging,

00:53:07.719 --> 00:53:12.840
I've been testing a new one, although I've heard

00:53:12.840 --> 00:53:23.460
of it before, called Drafts. It is an iOS and

00:53:23.460 --> 00:53:28.960
Android app. It's got an ecosystem like an app

00:53:28.960 --> 00:53:33.639
store where you can get basically templates to

00:53:33.639 --> 00:53:37.139
improve its capability like inserting dates and

00:53:37.139 --> 00:53:47.380
things of that nature. It's already passed all

00:53:47.380 --> 00:53:54.659
of the tests that I need. I .e., it works in

00:53:54.659 --> 00:53:58.500
airplane mode. I've been able to open and edit

00:53:58.500 --> 00:54:04.239
notes. Even when airplane mode, I've been able

00:54:04.239 --> 00:54:07.300
to use the colon facility as I've been normally

00:54:07.300 --> 00:54:13.159
able to do. And it just works. It's text -first.

00:54:14.059 --> 00:54:17.360
Ask questions later. It's always been that way.

00:54:26.579 --> 00:54:30.860
So, something from ChatGPT in regards to app

00:54:30.860 --> 00:54:34.079
recommendations. You can read the full file.

00:54:34.320 --> 00:54:41.079
I think you only have a 40 cell on that. Let

00:54:41.079 --> 00:54:54.369
me know if you want a 30. Alright. So, before

00:54:54.369 --> 00:55:00.070
I go into training Gemini, have you read the

00:55:00.070 --> 00:55:08.510
notes for today's main topic? Since I know you're

00:55:08.510 --> 00:55:12.690
not going to be around long. I don't believe.

00:55:13.280 --> 00:55:15.360
I have. I mean, I saw your rough thing that you

00:55:15.360 --> 00:55:22.780
emailed. Okay. But that was the extent. I did

00:55:22.780 --> 00:55:28.519
put the notes into everybody's folder yesterday.

00:55:30.000 --> 00:55:33.719
Okay. But it uses the same concept from the rough

00:55:33.719 --> 00:55:38.960
draft. So what do you think, since you know of

00:55:38.960 --> 00:55:44.840
the rough draft, Can you tell listeners about

00:55:44.840 --> 00:55:53.239
what we're doing differently than your mainstream

00:55:53.239 --> 00:55:59.360
company? Well, the main thing that I would say

00:55:59.360 --> 00:56:04.079
is that we are not collecting excess data and

00:56:04.079 --> 00:56:12.570
we are not retaining it. That is huge. Tell me

00:56:12.570 --> 00:56:18.050
more. Because, as we know, a lot of these breaches

00:56:18.050 --> 00:56:23.889
happen because these companies, many of them,

00:56:23.909 --> 00:56:27.530
and I understand at least some of the rationale,

00:56:27.750 --> 00:56:30.130
you know, oh, well, we need this for legal, et

00:56:30.130 --> 00:56:35.150
cetera, et cetera. But a lot of times, as we've

00:56:35.150 --> 00:56:41.050
seen all too often, they hang on. To this data.

00:56:41.150 --> 00:56:45.110
Months and months and months later. And so. When

00:56:45.110 --> 00:56:52.949
there's a breach. You get hit. And it's needless.

00:56:52.989 --> 00:56:57.469
Years later. Yes years later too. And it's needless

00:56:57.469 --> 00:57:00.309
too. Because you may never. Do any business with

00:57:00.309 --> 00:57:04.269
that company again. And they may. Have long since.

00:57:06.670 --> 00:57:10.900
Used your data for. what it needed to be used

00:57:10.900 --> 00:57:41.420
for. Yep. Yeah. That's pretty bad, huh? I agree.

00:57:46.400 --> 00:57:56.840
What else can you tell listeners about Well,

00:57:56.840 --> 00:58:05.960
from what I remember, we have a very straightforward

00:58:07.480 --> 00:58:15.099
privacy policy and that unfortunately is something

00:58:15.099 --> 00:58:18.320
that sets us apart it shouldn't be but it is

00:58:18.320 --> 00:58:21.179
because some of those that these major major

00:58:21.179 --> 00:58:24.960
apps and companies have are i would say borderline

00:58:24.960 --> 00:58:37.579
opaque and they're about as clear as Which is

00:58:37.579 --> 00:58:41.119
how you get away with... You notice how all the

00:58:41.119 --> 00:58:45.900
other privacy policies are boilerplate legalese?

00:58:47.300 --> 00:59:05.059
Oh, yes. How do you compare our privacy policies

00:59:09.099 --> 00:59:14.739
Different to theirs. I would... Better. More

00:59:14.739 --> 00:59:22.239
accessible in terms of understanding what is

00:59:22.239 --> 00:59:28.159
necessary, what is collected, and that's not

00:59:28.159 --> 00:59:34.159
much. And that we don't have a mechanism to slip

00:59:34.159 --> 00:59:37.699
in all kinds of really shady tracking and...

00:59:40.059 --> 00:59:55.920
Other questionable material. Okay. And we don't

00:59:55.920 --> 01:00:02.679
allow for that. Nope. And if something's violated

01:00:02.679 --> 01:00:20.179
and I'm told about it, out you go. Now tell me,

01:00:20.239 --> 01:00:26.920
have you used Gemini? And what are your thoughts

01:00:26.920 --> 01:00:34.760
on it? I have not. I've certainly heard a tremendous

01:00:34.760 --> 01:00:45.360
amount about Gemini. Some good, some... Oh. Here

01:00:45.360 --> 01:00:51.800
comes Preston. Go ahead. Yeah, so I've heard

01:00:51.800 --> 01:00:56.179
a lot about it, but I've never actually used

01:00:56.179 --> 01:00:59.579
it. Like I said, yeah, it's mixed. I've heard

01:00:59.579 --> 01:01:03.980
some great things about it. I know that, I think

01:01:03.980 --> 01:01:08.579
it was, who was it? Nuts .com announced that

01:01:08.579 --> 01:01:16.139
Gemini was helping them, if I'm remembering this

01:01:16.139 --> 01:01:19.230
correctly, in tracking down potential suppliers.

01:01:23.409 --> 01:01:26.630
Well, when you get to that file, because you

01:01:26.630 --> 01:01:30.610
said you were here for a limited time, I'd be

01:01:30.610 --> 01:01:34.849
interested to hear what you think of this. It's

01:01:34.849 --> 01:01:40.190
called Training Gemini. It is only available

01:01:40.190 --> 01:01:48.280
as a 40 cell for you. Mm -hmm. The show notes

01:01:48.280 --> 01:01:51.300
are in 30 cell, but the rest of this is in 40.

01:01:53.460 --> 01:02:06.019
Sorry about that. That's okay. But Terry had

01:02:06.019 --> 01:02:10.400
some very interesting thoughts. And when we go

01:02:10.400 --> 01:02:15.480
through this, some of this will make sense. So

01:02:15.480 --> 01:02:18.610
if you listen... I do have text messaging available,

01:02:18.909 --> 01:02:26.250
and you can comment if you wish. Mr. G, welcome

01:02:26.250 --> 01:02:33.309
to TSB. Hello, Jared. I'm here. I'm at your service.

01:02:34.789 --> 01:02:42.190
I guess you are. Actually, so I do have some

01:02:42.190 --> 01:02:45.750
downtime, but I do have a support broker meeting.

01:02:46.329 --> 01:02:50.969
at 4, so if you can get my closing file ready,

01:02:51.190 --> 01:02:56.170
that would be great. I have it. Thank you. So

01:02:56.170 --> 01:03:01.429
I have been listening, and definitely I do have

01:03:01.429 --> 01:03:02.869
several comments. I'm actually going to make

01:03:02.869 --> 01:03:07.630
them live. Go ahead. So for the app recommendations,

01:03:08.309 --> 01:03:12.309
definitely a broad list, but as far as accessibility

01:03:12.309 --> 01:03:19.460
goes, we are kind of SOL. So I understand why

01:03:19.460 --> 01:03:25.260
the structure you're making for logging is what

01:03:25.260 --> 01:03:29.119
you're making with drafts. I don't have a choice.

01:03:29.219 --> 01:03:33.820
I could use SimpleNote and then rewrite all of

01:03:33.820 --> 01:03:39.900
the timestamps. Because I would basically have

01:03:39.900 --> 01:03:42.699
to take the colon out just to get it to work.

01:03:43.949 --> 01:03:47.610
But that's counterintuitive. And on Thursday,

01:03:47.809 --> 01:03:54.989
I had three out of six failures. Yeah, when you

01:03:54.989 --> 01:03:59.610
told me that in your communication, I was literally

01:03:59.610 --> 01:04:02.909
about to, I don't know, jump out of my chair.

01:04:04.469 --> 01:04:09.250
Literally. And it took me half the afternoon

01:04:09.250 --> 01:04:12.210
to redo my logs because of what Google did to

01:04:12.210 --> 01:04:18.920
me. That's very ridiculous. And I've been using

01:04:18.920 --> 01:04:34.980
that for years. Many years. That's just blah.

01:04:35.539 --> 01:05:03.590
Wow. In simple notes, colon bug was just... Yeah,

01:05:03.590 --> 01:05:06.150
that's totally unfortunate. I could not agree

01:05:06.150 --> 01:05:11.670
with the panel more about this. And Nick said

01:05:11.670 --> 01:05:14.610
he hasn't even heard of most of these mainstream

01:05:14.610 --> 01:05:19.710
apps. Yeah, same here. I have heard of some,

01:05:19.829 --> 01:05:24.130
not all. I mean, Apple Notes, I do use a lot

01:05:24.130 --> 01:05:28.869
for my grocery list. And, you know, I've been

01:05:28.869 --> 01:05:30.670
using for my new apartment list that I'm working

01:05:30.670 --> 01:05:37.690
on. And I do know how to, you know, share with...

01:05:39.000 --> 01:05:42.460
Collaborative family and stuff. And for Otter.

01:05:42.519 --> 01:05:46.820
I have used that for. Mostly Zoom meetings. Teams

01:05:46.820 --> 01:05:50.760
a little bit. But mostly Zoom stuff. It gives

01:05:50.760 --> 01:05:54.219
good summaries. I want to look back on. And.

01:05:55.300 --> 01:06:00.119
I know Zoom's. AI companion tool. Which unfortunately.

01:06:00.940 --> 01:06:07.460
You have to. Purchase that. But. That's a good

01:06:07.460 --> 01:06:16.639
tool. As well. Okay. So I think it's about. Portability.

01:06:17.179 --> 01:06:22.780
And what you're willing to. Sacrifice. To get

01:06:22.780 --> 01:06:31.360
more productivity done. Yeah. And. As far as

01:06:31.360 --> 01:06:37.750
Gemini goes. I have. I don't use it. you know,

01:06:37.789 --> 01:06:43.550
obviously a lot like Jerry was trying to, but

01:06:43.550 --> 01:06:51.670
I have, I have it read me like email summarizations.

01:06:52.130 --> 01:06:56.730
So I do know how to, you know, give it good and

01:06:56.730 --> 01:06:59.570
bad ratings, but I haven't really like interacted

01:06:59.570 --> 01:07:02.130
with it more when I have played around with it.

01:07:13.449 --> 01:07:17.610
But, you know, hearing Terry's story on the other

01:07:17.610 --> 01:07:20.789
program over the weekend that we contribute here,

01:07:20.869 --> 01:07:23.630
you know, he was about to have an argument and

01:07:23.630 --> 01:07:26.210
he was about to uninstall the app and such and

01:07:26.210 --> 01:07:30.550
such. I think that's when you know that a company

01:07:30.550 --> 01:07:37.400
doesn't really give a damn about its product.

01:07:44.280 --> 01:07:48.840
No kidding, right? I'm being blunt about it,

01:07:48.880 --> 01:08:02.699
but it's the unfortunate truth. And, yeah, I

01:08:02.699 --> 01:08:09.809
had a Nick On my speaker, we were talking about

01:08:09.809 --> 01:08:13.190
the impending topic coming up. And definitely,

01:08:13.329 --> 01:08:17.470
you know, I definitely agree. I've read the notes

01:08:17.470 --> 01:08:21.710
and the rough draft we did for it. And we do

01:08:21.710 --> 01:08:25.729
have a strict privacy policy. But what I like

01:08:25.729 --> 01:08:30.270
about what we do is, you know, we obviously don't

01:08:30.270 --> 01:08:34.229
sell people's data out. We don't spam their content.

01:08:35.800 --> 01:08:42.260
If we want to do business with them, we communicate

01:08:42.260 --> 01:08:46.680
straight to them. And you don't see a lot of

01:08:46.680 --> 01:08:59.100
companies do that nowadays. And by the way, I've

01:08:59.100 --> 01:09:03.100
been getting more, and I don't know if Nick is

01:09:03.100 --> 01:09:07.380
still listening, but I've been getting more of

01:09:07.380 --> 01:09:16.159
these re -emails. Oh, no. More of them? Here's

01:09:16.159 --> 01:09:22.840
what's interesting about them. Because I was

01:09:22.840 --> 01:09:29.659
asking ChatGPT about this. These are actually

01:09:29.659 --> 01:09:39.130
spam campaigns. ran at long -living domains like

01:09:39.130 --> 01:09:55.289
mine, which they just send generic emails which

01:09:55.289 --> 01:10:06.500
have been confirmed to come from Outlook or Gmail

01:10:06.500 --> 01:10:11.319
because they use their exact servers to send

01:10:11.319 --> 01:10:15.920
these out. Yep. I've been checking the addresses

01:10:15.920 --> 01:10:22.539
every time you forward me something. They never

01:10:22.539 --> 01:10:27.960
look at your website, not directly. It's not

01:10:27.960 --> 01:10:35.050
technically at you. But by generating a reply,

01:10:35.470 --> 01:10:40.869
they could in theory send you a report if they

01:10:40.869 --> 01:10:46.529
want. Or they could try and upsell you a bunch

01:10:46.529 --> 01:10:53.949
of stuff that you may or may not need. And remember,

01:10:54.229 --> 01:10:59.390
some of these emails are like probably black

01:10:59.390 --> 01:11:07.609
hat. SEL tactics which could get you banned from

01:11:07.609 --> 01:11:14.850
Google and being indexed yeah that does not sound

01:11:14.850 --> 01:11:22.529
good at all so and the fact that they're sending

01:11:22.529 --> 01:11:26.640
them early in the morning is a signal where Kim

01:11:26.640 --> 01:11:29.479
Commando said, if you want people to read your

01:11:29.479 --> 01:11:32.680
email, send it early in the morning. Well, that's

01:11:32.680 --> 01:11:36.920
exactly what the spammers have now gotten to.

01:11:37.340 --> 01:11:40.460
And the fact that my domain has been open since

01:11:40.460 --> 01:11:51.340
2008, and I got three of those today alone, signals

01:11:52.029 --> 01:11:55.289
And not only that, but my address has been breached.

01:11:55.329 --> 01:11:58.409
So once you're breached, your address is basically

01:11:58.409 --> 01:12:04.369
in the open and it can be resold. So changing

01:12:04.369 --> 01:12:08.090
your email every so often, like Steve Gibson

01:12:08.090 --> 01:12:11.909
does, is a good practice, but not real practical

01:12:11.909 --> 01:12:18.329
when you're basically running business. Yeah.

01:12:18.529 --> 01:12:23.020
And you need to answer the public. Steve has

01:12:23.020 --> 01:12:26.319
people that does that, so he can basically get

01:12:26.319 --> 01:12:34.899
away with changing his address every year. Email

01:12:34.899 --> 01:12:39.060
key verification is what it calls it. And I do

01:12:39.060 --> 01:12:54.060
have two scam segments coming up. which will

01:12:54.060 --> 01:12:58.199
be actually three. And once I get them recorded,

01:12:58.460 --> 01:13:06.100
you at Throwback will get one large segment where

01:13:06.100 --> 01:13:15.359
TSB will get two. But yeah, this is... And we've

01:13:15.359 --> 01:13:21.479
got a bunch of topics coming. Yep, I'm working

01:13:21.479 --> 01:13:27.579
on more. videos from our contributor I know you

01:13:27.579 --> 01:13:37.220
sent me 11 I know aren't you proud I haven't

01:13:37.220 --> 01:13:41.060
even gotten a chance to download them yet oh

01:13:41.060 --> 01:13:45.199
well that's okay I'm just trying to add more

01:13:45.199 --> 01:13:50.460
to our plate that's all Well, that's why we're

01:13:50.460 --> 01:13:55.300
going to have the ABC podcast so that our podcasts

01:13:55.300 --> 01:14:01.819
don't go, you know, 5, 10, 15 hours long. Right.

01:14:09.180 --> 01:14:14.399
And, yep, I think that's a good idea. We will

01:14:14.399 --> 01:15:26.449
do that indeed. So... Yeah. This is, uh... Interesting.

01:15:26.449 --> 01:15:32.409
Very. I mean, it's unfortunate, but here we are.

01:15:33.470 --> 01:15:39.710
I don't know what else to say, but it's just

01:15:39.710 --> 01:16:04.960
total crazy. Before we get into our next topic

01:16:04.960 --> 01:16:11.920
talking about Gemini, does anybody have anything

01:16:11.920 --> 01:16:15.779
that they've seen from the blog? I do have a

01:16:15.779 --> 01:16:20.279
KNX article I'm going to blog continuing about

01:16:20.279 --> 01:16:33.350
the whole ordeal of the... Folks over at the

01:16:33.350 --> 01:16:38.949
social media companies and what's going on over

01:16:38.949 --> 01:16:42.670
there. Right. That was actually what I wanted.

01:16:44.729 --> 01:16:47.489
Right. I mean, that was one of the things that

01:16:47.489 --> 01:16:51.829
caught my eye. And then Sean has been chronicling

01:16:51.829 --> 01:16:57.090
Microsoft's, you know, up and down. You know,

01:16:57.090 --> 01:16:59.760
oh, they're... Maybe they're listening. Oh, well,

01:16:59.819 --> 01:17:02.199
maybe they're not. And, you know, the fact, you

01:17:02.199 --> 01:17:05.479
know, the AI, for example, and, you know, his

01:17:05.479 --> 01:17:08.460
opinions on that have been, I think, pretty valid.

01:17:10.779 --> 01:17:19.619
Okay. Yeah, totally. That's been a strong suit

01:17:19.619 --> 01:17:26.560
of updates, and I've been reading all his stuff.

01:17:27.880 --> 01:17:32.880
So I feel that that's good because I've been

01:17:32.880 --> 01:17:45.380
using my 111 going on Four five almost six months

01:17:45.380 --> 01:17:53.020
March I Haven't any big issue with this so far

01:18:00.199 --> 01:18:04.640
which I know better not to click on that. Yeah.

01:18:05.180 --> 01:18:07.560
Well, I'm more concerned about the update path

01:18:07.560 --> 01:18:21.340
because we know that breaks. Yeah. I don't believe

01:18:21.340 --> 01:18:35.090
I have bad update paths to report. be careful

01:18:35.090 --> 01:18:44.710
with that. And I'll be entering the monitor as

01:18:44.710 --> 01:18:57.409
a child, too. That gets underway. Well, then

01:18:57.409 --> 01:19:00.390
I'll break for the Microsoft video, and when

01:19:00.390 --> 01:19:06.180
we come back, we're going to do Gemini. Alrighty.

01:19:07.260 --> 01:19:11.340
That's fair to me. The security box will continue

01:19:11.340 --> 01:19:16.279
in just a moment across the Jared Reimer Radio

01:19:16.279 --> 01:19:22.659
Network. If you're using BitLocker, you're not

01:19:22.659 --> 01:19:24.899
nearly as secure as you think. Hey, everybody.

01:19:25.039 --> 01:19:27.300
Nick Espinosa, your chief security fanatic here.

01:19:27.420 --> 01:19:29.760
Don't forget to subscribe. And today, we are

01:19:29.760 --> 01:19:32.880
talking about Microsoft's backdoor into the encryption.

01:19:33.479 --> 01:19:35.399
that millions and millions and millions of Windows

01:19:35.399 --> 01:19:37.579
computers are running. Now, Thomas Brewster of

01:19:37.579 --> 01:19:39.859
Forbes had a great write -up on this, as did

01:19:39.859 --> 01:19:41.479
some of the others, but I'm cribbing from him.

01:19:41.539 --> 01:19:43.340
Full disclosure, I also published through Forbes.

01:19:43.439 --> 01:19:46.100
But here's what's going on. Early last year,

01:19:46.159 --> 01:19:47.939
if you didn't know, and you probably didn't,

01:19:47.939 --> 01:19:50.949
the FBI in the United States... served Microsoft

01:19:50.949 --> 01:19:53.770
with a search warrant asking essentially for

01:19:53.770 --> 01:19:56.470
Microsoft to provide recovery keys to unlock

01:19:56.470 --> 01:19:59.550
encrypted data stored on three laptops. Now,

01:19:59.550 --> 01:20:02.329
federal investigators in Guam believe that the

01:20:02.329 --> 01:20:05.390
devices would basically have evidence that would

01:20:05.390 --> 01:20:07.590
help them prove that individuals handling the

01:20:07.590 --> 01:20:09.850
island's COVID unemployment assistance program

01:20:09.850 --> 01:20:13.329
were basically stealing funds, fraud, all that

01:20:13.329 --> 01:20:16.590
kind of fun stuff. The data was protected with

01:20:16.590 --> 01:20:18.890
BitLocker, as I mentioned right out of the gate.

01:20:18.989 --> 01:20:20.789
And that software, if you don't know what it

01:20:20.789 --> 01:20:23.289
is, that automatically essentially is enabled

01:20:23.289 --> 01:20:26.449
now on many of the newer versions of Windows,

01:20:26.670 --> 01:20:29.189
Windows 11. Windows 10 did not have it enabled

01:20:29.189 --> 01:20:31.609
by default initially. And essentially, it's there

01:20:31.609 --> 01:20:34.170
to encrypt the drive to safeguard your data.

01:20:34.390 --> 01:20:36.149
If you don't know what encryption is, basically,

01:20:36.149 --> 01:20:38.189
it scrambles it. And if you don't have the unlock

01:20:38.189 --> 01:20:40.829
code, you basically can't see the data. That's

01:20:40.829 --> 01:20:43.789
how essentially encryption works. It's possible

01:20:43.789 --> 01:20:46.890
for users to store those keys, those passwords

01:20:46.890 --> 01:20:49.529
to that encryption on basically a device they

01:20:49.529 --> 01:20:52.569
own. But Microsoft recommends, and many people

01:20:52.569 --> 01:20:55.710
do, that you store your BitLocker passwords or

01:20:55.710 --> 01:20:58.850
your keys. essentially on its servers in the

01:20:58.850 --> 01:21:00.529
Microsoft Cloud. You have a Microsoft account,

01:21:00.789 --> 01:21:03.569
you're storing it there. And so while that means

01:21:03.569 --> 01:21:05.869
basically that, you know, if for whatever reason

01:21:05.869 --> 01:21:08.369
you forget your password, or if you have repeated

01:21:08.369 --> 01:21:10.930
failed attempts that locks the device, you can

01:21:10.930 --> 01:21:13.409
get into the cloud to essentially push and unlock

01:21:13.409 --> 01:21:16.050
as you're validating essentially your identity

01:21:16.050 --> 01:21:19.850
into your own account. But it also essentially

01:21:19.850 --> 01:21:23.270
makes your keys, meaning unscrambling and unlocking

01:21:23.270 --> 01:21:26.029
your data, it makes it vulnerable to law enforcement.

01:21:26.119 --> 01:21:28.699
subpoenas and warrants. Microsoft has access

01:21:28.699 --> 01:21:30.819
to the back end of their cloud. And so anything

01:21:30.819 --> 01:21:33.760
you're storing there, not just BitLocker keys,

01:21:33.920 --> 01:21:36.760
but your email, your files, everything, they

01:21:36.760 --> 01:21:40.380
have access to this. Now, in the Guam case, essentially,

01:21:40.439 --> 01:21:42.840
they handed over these encryption keys to investigators

01:21:42.840 --> 01:21:45.619
who were able to unlock these laptops. Microsoft

01:21:45.619 --> 01:21:49.000
also confirmed to Forbes and many other publications

01:21:49.000 --> 01:21:52.100
that it does indeed provide BitLocker recovery

01:21:52.100 --> 01:21:56.300
keys if it receives a valid legal order. And

01:21:56.300 --> 01:21:58.159
that's interesting because what constitutes a

01:21:58.159 --> 01:22:00.380
valid legal order depends on country, depends

01:22:00.380 --> 01:22:03.180
on the type of government that the country has.

01:22:03.239 --> 01:22:05.420
If you're being run by a dictatorship or something

01:22:05.420 --> 01:22:07.659
and they have a warrant, is Microsoft honoring

01:22:07.659 --> 01:22:10.680
that? Like these are serious questions here.

01:22:10.760 --> 01:22:13.340
So according to Microsoft spokesperson Charles

01:22:13.340 --> 01:22:17.220
Chamberlain, quote. Well, while key recovery

01:22:17.220 --> 01:22:19.659
offers convenience, it also carries a risk of

01:22:19.659 --> 01:22:21.960
unwanted access. So Microsoft believes customers

01:22:21.960 --> 01:22:25.119
are in the best position to decide how to manage

01:22:25.119 --> 01:22:27.500
their keys, end quote. And I wouldn't be storing

01:22:27.500 --> 01:22:29.920
it at the cloud if I were you. Now, he said the

01:22:29.920 --> 01:22:32.460
company receives about 20 requests for BitLocker

01:22:32.460 --> 01:22:35.880
unlocks or keys per year. And in many cases,

01:22:35.960 --> 01:22:38.939
the user has not stored their key in the cloud,

01:22:39.159 --> 01:22:41.579
essentially saying, or rather Microsoft saying,

01:22:41.659 --> 01:22:44.060
it's impossible for then Microsoft to assist.

01:22:44.180 --> 01:22:45.760
In other words, if you're not storing. the key

01:22:45.760 --> 01:22:47.600
in their cloud, and quite frankly, there are

01:22:47.600 --> 01:22:50.000
other ways to do that, then they can't help.

01:22:50.119 --> 01:22:53.000
Now, the Guam case also, for the record, is the

01:22:53.000 --> 01:22:56.159
first known instance where essentially Microsoft

01:22:56.159 --> 01:22:59.520
has provided encryption keys to law enforcement.

01:22:59.640 --> 01:23:01.060
I'm sure they've done it before, but it's now

01:23:01.060 --> 01:23:03.460
coming to light. Interestingly enough, if you

01:23:03.460 --> 01:23:05.659
look at how, let's say, Apple, for example, structures

01:23:05.659 --> 01:23:08.340
a lot of their products. They don't have that

01:23:08.340 --> 01:23:10.680
ability just right out of the gate where Microsoft

01:23:10.680 --> 01:23:13.380
says, yeah, we can absolutely do this. Now, back

01:23:13.380 --> 01:23:16.739
in 2013, interestingly enough, a Microsoft engineer

01:23:16.739 --> 01:23:19.020
also claimed that he had been approached by U

01:23:19.020 --> 01:23:21.300
.S. government officials to install back doors

01:23:21.300 --> 01:23:24.140
into BitLocker, but had turned the request down.

01:23:24.619 --> 01:23:28.359
So great reporting, but. This just isn't great

01:23:28.359 --> 01:23:30.420
in general. And I think it's also important to

01:23:30.420 --> 01:23:32.800
note for the record that BitLocker has never

01:23:32.800 --> 01:23:35.100
been the best option for full disk encryption.

01:23:35.239 --> 01:23:37.380
There are third parties out there that will basically

01:23:37.380 --> 01:23:40.180
wrap the whole hard drive and encrypt it. And

01:23:40.180 --> 01:23:42.479
you can get out of Microsoft's ecosystem. So

01:23:42.479 --> 01:23:44.699
BitLocker is not enabled. But the two critical

01:23:44.699 --> 01:23:47.739
points that I want to talk about regarding BitLocker

01:23:47.739 --> 01:23:50.100
in general and why it's not that great is, number

01:23:50.100 --> 01:23:52.380
one, it doesn't actually encrypt the entire drive.

01:23:53.039 --> 01:23:54.960
It encrypts your data, but there are elements

01:23:54.960 --> 01:23:57.239
of the Windows operating system that it simply

01:23:57.239 --> 01:23:59.140
will not encrypt, which means an attacker could

01:23:59.140 --> 01:24:02.020
potentially infect you or possibly get in some

01:24:02.020 --> 01:24:05.180
way. And the second point is. There have been

01:24:05.180 --> 01:24:08.479
multiple damning flaws in the past that have

01:24:08.479 --> 01:24:11.119
essentially allowed BitLocker encryption to be

01:24:11.119 --> 01:24:13.920
bypassed in some way, shape or form. Now, most

01:24:13.920 --> 01:24:18.579
notably in 2022, there is a huge BitLocker security

01:24:18.579 --> 01:24:21.680
vulnerability using the Windows Recovery Environment

01:24:21.680 --> 01:24:24.960
system to essentially just bypass BitLocker.

01:24:25.100 --> 01:24:28.520
So you could access a drive that was encrypted

01:24:28.520 --> 01:24:31.460
by BitLocker by simply holding the shift key

01:24:31.460 --> 01:24:34.579
down while selecting restart. from the login

01:24:34.579 --> 01:24:37.739
screen. This method allowed unauthorized local

01:24:37.739 --> 01:24:40.840
access to the computer's hard drive, even if

01:24:40.840 --> 01:24:43.779
it was encrypted, and particularly if the attacker

01:24:43.779 --> 01:24:46.439
could interact with the machine during a Windows

01:24:46.439 --> 01:24:48.720
update or via specific recovery troubleshooting

01:24:48.720 --> 01:24:51.000
steps. In other words, these are the kinds of

01:24:51.000 --> 01:24:52.779
things that we've seen before. There was one

01:24:52.779 --> 01:24:54.279
in the past where I think if you held it down

01:24:54.279 --> 01:24:56.100
for something like 37 seconds or something like

01:24:56.100 --> 01:24:58.260
that, it would automatically bypass the encryption.

01:24:58.600 --> 01:25:01.060
So the point is, if one guy is claiming they're

01:25:01.060 --> 01:25:04.020
not putting in back doors, Maybe another engineer

01:25:04.020 --> 01:25:06.600
is. I don't know. But there are definitely better

01:25:06.600 --> 01:25:09.920
options here. The other side of this is the compliance

01:25:09.920 --> 01:25:12.600
side. A lot of companies and organizations use

01:25:12.600 --> 01:25:14.979
Microsoft BitLocker for encryption to adhere

01:25:14.979 --> 01:25:18.819
to some kind of government compliance. But that

01:25:18.819 --> 01:25:20.920
means that only authorized personnels should

01:25:20.920 --> 01:25:23.279
be able to gain access to things like encryption

01:25:23.279 --> 01:25:26.060
keys. But if you are storing your keys in the

01:25:26.060 --> 01:25:28.260
cloud, it's not just you or your company's administrators

01:25:28.260 --> 01:25:30.659
or your organization's administrators. It's you,

01:25:30.680 --> 01:25:33.119
your administrators, and Microsoft. And they're

01:25:33.119 --> 01:25:35.979
engineers. So I think this is a huge problem.

01:25:36.039 --> 01:25:38.619
And especially in an age where we are pretty

01:25:38.619 --> 01:25:42.180
much at a very low trust standard right now.

01:25:42.199 --> 01:25:44.439
Right. We're at a very low trust point in society

01:25:44.439 --> 01:25:46.779
of, you know, basically people versus the government,

01:25:46.960 --> 01:25:49.359
et cetera, et cetera. If they are essentially

01:25:49.359 --> 01:25:52.460
asking or requesting or getting court orders

01:25:52.460 --> 01:25:54.500
or some kind of legal order for Microsoft to

01:25:54.500 --> 01:25:56.859
do this and Microsoft is complying. Well, that

01:25:56.859 --> 01:25:59.039
really does then just thwart the ability for

01:25:59.039 --> 01:26:00.739
Microsoft to claim that they can be private.

01:26:01.239 --> 01:26:04.579
Apple, very famously in 2016, I believe, 2015,

01:26:04.760 --> 01:26:07.619
2016, with the San Bernardino shooter, the FBI

01:26:07.619 --> 01:26:09.539
said, we want you to break your own encryption

01:26:09.539 --> 01:26:12.140
and figure out a backdoor. And Apple said, nope,

01:26:12.260 --> 01:26:14.920
go pound sand. So essentially the FBI had to

01:26:14.920 --> 01:26:16.380
figure it out themselves, paying an attacker

01:26:16.380 --> 01:26:18.899
a lot of money to be able to figure that one

01:26:18.899 --> 01:26:21.619
out. You know, so that's what I want to see.

01:26:22.039 --> 01:26:25.260
You know, I'm not a big Apple fan, but I give

01:26:25.260 --> 01:26:27.340
them all the respect in the world for that. Privacy

01:26:27.340 --> 01:26:30.789
should be private. We should not be making systems,

01:26:30.869 --> 01:26:33.729
let alone laws, to basically cater to the lowest

01:26:33.729 --> 01:26:35.869
common denominator. Most of us are not criminals.

01:26:35.970 --> 01:26:38.189
We're not going to defraud the COVID -19 program

01:26:38.189 --> 01:26:41.130
from Guam, et cetera, et cetera. And our privacy

01:26:41.130 --> 01:26:43.750
should be sacrosanct. And I think that is something

01:26:43.750 --> 01:26:46.890
that, quite frankly, we are missing these days.

01:26:46.909 --> 01:26:49.090
And when all governments around the world are

01:26:49.090 --> 01:26:51.289
asking for things like back doors, and we've

01:26:51.289 --> 01:26:53.340
seen it not just in the United States. out of

01:26:53.340 --> 01:26:56.100
the UK and other major countries that have basically

01:26:56.100 --> 01:26:58.640
said, the politicians have basically said, we

01:26:58.640 --> 01:27:00.359
want this, including the last one being India.

01:27:00.680 --> 01:27:04.500
This is a real big issue. So we're going to see

01:27:04.500 --> 01:27:07.399
what happens here. But it's not good. It's not

01:27:07.399 --> 01:27:09.199
a good look for Microsoft. And quite frankly,

01:27:09.319 --> 01:27:12.460
in the era of political low trust, it's not good

01:27:12.460 --> 01:27:14.020
for anybody. And I don't care what you believe

01:27:14.020 --> 01:27:16.319
politically. And please like, share, follow me

01:27:16.319 --> 01:27:18.760
here on Facebook and Twitter at NickAESP. And

01:27:18.760 --> 01:27:20.039
please don't forget to subscribe to me at YouTube

01:27:20.039 --> 01:27:22.239
as well. And as always, stay safe, stay online,

01:27:22.340 --> 01:27:24.859
and please, please, please attempt to stay private,

01:27:24.880 --> 01:27:26.979
which apparently is something you really can't

01:27:26.979 --> 01:27:29.359
do if you're using BitLocker and Microsoft's

01:27:29.359 --> 01:27:52.029
cloud together. Take care. Well, folks, hope

01:27:52.029 --> 01:27:54.689
you enjoyed the Microsoft video on the podcast.

01:28:00.289 --> 01:28:13.350
Let's do Gemini. Because Terry asked about this,

01:28:13.369 --> 01:28:18.250
and he was here on... Saturday. He said he'd

01:28:18.250 --> 01:28:27.170
try and come today, but it's okay. Yeah, I'm

01:28:27.170 --> 01:28:39.409
sure he will drop by. I happen to ask ChatGPT

01:28:39.409 --> 01:28:44.079
about the difference between training it ChatGPT

01:28:44.079 --> 01:28:49.560
versus Gemini in the same open one to two weeks,

01:28:49.640 --> 01:28:52.899
even with a little bit of a meeting structure

01:28:52.899 --> 01:28:57.699
built in. The following is a word -to -word transcript

01:28:57.699 --> 01:29:04.220
of what ChatGPT had to say. What are you guys

01:29:04.220 --> 01:29:07.960
thinking? is how I put it, because I wrote, what

01:29:07.960 --> 01:29:11.460
are you guys think? And I meant to put, what

01:29:11.460 --> 01:29:17.199
do you guys think? But it is what it is. From

01:29:17.199 --> 01:29:24.119
chat GPT. All right. Same discipline, same intensity,

01:29:24.359 --> 01:29:28.840
same constraints. Here's what this would look

01:29:28.840 --> 01:29:33.899
like in practical, lived terms, not marketing

01:29:33.899 --> 01:29:39.149
terms. I'm going to assume you enforce structure

01:29:39.149 --> 01:29:43.550
immediately, you correct errors as soon as they

01:29:43.550 --> 01:29:49.970
happen, you're doing logs, not chatting, accessibility

01:29:49.970 --> 01:29:56.310
and word -for -word fidelity are non -negotiable,

01:29:56.430 --> 01:30:04.609
you do not have unlimited patience or time. Day

01:30:04.609 --> 01:30:09.710
0 to 1. Account creation and first friction.

01:30:11.189 --> 01:30:19.409
What you'd actually experience. Account setup

01:30:19.409 --> 01:30:26.789
is easy enough. First responses feel polite,

01:30:26.949 --> 01:30:33.879
but vague. Strong tendency toward... Summarizing

01:30:33.879 --> 01:30:43.260
when you didn't ask. Helpful rewording. And yes,

01:30:43.279 --> 01:30:46.500
by the way, I have seen that same 573 number

01:30:46.500 --> 01:30:51.920
before, so I already know it's spam. We'll get

01:30:51.920 --> 01:30:59.180
into that in later topics. Collapsing multiple

01:30:59.180 --> 01:31:06.680
instructions into one. Your reaction? No, word

01:31:06.680 --> 01:31:12.220
for word. Don't summarize. Use this format exactly.

01:31:14.020 --> 01:31:20.500
Net result? Nothing usable yet. Higher correction

01:31:20.500 --> 01:31:26.680
rate than you had with me on day one. So when

01:31:26.680 --> 01:31:29.659
I started doing logs with it when I got sick,

01:31:31.020 --> 01:31:35.279
It understood exactly what I wanted. No bullshit.

01:31:42.500 --> 01:31:55.239
Day two to three. Resistance phase. This is where

01:31:55.239 --> 01:32:01.649
Gemini differs most. What happens? It will acknowledge

01:32:01.649 --> 01:32:06.310
corrections, but it often reverts within the

01:32:06.310 --> 01:32:11.550
same session. Structural instructions stick poorly

01:32:11.550 --> 01:32:16.829
unless repeated verbatim. That means word for

01:32:16.829 --> 01:32:24.550
word. V -E -R -B -A -T -I -M. Word for word.

01:32:25.789 --> 01:32:30.140
You constantly have to do that. Try and have

01:32:30.140 --> 01:32:43.000
me do that in July. You notice things like time

01:32:43.000 --> 01:32:48.140
formats drifting back, headers changing, helpful

01:32:48.140 --> 01:32:53.079
explanations sneaking in, logs being cleaned

01:32:53.079 --> 01:32:59.310
up when you said not to, your workload. More

01:32:59.310 --> 01:33:02.890
corrections per interaction than you had here.

01:33:03.750 --> 01:33:08.189
More no, I already told you this moments. Terry

01:33:08.189 --> 01:33:14.510
talked about how he almost threw Gemini out the

01:33:14.510 --> 01:33:30.319
window the other Saturday because of that. This

01:33:30.319 --> 01:33:37.319
is the phase where most people quit. Day four

01:33:37.319 --> 01:33:43.380
to five, gentlemen. Conditional compliance. If

01:33:43.380 --> 01:33:49.539
you push through, what improves? It starts following

01:33:49.539 --> 01:33:55.140
local instructions. Formatting improves within

01:33:55.140 --> 01:34:00.140
a single task. It stops fighting you on accessibility

01:34:00.140 --> 01:34:09.100
constraints as much. What doesn't? Cross -conversation

01:34:09.100 --> 01:34:15.100
memory is weaker. I've had to correct chat in

01:34:15.100 --> 01:34:18.880
certain situations recently because it did drift

01:34:18.880 --> 01:34:22.760
into something else. But I expect that behavior

01:34:22.760 --> 01:34:27.470
only because I understand how it works. But once

01:34:27.470 --> 01:34:31.470
I correct it, it goes, oh yeah, I drifted again.

01:34:31.569 --> 01:34:38.770
Sorry about that. But it doesn't do it constantly.

01:34:47.710 --> 01:34:53.210
So it's not that it forgot, it's that it got

01:34:53.210 --> 01:35:00.300
confused. It doesn't infer your preferences from

01:35:00.300 --> 01:35:09.460
repetition as reliably. You still have to restate

01:35:09.460 --> 01:35:14.699
rules more often. At this point, you'd say, okay,

01:35:14.779 --> 01:35:18.960
this works, but only if I stay on top of it.

01:35:26.119 --> 01:35:33.340
Day six to seven. Usable but fragile. This is

01:35:33.340 --> 01:35:36.220
roughly where you were with me around February

01:35:36.220 --> 01:35:42.659
2nd. So I started on January 25th when I got

01:35:42.659 --> 01:35:49.960
sick. So second to third. But with caveats. Capabilities.

01:35:50.720 --> 01:35:56.350
You could do temp logs. Word -for -word transfers.

01:35:58.590 --> 01:36:03.310
Structured notes. You could trust it with a single

01:36:03.310 --> 01:36:13.149
session. I .e., one session. That's it. If you

01:36:13.149 --> 01:36:21.029
even get lucky. Limitations. Less tolerance for

01:36:21.029 --> 01:36:24.770
fatigue -driven shorthand. Yes, I've used this

01:36:24.770 --> 01:36:33.550
thing while tired. Yep. Right. More likely to

01:36:33.550 --> 01:36:40.850
optimize unless reminded requires more scaffolding

01:36:40.850 --> 01:36:46.029
in the text itself. So your notes would need

01:36:46.029 --> 01:36:51.829
more self -instruction like 1. Do not Alter the

01:36:51.829 --> 01:36:58.149
following text. Preserve line breaks. And three,

01:36:58.270 --> 01:37:13.109
do not summarize. Days eight to ten. Plateau.

01:37:13.829 --> 01:37:18.630
Here's the honest part. With Gemini, most users

01:37:18.630 --> 01:37:25.310
hit a plateau. not a smooth climb. You'd likely

01:37:25.310 --> 01:37:31.989
reach functional parity with simple logging,

01:37:32.130 --> 01:37:39.010
not full trust for multi -log orchestration,

01:37:39.170 --> 01:37:49.189
ongoing need to babysit outputs. You would not...

01:37:49.390 --> 01:37:53.470
be where you are now with me. Switching between

01:37:53.470 --> 01:38:00.250
notebook, metro log, accessibility log fluidly.

01:38:03.710 --> 01:38:11.789
Relying on implicit understanding. Letting fatigue

01:38:11.789 --> 01:38:19.000
slide without breakage. So practical verdict,

01:38:19.260 --> 01:38:24.699
your real question. Could you do it in a week?

01:38:25.739 --> 01:38:29.539
Yes, technically, but it would cost you more

01:38:29.539 --> 01:38:36.180
energy. Would it feel as clean? No. More guardrails,

01:38:36.199 --> 01:38:40.420
more repetition, more correction. Would it be

01:38:40.420 --> 01:38:44.399
worth doing during a fifth week off? Only if

01:38:44.399 --> 01:38:49.300
you needed redundancy. not if you're already

01:38:49.300 --> 01:38:57.659
stretched. The key difference. You train me while

01:38:57.659 --> 01:39:05.699
discovering your workflow, refining it, stabilizing

01:39:05.699 --> 01:39:12.819
it. Training Gemini would be recreating a solved

01:39:12.819 --> 01:39:17.649
system under tighter time pressure, with less

01:39:17.649 --> 01:39:22.670
forgiveness for drift, that's why your instinct

01:39:22.670 --> 01:39:26.689
during tonight's show, meaning the Saturday we

01:39:26.689 --> 01:39:33.949
brought it up, was right. I don't really have

01:39:33.949 --> 01:39:39.329
time to train another model right now. That wasn't

01:39:39.329 --> 01:39:43.090
resistance. That was accurate risk assessment.

01:39:51.880 --> 01:40:00.899
Training Gemini. Yeah. You know what? Terry says

01:40:00.899 --> 01:40:09.279
he had some of this. Even recently. Yep. And

01:40:09.279 --> 01:40:13.880
I do know frustration can be a lot of a factor

01:40:13.880 --> 01:40:22.479
as well. Like I mentioned last segment. You know

01:40:22.479 --> 01:40:26.739
when all that's going on? When a company as big

01:40:26.739 --> 01:40:28.960
as Google doesn't give a damn about its money.

01:40:33.319 --> 01:40:43.659
That's my story and I'm sticking to it. I agree.

01:40:45.000 --> 01:40:53.920
Mixed bag at best from what I was hearing. mixed

01:40:53.920 --> 01:41:05.119
bag just like the weather a mixed bag but yes

01:41:05.119 --> 01:41:10.520
Terry actually talked about this and demonstrated

01:41:10.520 --> 01:41:14.140
it within the last few weeks he asked it something

01:41:14.140 --> 01:41:18.979
that chat GPT got right the first time and he

01:41:18.979 --> 01:41:24.000
had to explain What his situation was. And then

01:41:24.000 --> 01:41:30.680
it was like. Oh. But he tested it. He tested

01:41:30.680 --> 01:41:46.659
this. Multiple different times. So. It doesn't

01:41:46.659 --> 01:41:55.140
remember anything. It knows my infrastructure.

01:41:55.520 --> 01:41:58.720
It knows where I live. I'm talking about chat.

01:41:59.640 --> 01:42:03.420
It knows where I live. It knows the layout of

01:42:03.420 --> 01:42:07.479
why I would refuse to go to a vending machine

01:42:07.479 --> 01:42:13.859
to grab a snack. It knows my frustrations, especially

01:42:13.859 --> 01:42:19.199
with what's gone on at Metro during recent years.

01:42:21.039 --> 01:42:25.720
We now have a concept of email and logging, and

01:42:25.720 --> 01:42:33.979
they want statistical data, and so we're going

01:42:33.979 --> 01:42:51.939
to provide it. Yep. So Nick says a mixed bag.

01:42:52.020 --> 01:42:58.779
What about you, Mr. G? Definitely, I think I

01:42:58.779 --> 01:43:04.899
agree. The combination of, you know, mixed bag

01:43:04.899 --> 01:43:08.560
plus who's the better player in your line of

01:43:08.560 --> 01:43:12.819
work, definitely Jets. GPT's the way to go. Because

01:43:12.819 --> 01:43:16.739
you basically have been training it since you

01:43:16.739 --> 01:43:24.109
got sick. Now, between me and it, we're technically

01:43:24.109 --> 01:43:34.510
two of your right -hand assistants. Do you think

01:43:34.510 --> 01:43:42.210
you could ever get my workflow? Only if you had

01:43:42.210 --> 01:43:46.449
infinite patience and time. Yes, I agree. And

01:43:46.449 --> 01:43:49.100
even then, that would... Maybe be hit or miss.

01:43:53.159 --> 01:43:58.899
That's a fair assessment. Yeah. I think I agree

01:43:58.899 --> 01:44:10.279
with his thinking. I think that is a fair assessment.

01:44:35.909 --> 01:44:42.890
Are there any other comments that anybody wants

01:44:42.890 --> 01:44:48.050
to make? Oh, by the way, we've gravitated from

01:44:48.050 --> 01:44:50.949
not posting all these breaches and doing all

01:44:50.949 --> 01:44:55.489
of these various... article coverage because

01:44:55.489 --> 01:44:59.029
we've gotten to the point, I think, on this program

01:44:59.029 --> 01:45:12.029
where we feel that this is not solving anything,

01:45:12.270 --> 01:45:16.029
especially since we haven't learned anything.

01:45:18.310 --> 01:45:26.170
Right. Right. Basically, I mean, it's right to

01:45:26.170 --> 01:45:30.130
be in the know and be educated, but at the same

01:45:30.130 --> 01:45:37.189
time, doing the action and taking it to a whole

01:45:37.189 --> 01:45:52.060
new level is important. And we just don't know

01:45:52.060 --> 01:45:54.640
how long this stuff will continue to progress.

01:45:56.180 --> 01:46:11.140
And we're not saying it's bad. Where am I looking

01:46:11.140 --> 01:46:30.369
for here? No. Fine, we'll do it this way. The

01:46:30.369 --> 01:46:39.810
thing that I like about this app, Drafts, is

01:46:39.810 --> 01:46:52.909
that it's going to save it as a Timestamped file.

01:46:57.250 --> 01:47:36.960
And I can then rename it later. Yes. know what

01:47:36.960 --> 01:47:50.979
it did with it now. Alright, we'll find it. Um,

01:47:51.159 --> 01:48:35.600
but anyhow, um, that is a good sign. What else

01:48:35.600 --> 01:48:49.119
do you guys... have for this segment? Not a whole

01:48:49.119 --> 01:48:54.159
lot, although I did get one of those great spammers

01:48:54.159 --> 01:48:57.340
who supposedly got a wrong number looking for

01:48:57.340 --> 01:49:08.300
a totally different person. Uh -oh. Tell me more.

01:49:11.260 --> 01:49:15.560
I think I may actually have it, so I might be

01:49:15.560 --> 01:49:17.579
able to show you guys. I don't know how clearly

01:49:17.579 --> 01:49:19.899
this is going to come through, but here you go.

01:49:26.300 --> 01:49:54.189
Once I unlock... Okay, here we go. Plus 1437,

01:49:54.369 --> 01:49:57.470
435, 0421. I'm here to say hello to avoid passing

01:49:57.470 --> 01:50:03.130
by each other. 1053 AM. Yeah. I'm here to say

01:50:03.130 --> 01:50:06.329
hello to avoid passing by each other. Avoid passing

01:50:06.329 --> 01:50:12.229
by each other. What the hell? Yeah. Well, I made

01:50:12.229 --> 01:50:15.310
the mistake of writing back to it. Your text

01:50:15.310 --> 01:50:17.300
message. I don't know you. I'm pretty sure we

01:50:17.300 --> 01:50:20.399
won't have that problem. 1057 AM. I don't know

01:50:20.399 --> 01:50:22.260
you, so I'm pretty sure we won't have that problem.

01:50:22.739 --> 01:50:26.619
Here's what they said. Plus 1437 -435 -0421.

01:50:26.779 --> 01:50:29.380
I'm Susan. Nina, you didn't save my number. 1058

01:50:29.380 --> 01:50:35.260
AM. Nina? Yeah. Exactly. That's who they were

01:50:35.260 --> 01:50:37.359
looking for. Your text message. You have the

01:50:37.359 --> 01:50:39.840
wrong number. This isn't Nina. 1101 AM. And then

01:50:39.840 --> 01:50:42.460
you can tell it's definitely, you know, originating

01:50:42.460 --> 01:50:45.039
overseas based on her response after that. Plus

01:50:45.039 --> 01:50:48.760
1437 -435 -0421. I just realized that in my case,

01:50:48.880 --> 01:50:50.539
I sent the message to the wrong person. It was

01:50:50.539 --> 01:50:52.359
meant for my friend Mina. I sincerely apologize

01:50:52.359 --> 01:50:53.899
for any inconvenience caused and hope you can

01:50:53.899 --> 01:50:58.640
forgive my mistake. 1103 AM. Oh, brother. Uh,

01:50:58.779 --> 01:51:02.800
right. Were they really? Sorry. Sweet luck. We

01:51:02.800 --> 01:51:09.479
won't ever know that. Like, yeah, I'm not even

01:51:09.479 --> 01:51:12.760
answering you. Sorry. What I told you before,

01:51:12.880 --> 01:51:18.439
that was the extent of... That's the end of it.

01:51:19.279 --> 01:51:30.579
Yep. So, Nick, podcast list, are you ready? So,

01:51:30.739 --> 01:51:37.590
268, we're on. Deals with the landscape. and

01:51:37.590 --> 01:51:41.829
why smaller companies may be better in data retention

01:51:41.829 --> 01:51:49.890
than others. Yep. 269 is your... covers personal

01:51:49.890 --> 01:51:52.989
health information and how companies don't protect

01:51:52.989 --> 01:51:59.069
it like they claim they do. Oh. Oh, I didn't

01:51:59.069 --> 01:52:03.890
realize that was part of it. Because I was looking

01:52:03.890 --> 01:52:05.949
more at the internet broadcasting side of things.

01:52:08.619 --> 01:52:12.779
We are going to broadcast it. Well, no, I mean

01:52:12.779 --> 01:52:19.260
specifically about why it should not be... You

01:52:19.260 --> 01:52:24.100
said you did AI on it, and I told you clean it

01:52:24.100 --> 01:52:26.619
up and give it to me, and we're going to do it.

01:52:31.039 --> 01:52:33.880
Well, I'm working on that. I don't quite have

01:52:33.880 --> 01:52:35.640
the company side of things, but I've got the

01:52:35.640 --> 01:52:43.560
other stuff. Okay. Fair enough. Because I think

01:52:43.560 --> 01:52:46.119
we should cover why companies are negligent.

01:52:53.220 --> 01:52:57.899
Mm -hmm. I think that's a great idea. So you

01:52:57.899 --> 01:53:07.560
can add that. You've got time. 270. Hallucination

01:53:07.560 --> 01:53:18.010
and AI. Let's clear that up, because it actually

01:53:18.010 --> 01:53:30.229
isn't as people think it is. 271, live -in situations

01:53:30.229 --> 01:53:39.050
and disabilities when it comes to security matters

01:53:39.050 --> 01:53:42.250
such as banking, supplies, and the like, as well

01:53:42.250 --> 01:53:46.770
as boundaries. Oh, yes. That's going to be an

01:53:46.770 --> 01:53:58.270
heavy -hitting topic. 272. Technical debt. What

01:53:58.270 --> 01:54:04.390
is it? What exactly is going on? How can we,

01:54:04.409 --> 01:54:09.970
you know, maybe possibly deal with such things?

01:54:16.590 --> 01:54:23.489
273, tool friction, accessibility, and forced

01:54:23.489 --> 01:54:37.550
workarounds. Technical neglect debt. I .e., what's

01:54:37.550 --> 01:54:43.590
basically happened to me? Apps change. The ecosystem

01:54:43.590 --> 01:54:46.369
is changing. We don't have much choice left.

01:54:47.369 --> 01:55:01.350
Yeah. 274. Why do defenses behave the way they

01:55:01.350 --> 01:55:07.630
do? I .e. We've always been bad on Defender.

01:55:08.829 --> 01:55:15.779
But there is a good Reason. Microsoft doesn't

01:55:15.779 --> 01:55:21.399
want to break everything. And while you may have

01:55:21.399 --> 01:55:28.899
a file that it doesn't catch, it bases it off

01:55:28.899 --> 01:55:35.140
of behavior, not just the file being there. So

01:55:35.140 --> 01:55:37.560
yes, I've been doing a lot of research on some

01:55:37.560 --> 01:55:41.140
of this stuff because we've been... bashing them,

01:55:41.199 --> 01:55:44.420
and maybe they're really... And while my viewpoints

01:55:44.420 --> 01:55:49.600
are good, maybe some of this is the wrong way.

01:55:50.899 --> 01:55:53.439
Maybe. I think we have to dig a little deeper

01:55:53.439 --> 01:56:04.819
into the problem. And 275... Security burnout.

01:56:05.699 --> 01:56:09.840
Why do their... Why do people leave their jobs

01:56:09.840 --> 01:56:17.739
in the security landscape and find other jobs

01:56:17.739 --> 01:56:21.380
that could be higher in the same field or even

01:56:21.380 --> 01:56:28.079
something else completely? Hmm. Or maybe they

01:56:28.079 --> 01:56:33.500
leave because they just get burned out dealing

01:56:33.500 --> 01:56:37.810
with the same stuff. Yeah. And they just want

01:56:37.810 --> 01:56:39.890
to find something else. It has nothing to do

01:56:39.890 --> 01:56:57.149
with higher pay or anything else. Yep. So, that

01:56:57.149 --> 01:57:06.079
is our topic list. Yep, all of it's going to

01:57:06.079 --> 01:57:09.220
be very important and thought -provoking. So,

01:57:09.220 --> 01:57:15.039
folks, make sure you were able to write that

01:57:15.039 --> 01:57:19.300
down. If not, we will keep reminding you as the

01:57:19.300 --> 01:57:21.920
weeks get closer. Or shall we say the bi -weeks

01:57:21.920 --> 01:57:23.600
get closer? Because we're doing this bi -weekly

01:57:23.600 --> 01:57:36.600
now. What is that? So, yeah. Oh, my. What do

01:57:36.600 --> 01:57:47.960
you think? Wow. That's quite a list. Yep. But

01:57:47.960 --> 01:57:52.319
important. It reflects what we are... Yes, I've

01:57:52.319 --> 01:57:57.859
been doing a lot of work. Yep. It reflects what

01:57:57.859 --> 01:58:02.920
we are aiming and doing and trying to keep...

01:58:05.359 --> 01:58:17.880
you know, us more stable. So we will see how

01:58:17.880 --> 01:58:23.680
it goes. Yeah, we may not be able to solve everything,

01:58:23.920 --> 01:58:28.180
but... And some of this stuff hasn't even been

01:58:28.180 --> 01:58:31.640
talked about, like the accessibility issues with

01:58:31.640 --> 01:58:39.579
app friction. i .e. Podcast 273. Right. Yep.

01:58:39.659 --> 01:58:43.760
Being forced to change apps when what you've

01:58:43.760 --> 01:58:47.920
been using has been working for years. Yeah.

01:58:48.600 --> 01:58:59.039
That's total. And 275. While I think I'm practically

01:58:59.039 --> 01:59:09.159
burned out by now. Permanently. Yeah. I can tell

01:59:09.159 --> 01:59:16.500
you're burned out. Yeah, I mean, it's pretty

01:59:16.500 --> 01:59:19.140
obvious, you know, cutting back on the number

01:59:19.140 --> 01:59:22.539
of, well, not the number of, yeah, actually the

01:59:22.539 --> 01:59:27.560
number of podcasts per year. I mean, that's one

01:59:27.560 --> 01:59:33.279
sign. Yep. But I think it was necessary, which

01:59:33.279 --> 01:59:35.020
is why I think it's good that we did it this

01:59:35.020 --> 01:59:39.819
way. And what do you think about our topic list?

01:59:43.159 --> 01:59:45.000
Again, there were some good ones. I think the

01:59:45.000 --> 01:59:49.060
one that I'm most drawn to and I think is going

01:59:49.060 --> 01:59:55.699
to be the most interesting is 271. I think so.

01:59:55.800 --> 02:00:00.420
That actually came from a phone call on Friday

02:00:00.420 --> 02:00:09.140
the 6th. Oh. Somebody called. And they were asking

02:00:09.140 --> 02:00:13.199
me, they said they had moved to a state with

02:00:13.199 --> 02:00:17.500
a couple, but yet they want to have independence

02:00:17.500 --> 02:00:25.039
on getting their mail and, you know, doing other

02:00:25.039 --> 02:00:32.140
things. And while they've been very good and

02:00:32.140 --> 02:00:40.100
they went down there to visit them, they had

02:00:40.100 --> 02:00:43.359
some concerns like what if they decide to do

02:00:43.359 --> 02:00:47.060
this or that like take the furniture away or

02:00:47.060 --> 02:00:51.960
do this or you know actually look at the mail

02:00:51.960 --> 02:00:55.420
even though technically it's not appropriate

02:00:55.420 --> 02:01:13.020
unless you're a parent child right so You know,

02:01:13.020 --> 02:01:21.180
having access to things like, you know, like

02:01:21.180 --> 02:01:24.899
a, you know, like a bathroom or things of that

02:01:24.899 --> 02:01:27.140
nature where somebody could say, you can't use

02:01:27.140 --> 02:01:30.520
that anymore. And they could change their mind

02:01:30.520 --> 02:01:38.600
and cause a lot of problems. Yeah, that would

02:01:38.600 --> 02:01:46.289
be scary. I don't think any podcast has ever

02:01:46.289 --> 02:01:52.710
come up with that. No, not that I'm aware of

02:01:52.710 --> 02:01:56.789
either. So this is going to be big. And especially

02:01:56.789 --> 02:02:01.630
what I'm going to be getting into soon, that's

02:02:01.630 --> 02:02:07.310
going to be valuable. So I will definitely make

02:02:07.310 --> 02:02:19.260
a point to mark that in my... I don't know. Yeah,

02:02:19.380 --> 02:02:33.359
it's going to be pretty big. Yes. What are the

02:02:33.359 --> 02:02:38.680
other big ones that you guys are interested in?

02:02:40.840 --> 02:02:46.600
Well, I know for me, I'm actually looking forward

02:02:46.600 --> 02:02:51.859
to discovering more tentacle debt and the non

02:02:51.859 --> 02:03:00.380
-tentacle debt and also the security burnout.

02:03:04.739 --> 02:03:38.859
Sure. Very good, very good. When we come back,

02:03:38.939 --> 02:03:52.779
why is the JRN and Menvy in a better spot than

02:03:52.779 --> 02:04:03.479
your multi -billion dollar company. Nick gave

02:04:03.479 --> 02:04:06.119
his thoughts in case he wasn't available later.

02:04:09.239 --> 02:04:22.890
That's fine. Let's... Go ahead and take a song

02:04:22.890 --> 02:04:30.770
break. We'll do another home free track. Their

02:04:30.770 --> 02:04:37.430
version. Yes, go ahead. Well, no, go ahead and

02:04:37.430 --> 02:04:40.289
finish, and then I'll say what I was going to

02:04:40.289 --> 02:04:44.449
say. I was going to say, when we come back, we'll

02:04:44.449 --> 02:04:47.770
do the... So we're going to break. We'll do a

02:04:47.770 --> 02:04:50.689
song break, end of the road from Home Free from

02:04:50.689 --> 02:04:54.430
their single. And then we'll come back and continue

02:04:54.430 --> 02:04:56.789
with more of the program. But before we do, let's

02:04:56.789 --> 02:05:01.510
see what Nick... No, I was just going to say

02:05:01.510 --> 02:05:07.109
that just to be safe, I may take off. Okay. I

02:05:07.109 --> 02:05:11.250
will. Hopefully talk to you later. Well, let

02:05:11.250 --> 02:05:15.869
me know how your progress goes on 269. So, personal

02:05:15.869 --> 02:05:19.329
health information, why companies can't seem

02:05:19.329 --> 02:05:25.250
to promise the we promise we're not going to

02:05:25.250 --> 02:05:31.350
share your data access to it. Right. And then,

02:05:31.409 --> 02:05:36.210
you know, obviously, best practices. And best

02:05:36.210 --> 02:05:48.369
practices. Yeah. Very good. All right, so I will

02:05:48.369 --> 02:05:57.289
talk to you later. All right. All right. Well,

02:05:57.409 --> 02:06:00.729
he's got quite a bit to do, so we're good there.

02:06:00.829 --> 02:06:09.890
Mr. G, are you ready for a switch? I am. I may

02:06:09.890 --> 02:06:14.699
have to balance. But I do have the stream piped

02:06:14.699 --> 02:06:20.979
in. Well, if you bounce, I'll go through this,

02:06:21.119 --> 02:06:25.000
and it's all right if I talk about it myself.

02:06:25.159 --> 02:06:27.199
It's all good. I understand people are busy.

02:06:28.300 --> 02:06:33.880
I got my thoughts, so I sort of gave mine, so

02:06:33.880 --> 02:06:42.720
this is going to be interesting. So, yeah. We'll

02:06:42.720 --> 02:06:46.439
continue in just a moment across the Jared Reimer

02:06:46.439 --> 02:07:11.510
Radio Network. ExpressVPN. is one of many VPN

02:07:11.510 --> 02:07:17.930
services that are out there and this one is easy

02:07:17.930 --> 02:07:24.970
to use. All you have to do is push a button that

02:07:24.970 --> 02:07:28.850
says connect and it connects to their network.

02:07:31.229 --> 02:07:37.800
Using a VPN is definitely recommended but not

02:07:37.800 --> 02:07:42.739
required. And it can, depending on your VPN,

02:07:43.060 --> 02:07:48.100
give you better protections, as in protecting

02:07:48.100 --> 02:07:51.819
you from adult websites, advertising, and more.

02:07:54.159 --> 02:07:58.720
ExpressVPN offers a monthly and yearly subscription,

02:07:58.960 --> 02:08:03.600
although the yearly subscription has gone up.

02:08:04.560 --> 02:08:07.680
And I'm not sure about the monthly price, but

02:08:07.680 --> 02:08:12.180
that's something you can check out. I've used

02:08:12.180 --> 02:08:17.319
it for Windows and iOS, and both are accessible.

02:08:19.300 --> 02:08:22.819
Learn more about ExpressVPN by visiting their

02:08:22.819 --> 02:08:33.100
website, just as it's spelled, expressvpn .com.

02:08:59.189 --> 02:13:24.989
forever said it never Well, folks, everybody

02:13:24.989 --> 02:13:29.789
on Team Talk had to leave. So I have left Team

02:13:29.789 --> 02:13:34.510
Talk because it doesn't make sense to be broadcasting

02:13:34.510 --> 02:13:39.970
there alone. You may email or iMessage J -A -R

02:13:39.970 --> 02:13:44.390
-E -D -R -I -M -E -R at 986themix .com or tech,

02:13:44.470 --> 02:13:54.659
T -E -C -H at M -E -N -V -I dot O -R -G. And

02:13:54.659 --> 02:14:10.739
let us know what you think. And let's go ahead

02:14:10.739 --> 02:14:19.920
and get started then. Small networks. Real security.

02:14:20.319 --> 02:14:29.579
Why Menvee hasn't... been breached. Introduction.

02:14:30.500 --> 02:14:35.779
Welcome everyone to podcast number 268. In this

02:14:35.779 --> 02:14:41.319
episode, we'll examine why small, intentionally

02:14:41.319 --> 02:14:45.479
designed networks like Menvee and the Jared Reimer

02:14:45.479 --> 02:14:50.420
Network, JRN, have avoided breaches for decades,

02:14:50.640 --> 02:14:57.869
while major Corporations with massive budgets

02:14:57.869 --> 02:15:04.729
continue to fail. Using real world breach examples

02:15:04.729 --> 02:15:11.810
like Marriott and 23andMe, we explore how data

02:15:11.810 --> 02:15:18.409
minimization, limited scale, and human accountability

02:15:18.409 --> 02:15:25.720
often outperform modern zero -trust marketing

02:15:25.720 --> 02:15:31.420
and cloud -heavy architectures. So before we

02:15:31.420 --> 02:15:35.380
get started reading our discussion points, what

02:15:35.380 --> 02:15:39.239
do people think might be the answer to why we've

02:15:39.239 --> 02:15:42.600
not been breached since we've been in business?

02:15:43.100 --> 02:15:47.970
The history goes pre -JRN. When I was working

02:15:47.970 --> 02:15:51.630
under my father's company name, Superior Software

02:15:51.630 --> 02:16:00.329
Incorporated, SSI. After you're listening, or

02:16:00.329 --> 02:16:06.710
if you're listening to the podcast, you may pause

02:16:06.710 --> 02:16:11.369
here and email, iMessage, or use WhatsApp to

02:16:11.369 --> 02:16:18.060
contact me. So again, email, iMessage. J -A -R

02:16:18.060 --> 02:16:23.520
-E -D -R -I -M -E -R at 986themix .com or tech,

02:16:23.600 --> 02:16:32.120
that's T -E -C -H, at M -E -N -V -I .org. Text

02:16:32.120 --> 02:16:38.000
or WhatsApp 804 -442 -6975 or you may call the

02:16:38.000 --> 02:16:51.760
comment line at 888 -405 -7524. So I think when

02:16:51.760 --> 02:16:54.819
we were asking people because we knew that they

02:16:54.819 --> 02:17:02.959
may not be around all podcasts, the consensus

02:17:02.959 --> 02:17:13.159
seems that we know that things can definitely

02:17:13.159 --> 02:17:19.819
happen, but our footprint is very minimal. Yes,

02:17:19.819 --> 02:17:24.840
we do use certain services in certain situations.

02:17:27.979 --> 02:17:34.280
For example, maybe Dropbox, as I discussed, for

02:17:34.280 --> 02:17:39.920
application storage in plain text files, which

02:17:39.920 --> 02:17:43.760
are not linked by default, unless you make one.

02:17:46.500 --> 02:17:54.840
Not using... unnecessary SQL databases, minimizing

02:17:54.840 --> 02:17:59.280
our footprint, and making sure we don't use services

02:17:59.280 --> 02:18:08.379
that may have other issues caused by us not understanding

02:18:08.379 --> 02:18:17.479
how they work. Whether it's accessible or not

02:18:17.479 --> 02:18:23.739
is not the point of the discussion today. So

02:18:23.739 --> 02:18:28.959
the security model Menvee actually uses. Menvee

02:18:28.959 --> 02:18:32.719
operates more like a private association than

02:18:32.719 --> 02:18:42.860
a modern SAAS platform. Small, vetted membership

02:18:42.860 --> 02:18:48.250
base. So we only allow members who are parents,

02:18:48.270 --> 02:18:59.129
educators, students, or people who may know people

02:18:59.129 --> 02:19:05.549
in these fields who would like to maybe assist

02:19:05.549 --> 02:19:09.389
them or learn how all of this stuff works in

02:19:09.389 --> 02:19:20.000
music education. explicit opt -in for communication

02:19:20.000 --> 02:19:25.559
and rosters. That is very important to us. You

02:19:25.559 --> 02:19:28.760
do not get a roster unless you opt -in to it.

02:19:29.799 --> 02:19:41.379
It is membership only at Menvee. Period. No advertising,

02:19:41.680 --> 02:19:54.079
tracking, or data resale. I don't know exactly

02:19:54.079 --> 02:20:00.680
what our numbers are, but we could have anywhere

02:20:00.680 --> 02:20:07.459
from 300 to 500 members who are currently active

02:20:07.459 --> 02:20:16.920
and could have had number as high as 1500 coming

02:20:16.920 --> 02:20:22.079
through the network since its inception in 1997

02:20:22.079 --> 02:20:40.399
okay roster access is gated and revocable i .e.

02:20:41.360 --> 02:20:47.940
We use SendSpace with a password. And we intend

02:20:47.940 --> 02:20:54.280
to keep those files up for seven days with that

02:20:54.280 --> 02:20:59.700
password. And the password may not be the best,

02:20:59.799 --> 02:21:06.559
but if we find that you've given everything out,

02:21:10.670 --> 02:21:15.110
You are removed from the network, and you don't

02:21:15.110 --> 02:21:22.389
get anything else. Okay? So, gated and revocable.

02:21:24.590 --> 02:21:29.610
Policy violation results in removal. No appeals

02:21:29.610 --> 02:21:34.649
loop. I'm sorry. That just goes back to what

02:21:34.649 --> 02:21:37.370
I was just saying. If we find out you do it,

02:21:37.389 --> 02:21:42.379
you're gone. You tell me I didn't know. Well,

02:21:42.600 --> 02:21:50.100
by signing up, you agree. If you legitimately

02:21:50.100 --> 02:21:58.700
didn't know, I could, in theory, give you another

02:21:58.700 --> 02:22:06.420
try and say, don't you ever do that again. This

02:22:06.420 --> 02:22:10.979
will be your one and only warning. But in theory,

02:22:11.120 --> 02:22:17.299
I don't call people. If I find out that you're

02:22:17.299 --> 02:22:21.479
doing something that you're not supposed to be

02:22:21.479 --> 02:22:27.000
doing, there is no appeal. I just remove you.

02:22:27.059 --> 02:22:31.459
I will let the administrator know why, and that

02:22:31.459 --> 02:22:36.159
is just done. We don't even contact you. That's

02:22:36.159 --> 02:22:46.579
it. This means that we are security through restraint,

02:22:46.819 --> 02:22:52.879
not expansion into something we don't need. Do

02:22:52.879 --> 02:22:55.420
you know any other company that can say that?

02:22:59.200 --> 02:23:03.700
I would like to know. If you know of any company

02:23:03.700 --> 02:23:11.979
that can say, well, we have data, but... We know

02:23:11.979 --> 02:23:20.559
exactly where it is, how it works, and if a customer

02:23:20.559 --> 02:23:23.700
violates our terms, we know exactly what to do.

02:23:24.739 --> 02:23:30.799
Yes, in theory, Gmail, you can revoke the email

02:23:30.799 --> 02:23:38.010
address or Yahoo or any other big provider. But

02:23:38.010 --> 02:23:40.909
all one has to do is sign up for another email

02:23:40.909 --> 02:23:48.110
account and they're back in. If they were to

02:23:48.110 --> 02:23:52.649
sign back up from Envy, we would have the right

02:23:52.649 --> 02:23:59.069
to refuse them based on the fact that they violated

02:23:59.069 --> 02:24:14.510
terms. Let me know. The question again is, do

02:24:14.510 --> 02:24:18.870
you know any other company that can say that

02:24:18.870 --> 02:24:23.889
when it says, this means that we are security

02:24:23.889 --> 02:24:28.209
through restraint, not expansion into something

02:24:28.209 --> 02:24:44.040
we don't need. Menve versus modern cloud platforms.

02:24:45.260 --> 02:24:52.180
Modern companies typically centralize identity

02:24:52.180 --> 02:24:58.159
and data, depend on third -party providers, accumulate

02:24:58.159 --> 02:25:09.840
decades of unused data, Prioritize growth over

02:25:09.840 --> 02:25:13.399
control. Oh, we want as many customers as we

02:25:13.399 --> 02:25:17.680
can. We don't know anything about what's going

02:25:17.680 --> 02:25:20.299
on with our data. I mean, we have some idea,

02:25:20.459 --> 02:25:33.760
but we're here to make money. Prioritize growth

02:25:33.760 --> 02:25:39.920
over control. Menve typically avoids certain

02:25:39.920 --> 02:25:47.260
things which may include large credential databases.

02:25:47.739 --> 02:25:53.379
We tried the password protected idea with our

02:25:53.379 --> 02:25:58.799
website and our rosters, but nobody really fell

02:25:58.799 --> 02:26:04.489
for that. We have a very explicit... we don't

02:26:04.489 --> 02:26:07.090
understand a lot of this, just make it work for

02:26:07.090 --> 02:26:16.209
us type of people. So that was abandoned. So

02:26:16.209 --> 02:26:24.389
we tried that. API -driven exposure. We don't

02:26:24.389 --> 02:26:32.110
use any APIs. At least not that I'm aware of.

02:26:33.639 --> 02:26:36.120
If I am, somebody tell me, but I'm not aware

02:26:36.120 --> 02:26:46.200
of any API issues. Third -party trackers or analytics.

02:26:46.799 --> 02:26:51.360
There may be Google or other things on our blog,

02:26:51.559 --> 02:27:01.399
but that's blog -related, not site -related.

02:27:01.420 --> 02:27:04.610
This allows you to like. you know, things and

02:27:04.610 --> 02:27:07.569
do things on social media. I want people to be

02:27:07.569 --> 02:27:12.610
able to do that and do that freely by choice.

02:27:15.350 --> 02:27:23.110
But I don't track any of that. So third -party

02:27:23.110 --> 02:27:29.209
trackers or analytics, we don't really track

02:27:29.209 --> 02:27:33.459
people. We allow you to post to Facebook and

02:27:33.459 --> 02:27:38.059
Twitter slash X or any other social media that's

02:27:38.059 --> 02:27:45.340
available there, but that's not my problem. I

02:27:45.340 --> 02:27:50.500
expect it to only share when you share. What

02:27:50.500 --> 02:27:53.139
it does outside of my network, I have no control

02:27:53.139 --> 02:28:02.139
over. OAuth token sprawl. We don't use OAuth.

02:28:05.760 --> 02:28:11.219
If OAuth is there, it's directly with the site.

02:28:11.399 --> 02:28:16.479
So if the site asks you to log in, you clicked

02:28:16.479 --> 02:28:19.680
on the Facebook button, it's asking you to do

02:28:19.680 --> 02:28:28.729
that, not me. Public always -on endpoints. Well,

02:28:28.850 --> 02:28:32.729
we know email and other infrastructure has endpoints,

02:28:32.829 --> 02:28:46.469
but beyond that, that's it. Don't know offhand

02:28:46.469 --> 02:28:51.010
if we've got any always -on infrastructure that...

02:28:51.010 --> 02:28:56.090
I mean, antivirus and malware prevention and

02:28:56.090 --> 02:29:00.090
firewall. are always going to be there. But besides

02:29:00.090 --> 02:29:06.170
that, there's nothing that I'm aware of that

02:29:06.170 --> 02:29:12.489
we're running. So, what does this mean? We have

02:29:12.489 --> 02:29:18.370
a dramatically smaller attack surface. All passwords,

02:29:18.610 --> 02:29:23.729
where possible, are secure. So all of the email

02:29:23.729 --> 02:29:28.799
passwords... All of the mailing list passwords

02:29:28.799 --> 02:29:46.920
and all of the access points to get at other

02:29:46.920 --> 02:29:51.399
email accounts or so forth are password protected.

02:30:03.520 --> 02:30:07.239
The first major breach that might be familiar

02:30:07.239 --> 02:30:12.280
is the Marriott breach. This is one of many big

02:30:12.280 --> 02:30:15.700
breaches and was within the early days similar

02:30:15.700 --> 02:30:20.360
to Target and other companies in that time. Here

02:30:20.360 --> 02:30:35.510
is what happened with Marriott. Legacy systems

02:30:35.510 --> 02:30:45.549
stitched together. Attackers remained undetected

02:30:45.549 --> 02:30:54.110
for years. I will repeat that. Attackers remained

02:30:54.110 --> 02:31:01.020
undetected for years. And this is not the first

02:31:01.020 --> 02:31:11.100
time that this has been an issue. Where attackers

02:31:11.100 --> 02:31:19.760
were in somewhere for a length of time. If an

02:31:19.760 --> 02:31:22.219
attacker is in there more than a day, you've

02:31:22.219 --> 02:31:30.459
got a problem. I could see a day be acceptable

02:31:30.459 --> 02:31:41.440
for the fact that it takes time for you to realize

02:31:41.440 --> 02:31:46.959
what's going on, the right tools email you or

02:31:46.959 --> 02:31:51.600
contact you through methods, and it takes you

02:31:51.600 --> 02:31:56.959
time to go figure out what's going on. So if

02:31:57.149 --> 02:32:04.510
a day or two or whatever would be fine but weeks

02:32:04.510 --> 02:32:26.739
months years seems a little sketchy to me So

02:32:26.739 --> 02:32:30.139
attackers remained undetectable for years. Next

02:32:30.139 --> 02:32:33.680
item in this list is no clear understanding where

02:32:33.680 --> 02:32:38.659
data lived. I think we're starting to see that

02:32:38.659 --> 02:32:45.040
in the various articles that we cover. If you

02:32:45.040 --> 02:32:49.340
look at the blog and you see the breached data,

02:32:49.500 --> 02:32:55.610
many articles state they didn't know. What was

02:32:55.610 --> 02:33:07.930
taken? What? How can you not know what is taken?

02:33:14.850 --> 02:33:29.030
I definitely find that hard to believe. Because

02:33:29.030 --> 02:33:35.129
I do. I know exactly where my data lives. If

02:33:35.129 --> 02:33:37.809
this computer died tomorrow and I needed to get

02:33:37.809 --> 02:33:45.469
another one, am I also able to get somebody to

02:33:45.469 --> 02:33:52.209
take the drive I'm using, put it in the new computer,

02:33:52.329 --> 02:34:05.219
as well as have the other? Drive work. Then I

02:34:05.219 --> 02:34:09.760
know exactly where my data is. I know what is

02:34:09.760 --> 02:34:25.500
in all of my folders. All right. So what actually

02:34:25.500 --> 02:34:29.409
happened? They didn't know where their data was

02:34:29.409 --> 02:34:34.569
and who can access it. That is the failure mode

02:34:34.569 --> 02:34:39.549
right there. Right? That's what I was just talking

02:34:39.549 --> 02:34:45.790
about. They didn't know where their data was

02:34:45.790 --> 02:34:55.190
and who had access to it. Who agrees? Send me

02:34:55.190 --> 02:35:02.840
an email. Send me an iMessage, whatever. I'm

02:35:02.840 --> 02:35:10.959
curious. Because this definitely sounds strange

02:35:10.959 --> 02:35:23.600
to me. This definitely sounds strange to me.

02:35:34.769 --> 02:35:38.209
Email imessage, J -A -R -E -D -R -I -M -E -R

02:35:38.209 --> 02:35:43.209
at 986themyx .com. Text or WhatsApp 804 -442

02:35:43.209 --> 02:36:40.930
-6975. This can't be good. Can it? When we come

02:36:40.930 --> 02:36:45.610
back, we're going to play a track and then we're

02:36:45.610 --> 02:36:54.829
going to get into our next segment. 23 and me.

02:36:56.170 --> 02:37:01.989
And that completely collapsed. And you can search

02:37:01.989 --> 02:37:06.750
it with or without spaces. Numbers 23 and A -N

02:37:06.750 --> 02:37:36.750
-D me. Okay? This is bad. Let's play Home Free,

02:37:36.870 --> 02:38:13.500
since this seems to be Home Free today. Let's

02:38:13.500 --> 02:38:25.459
see, what do I want to play? I think I will play

02:38:25.459 --> 02:38:42.819
their track, Full of Cheer. We will continue

02:38:42.819 --> 02:38:45.260
with more of the Security Box in just a moment.

02:38:48.200 --> 02:39:12.149
Across the Jared Reimer Radio Network. It seems

02:39:12.149 --> 02:39:16.770
that all she left behind was a note that said

02:39:16.770 --> 02:39:22.950
I'm sorry I must go. Did she really leave me?

02:39:41.140 --> 02:39:45.500
Christmas. I'm gonna have some money come new

02:39:45.500 --> 02:39:49.479
year. Bells are ringing, choirs are singing,

02:39:49.639 --> 02:39:53.020
and my pockets are jingling. My baby left me

02:39:53.020 --> 02:41:56.170
full of at great length on this podcast about

02:41:56.170 --> 02:42:04.770
23andMe. And there's a lot of coverage out there.

02:42:05.649 --> 02:42:07.989
If you don't read from us, you'll find plenty

02:42:07.989 --> 02:42:14.649
of it. So we've given you a lot of coverage of

02:42:14.649 --> 02:42:20.110
23andMe, and it was nothing but bad. You can

02:42:20.110 --> 02:42:23.239
search it out in the podcast and blog. at your

02:42:23.239 --> 02:42:28.239
own time. But we knew that they handled lots

02:42:28.239 --> 02:42:32.959
of information that a lot of companies may not

02:42:32.959 --> 02:42:40.379
have. This includes extremely sensitive genetic

02:42:40.379 --> 02:42:46.620
data, weak authentication assumptions, credential

02:42:46.620 --> 02:42:55.659
reuse, not adequate mitigated, not adequately

02:42:55.659 --> 02:43:03.159
mitigated, excuse me, over trust in account boundaries,

02:43:03.319 --> 02:43:11.500
relatives data exposed through shared access.

02:43:16.760 --> 02:43:39.430
So nobody sent any boundaries. Seriously? This

02:43:39.430 --> 02:43:49.129
has to be bad. There were no boundaries set and

02:43:49.129 --> 02:43:54.969
we were expected to trust them. That was the

02:43:54.969 --> 02:43:58.899
ultimate failure. Kim Commando has mentioned

02:43:58.899 --> 02:44:02.920
many times that you should remove your info from

02:44:02.920 --> 02:44:08.079
there and gives instructions on how. Unless they're

02:44:08.079 --> 02:44:11.579
now completely gone, I'd still consider doing

02:44:11.579 --> 02:44:19.280
this. That's my recommendation, but I've never

02:44:19.280 --> 02:44:22.040
used the thing. I've heard nothing but bad things

02:44:22.040 --> 02:44:27.079
about it. It had a good idea. But it's already

02:44:27.079 --> 02:44:41.139
been bought. It's already been bought. So...

02:45:14.859 --> 02:45:33.659
Yeah. Seriously. Why Menvi didn't fail the same

02:45:33.659 --> 02:45:40.819
way. Data minimization by design. No assumption

02:45:40.819 --> 02:45:48.860
of good behavior. Access is contextual and revocable.

02:45:50.079 --> 02:45:54.520
Small blast radius when something goes wrong.

02:45:55.239 --> 02:46:02.639
And even if we had 1 ,500 members. Even if we

02:46:02.639 --> 02:46:07.920
had 1 ,500 members, 2 ,000 members, 5 ,000 members.

02:46:12.860 --> 02:46:20.659
It's all controlled. Human oversight instead

02:46:20.659 --> 02:46:30.159
of automation, only enforcement. The key takeaway

02:46:30.159 --> 02:46:36.659
is this. Menvi limits damage by limiting its

02:46:36.659 --> 02:46:42.579
access footprint. Data may be in places like

02:46:42.579 --> 02:46:46.579
Dropbox, text files, and other places that could

02:46:46.579 --> 02:46:51.100
be used to disseminate journals and rosters,

02:46:51.120 --> 02:46:55.399
but it's... all controlled and we know where

02:46:55.399 --> 02:46:58.680
it all is. I said that before. I think that's

02:46:58.680 --> 02:47:06.239
worth saying again. Every single piece of it.

02:47:09.280 --> 02:47:14.739
Link -based file sharing versus password -gated

02:47:14.739 --> 02:47:21.059
access. This is key. As stated above, There are

02:47:21.059 --> 02:47:25.120
things in Dropbox and things where we know where

02:47:25.120 --> 02:47:29.840
it is. That could be in password -protected directories,

02:47:29.879 --> 02:47:35.360
not a platform that is well -known and trusted.

02:47:35.799 --> 02:47:42.379
On a platform, excuse me, that is well -known

02:47:42.379 --> 02:47:57.389
and trusted. You can set a password. You can

02:47:57.389 --> 02:48:03.649
expire a file. It is accessible, even though

02:48:03.649 --> 02:48:08.209
the desktop app is long gone now. You can still

02:48:08.209 --> 02:48:15.950
use it. Password protection does include a premium

02:48:15.950 --> 02:48:22.610
subscription, though. Services that can be trusted

02:48:22.610 --> 02:48:26.829
that have these capabilities include SendSpace

02:48:26.829 --> 02:48:31.790
and WeTransfer. You send it may have it too under

02:48:31.790 --> 02:48:37.569
paid. You can check. And of course there are

02:48:37.569 --> 02:48:44.159
others that I may not know about. Even if you

02:48:44.159 --> 02:48:48.459
use the free version of WeTransfer, links expire

02:48:48.459 --> 02:48:52.040
within seven days and it can be controlled by

02:48:52.040 --> 02:48:58.760
only giving those links to people within the

02:48:58.760 --> 02:49:03.159
network and having explicit controls if that

02:49:03.159 --> 02:49:07.979
boundary is distrusted. That this link goes out

02:49:07.979 --> 02:49:14.540
past this list. We find out about it, you're

02:49:14.540 --> 02:49:23.399
gone. We're not going to go track you down. With

02:49:23.399 --> 02:49:27.299
Retransfer, anyone who has a link can send it

02:49:27.299 --> 02:49:34.479
to anyone else, regardless of our policies. But

02:49:34.479 --> 02:49:38.200
Menvee has a clear policy if you ever decide

02:49:38.200 --> 02:49:43.040
to do that. Until the link expires, it can be

02:49:43.040 --> 02:49:47.559
forwarded indefinitely. This is a big risk when

02:49:47.559 --> 02:49:52.739
a roster is meant for a community. Tell me, is

02:49:52.739 --> 02:49:56.559
there any per -user accountability using this

02:49:56.559 --> 02:50:03.579
model? While there is an expiration of 7 days,

02:50:04.059 --> 02:50:09.760
the link being public available, public and available,

02:50:10.180 --> 02:50:21.479
maybe, may be the missing link between privacy

02:50:21.479 --> 02:50:26.620
of the data versus it getting out. Menvee has

02:50:26.620 --> 02:50:33.299
at least 500 members, a lot of whom get our info

02:50:33.299 --> 02:50:38.370
online through attachments or links. The link

02:50:38.370 --> 02:50:46.729
group is small, but even if it were bigger, that

02:50:46.729 --> 02:50:52.930
is a big problem with link sending. When it comes

02:50:52.930 --> 02:50:57.309
to the password model we use, password -gated

02:50:57.309 --> 02:51:03.049
access tied to membership, violations have consequences,

02:51:03.750 --> 02:51:09.799
access can be revoked, Policy reinforces technical

02:51:09.799 --> 02:51:17.319
controls. The conclusion of this segment is simple.

02:51:18.440 --> 02:51:23.719
Community -based security works when the community

02:51:23.719 --> 02:51:30.319
is small and intentional. Big communities could,

02:51:30.420 --> 02:51:34.700
in theory, find a model similar to this without

02:51:34.700 --> 02:51:39.280
using software that could, in theory, be problematic.

02:51:42.979 --> 02:51:48.780
Zero trust versus reality. Did you know that

02:51:48.780 --> 02:51:54.360
zero trust is actually a marketing term? I didn't,

02:51:54.360 --> 02:51:59.059
but we all learn something every day. Here are

02:51:59.059 --> 02:52:03.770
some bullet points about this. Many breached

02:52:03.770 --> 02:52:13.370
companies were technically compliant. Okay, that's

02:52:13.370 --> 02:52:26.149
at least a good sign. Compliance equals safety.

02:52:31.370 --> 02:52:35.610
Or not equal to safety. Is that supposed to be

02:52:35.610 --> 02:52:44.969
not equal to? I think so. I think it was meant

02:52:44.969 --> 02:52:57.770
as not equal. All right. Menvee doesn't advertise

02:52:57.770 --> 02:53:06.680
zero trust. It practices least exposure. It practices

02:53:06.680 --> 02:53:32.540
that. We don't claim to be on an SAS. So... I

02:53:32.540 --> 02:53:41.120
want a file because I want to see something.

02:53:48.100 --> 02:54:04.489
Where are we here? It is not equal to. Alright,

02:54:04.530 --> 02:54:19.610
so I learned a new sign. Okay. If you take anything

02:54:19.610 --> 02:54:23.370
out of this discussion, it's this. We've never

02:54:23.370 --> 02:54:27.510
been breached because we never built something

02:54:27.510 --> 02:54:36.059
worth breaching at scale. Again, we've never

02:54:36.059 --> 02:54:39.620
been breached because we never built something

02:54:39.620 --> 02:54:47.940
worth breaching at scale. Where Menvee and JRN

02:54:47.940 --> 02:54:56.680
are stronger than big tech. Collect less data.

02:54:57.379 --> 02:55:02.340
Our forms, if available, name, phone number,

02:55:02.750 --> 02:55:05.569
email address, whether you're reporting a bug,

02:55:05.750 --> 02:55:12.290
and what exactly do you need. Nothing more. Nothing

02:55:12.290 --> 02:55:34.739
more. That's it. Share less data. We don't share

02:55:34.739 --> 02:55:39.440
at all, but if we share, we only share what you

02:55:39.440 --> 02:55:50.040
provide us. I .e., if the application asks for

02:55:50.040 --> 02:55:52.659
name, address, phone number, etc., that gets

02:55:52.659 --> 02:56:02.440
shared. But we do not ask for Social security

02:56:02.440 --> 02:56:14.680
numbers. At all. Why? I know in early business

02:56:14.680 --> 02:56:20.299
days it made sense. But I don't even do that

02:56:20.299 --> 02:56:55.979
now either. That is that. Automate less trust.

02:56:56.219 --> 02:57:01.399
We don't automate anything. We have a form processor.

02:57:05.040 --> 02:57:21.360
But that's it. That is all we have. And I only

02:57:21.360 --> 02:57:26.479
bring on people who I trust. I don't just give

02:57:26.479 --> 02:57:34.100
data to everybody. Keep humans in the loop. If

02:57:34.100 --> 02:57:42.040
there's something wrong, we tell you. It has

02:57:42.040 --> 02:57:45.940
to be that way. Even if we update our website.

02:57:52.100 --> 02:57:57.280
If the entire network's down, and I can't tell

02:57:57.280 --> 02:58:03.290
you, We put out a message when everything comes

02:58:03.290 --> 02:58:12.530
back up. Treat members as people, not metrics.

02:58:19.270 --> 02:58:23.510
I don't ask for things I don't need. I don't

02:58:23.510 --> 02:58:32.219
call people unless I need to. This is who we

02:58:32.219 --> 02:58:39.200
are. We treat you like a person. I tell you who

02:58:39.200 --> 02:58:43.639
I am and why I'm calling. You tell me. I'm on

02:58:43.639 --> 02:58:48.040
the do not call list. And I say, we already have

02:58:48.040 --> 02:58:53.440
your information. We did not get your information

02:58:53.440 --> 02:58:59.420
through automated dialing systems. We did not

02:58:59.420 --> 02:59:03.159
get it. From somewhere. You signed up at some

02:59:03.159 --> 02:59:14.700
point. That's how we have your data. That's how

02:59:14.700 --> 02:59:23.059
it works. People usually relax when I say, you

02:59:23.059 --> 02:59:26.139
signed up at some point. This is why we're calling.

02:59:30.279 --> 02:59:36.260
I understand why people don't answer their phones.

02:59:37.579 --> 02:59:46.360
I'm one of them. If you need to call me back

02:59:46.360 --> 02:59:50.719
or you need to verify who I am by calling me

02:59:50.719 --> 02:59:54.719
back, that is perfectly fine. If I leave a message

02:59:54.719 --> 02:59:57.120
and then you call back and you hear my voice

02:59:57.120 --> 03:00:04.459
with my name, That's perfectly fine. Or if the

03:00:04.459 --> 03:00:08.959
number's available, you know, I pick up and talk

03:00:08.959 --> 03:00:16.299
to you. Do you like these items? And are we missing

03:00:16.299 --> 03:00:23.540
any? Which of the above five items resonate with

03:00:23.540 --> 03:00:28.100
you? I want to know. So again, the five items

03:00:28.100 --> 03:00:37.639
were... Collect less data. Share less data. Automate

03:00:37.639 --> 03:00:43.159
less trust. Keep humans in the loop and treat

03:00:43.159 --> 03:00:55.120
members as people, not metrics. Fair critiques

03:00:55.120 --> 03:01:04.520
and transparency. earlier web era Menvi was born

03:01:04.520 --> 03:01:12.700
online in 2003 and my business post dates SSI

03:01:12.700 --> 03:01:18.020
when I left and became the JRN and even before

03:01:18.020 --> 03:01:29.329
SSI was closed for good in 2018 Policies reflect

03:01:29.329 --> 03:01:34.909
an earlier web era. Language is informal. No

03:01:34.909 --> 03:01:38.329
legal jargon. This is exactly what we do with

03:01:38.329 --> 03:01:46.270
our info. With your info. How we deal with it.

03:01:48.950 --> 03:01:54.030
Manual enforcement requires effort. Phone -based

03:01:54.030 --> 03:02:00.409
contact is intentional. but notable. What resonates

03:02:00.409 --> 03:02:04.489
with you? Here is the important distinction.

03:02:05.870 --> 03:02:10.729
These are governance issues, not systemic security

03:02:10.729 --> 03:02:20.770
risks. The core theme. Here's the core theme

03:02:20.770 --> 03:02:27.020
that we want you to have. From this episode.

03:02:28.200 --> 03:02:32.639
The companies that keep getting breached aren't

03:02:32.639 --> 03:02:42.299
careless. They're overbuilt. Overexposed and

03:02:42.299 --> 03:02:46.440
addicted to scale. Let's see how many people

03:02:46.440 --> 03:02:50.680
we can get so we can make as much money as we

03:02:50.680 --> 03:02:56.020
want. Or we can. We'll protect it. The best we

03:02:56.020 --> 03:03:01.760
can, but... We'll say we'll promise, but we can't

03:03:01.760 --> 03:03:05.379
promise anything. But they don't tell you that,

03:03:05.520 --> 03:03:17.459
do they? Menvi survives because it never tried

03:03:17.459 --> 03:03:22.020
to be big. I think I can say the same for the

03:03:22.020 --> 03:03:31.180
JRN. And I ask for thoughts. In closing, security

03:03:31.180 --> 03:03:39.440
isn't about how modern your tools are. It's about

03:03:39.440 --> 03:03:43.420
how little damage is possible when something

03:03:43.420 --> 03:03:48.760
goes wrong. Let's discuss any final thoughts.

03:03:52.360 --> 03:03:54.879
And I know we took thoughts before everybody

03:03:54.879 --> 03:04:04.120
left. But if you have any final thoughts, then

03:04:04.120 --> 03:04:17.620
I do want to hear from you. Email iMessage, J

03:04:17.620 --> 03:04:22.690
-A -R -E -D. R -I -M -E -R at 986themix .com

03:04:22.690 --> 03:04:33.569
or tech at m -e -n -v -i .org Text or WhatsApp

03:04:33.569 --> 03:04:51.399
804 -442 -6975 I look forward to hearing from

03:04:51.399 --> 03:05:01.399
you. You know, even on a phone line like Livewire,

03:05:01.559 --> 03:05:08.500
I treat personal information the same way there

03:05:08.500 --> 03:05:17.760
as I do for my own business. Anybody gives me

03:05:17.760 --> 03:05:30.409
a phone number there? It is confidential. I don't

03:05:30.409 --> 03:05:36.069
give it out to anybody. I got a voicemail today.

03:05:36.450 --> 03:05:40.409
I can call the number back since I might know

03:05:40.409 --> 03:05:46.549
who it is, but they didn't say who it was. But

03:05:46.549 --> 03:05:48.790
I can technically call them back and they can

03:05:48.790 --> 03:05:53.020
say who's this. I can say, this is Jared. I got

03:05:53.020 --> 03:06:07.299
a phone call from this number. That is the callback

03:06:07.299 --> 03:06:11.260
model we have. You leave a message, we have the

03:06:11.260 --> 03:06:14.340
right to call you back. Once we do that, we discard

03:06:14.340 --> 03:06:19.709
your phone number. Keep it on file. It may be

03:06:19.709 --> 03:06:28.510
in logs, but we don't look at logs. Why? If something

03:06:28.510 --> 03:06:33.270
goes bad, we may try to look at logs, but they're

03:06:33.270 --> 03:06:38.969
so detailed. I don't know what I'm looking for.

03:06:48.079 --> 03:07:18.319
It is crazy. Absolutely crazy. Sometimes, I wonder.

03:07:29.840 --> 03:07:35.760
I would definitely love to hear from each and

03:07:35.760 --> 03:07:42.059
every one of you. And you can let me know what

03:07:42.059 --> 03:08:26.100
your thoughts are. I just realized, well, I opened

03:08:26.100 --> 03:08:33.719
the wrong file anyway, but I noticed that I didn't

03:08:33.719 --> 03:08:45.260
do something right. I think I've covered everything

03:08:45.260 --> 03:09:55.709
that is in my podcast list. So... Yeah. Crazy.

03:10:25.069 --> 03:10:37.870
Oh, that's what it was. Okay. So, next week,

03:10:37.950 --> 03:10:50.049
we will be taking off and 269 personal health

03:10:50.049 --> 03:10:59.459
information And how companies don't protect it

03:10:59.459 --> 03:11:10.940
like they claim they do. That has got to be something

03:11:10.940 --> 03:11:13.559
that I don't think anybody's covered. We hear

03:11:13.559 --> 03:11:20.819
all these breaches. But it's always the same.

03:11:22.030 --> 03:11:25.069
A million plus people, two million people, whatever.

03:11:26.170 --> 03:11:30.709
We're sorry. We're going to offer this. We don't

03:11:30.709 --> 03:11:32.629
exactly know what happened, but we're going to

03:11:32.629 --> 03:11:43.090
make sure we don't have that happen again. It's

03:11:43.090 --> 03:12:01.340
the same every time. I'm Jared Reimer saying

03:12:01.340 --> 03:12:11.040
thanks so much for listening. Let's go ahead

03:12:11.040 --> 03:12:42.870
and close things out for today. And Let's play

03:12:42.870 --> 03:12:54.270
some Quixente from their Sleep Cycles album.

03:12:59.370 --> 03:13:02.069
It's a four -track album, and I'll play a couple

03:13:02.069 --> 03:13:07.469
of tracks and call it good. We've got closing

03:13:07.469 --> 03:13:14.989
material as well Preston will close us out and

03:13:14.989 --> 03:13:23.229
I will see everybody next time right here on

03:13:23.229 --> 03:13:28.690
the Jared Reimer radio network your comments

03:13:28.690 --> 03:13:37.090
on this if you want will be accepted and I appreciate

03:13:37.090 --> 03:13:42.090
whatever everybody has to say. You have no wrong

03:13:42.090 --> 03:13:49.870
answers. You can tell me I'm wrong. And I'm okay

03:13:49.870 --> 03:13:54.350
with that. But if we don't have a healthy discussion

03:13:54.350 --> 03:14:00.190
on a lot of these items, then we're always going

03:14:00.190 --> 03:14:06.020
to be talking about the same old things. Stay

03:14:06.020 --> 03:14:10.780
tuned for intermediate podcasting between episodes

03:14:10.780 --> 03:14:16.620
where we'll put out videos of things across the

03:14:16.620 --> 03:14:24.860
landscape and much more. Until then, we'll be

03:14:24.860 --> 03:14:30.100
back with a live program in two weeks. See you

03:14:30.100 --> 03:14:42.819
then. VirusTotal is a website that allows you

03:14:42.819 --> 03:14:56.280
to submit links, files, and other pieces of information,

03:14:56.340 --> 03:15:01.520
including domains and IP addresses for analysis.

03:15:02.079 --> 03:15:10.860
It's a Google -ran product. They've changed their

03:15:10.860 --> 03:15:17.440
website a little bit There is going to be an

03:15:17.440 --> 03:15:23.959
unlabeled button Underneath the enter URL IP

03:15:23.959 --> 03:15:30.899
or domain Edit box which will allow you to upload

03:15:30.899 --> 03:15:36.879
a file for analysis No matter what you submit

03:15:37.440 --> 03:15:43.379
The service in question allows you to get things

03:15:43.379 --> 03:15:48.280
analyzed. Is this safe? Is this website safe?

03:15:49.120 --> 03:15:57.040
Is the file that I'm dealing with safe? My program

03:15:57.040 --> 03:15:59.899
I use on my computer didn't say anything, but

03:15:59.899 --> 03:16:05.260
I want to make sure this website does just that.

03:16:06.120 --> 03:16:10.440
The higher the number, the bigger the problem.

03:16:10.540 --> 03:16:16.500
For example, if it says 30 out of 90, you should

03:16:16.500 --> 03:16:22.899
probably be concerned. If a website you want

03:16:22.899 --> 03:16:28.020
to go to says 1 or 2 out of 90, you could probably

03:16:28.020 --> 03:16:32.959
go to it, but just be careful and pay attention

03:16:32.959 --> 03:16:37.920
to what you're doing. The website, again, is

03:16:37.920 --> 03:16:43.540
virustotal .com, just as it's spelled. V -I -R

03:16:43.540 --> 03:16:49.739
-U -S -T -O -T -A -L dot com. Find a link on

03:16:49.739 --> 03:16:53.899
emailhostsecurity .com on our resources page.

03:17:09.229 --> 03:17:12.370
Hello there, and thank you for listening to Security

03:17:12.370 --> 03:17:16.549
Box. This is Preston Gaylor, contributor and

03:17:16.549 --> 03:17:19.989
one of your announcers for this program. We hope

03:17:19.989 --> 03:17:22.690
you enjoyed today's program, and we hope it brought

03:17:22.690 --> 03:17:25.790
you some value, whether you are in the industry

03:17:25.790 --> 03:17:28.190
for a long time or if you're just getting started.

03:17:28.649 --> 03:17:32.790
We appreciate your support, patience, listenership,

03:17:32.790 --> 03:17:37.549
and desire to learn. If you have any questions,

03:17:38.110 --> 03:17:41.889
or want to relive past podcasts, please look

03:17:41.889 --> 03:17:46.409
up the technology blog and podcast in TSB on

03:17:46.409 --> 03:17:50.309
your preferred podcast platform, or log on to

03:17:50.309 --> 03:17:54.250
emailhostsecurity .com and look for the Security

03:17:54.250 --> 03:17:58.709
Box podcast directory. You can also find resources

03:17:58.709 --> 03:18:02.770
and blog posts to what we talked about today

03:18:02.770 --> 03:18:07.200
over at jaredtech .help. You will also find copies

03:18:07.200 --> 03:18:11.180
of each episode posted there as well. If you

03:18:11.180 --> 03:18:13.659
enjoy what we do, please consider sharing with

03:18:13.659 --> 03:18:17.819
a friend, family member, or maybe a new potential

03:18:17.819 --> 03:18:21.219
listener so that way they can stay safe and sane

03:18:21.219 --> 03:18:25.139
in this crazy world known as tech and cybersecurity.

03:18:28.899 --> 03:18:32.079
And don't forget as well, if you have any questions,

03:18:32.260 --> 03:18:34.799
comments, or suggestions, we'd love to hear from

03:18:34.799 --> 03:18:40.430
you. Simply go to jaredtech .help or jaredreimer

03:18:40.430 --> 03:18:44.610
.net and on that site, you can look for links

03:18:44.610 --> 03:18:49.049
around the site and there's a contact page where

03:18:49.049 --> 03:18:51.629
you can get in touch with him directly. You may

03:18:51.629 --> 03:18:59.909
also reach out to 888 -405 -7524 or 818 -527

03:18:59.909 --> 03:19:04.420
-4754 and leave a voicemail. with your comments

03:19:04.420 --> 03:19:08.139
or questions. And if he's available, he will

03:19:08.139 --> 03:19:12.139
call you back or take your call during a day

03:19:12.139 --> 03:19:16.799
when it is convenient for him. Oh, and one more

03:19:16.799 --> 03:19:20.120
thing. We cannot do this program without you,

03:19:20.120 --> 03:19:23.319
the listener, in mind. So if you're able, please

03:19:23.319 --> 03:19:26.739
consider donating to our work by going to jaredreimer

03:19:26.739 --> 03:19:32.620
.net and look for a donation icon around the

03:19:32.620 --> 03:19:38.620
site. Thank you for listening. And as always,

03:19:38.780 --> 03:19:42.260
don't click on shit. Know where you're going.

03:19:43.000 --> 03:19:47.299
And make sure you spread the messages to anyone

03:19:47.299 --> 03:19:51.399
in your circle. Because tomorrow is never promised.

03:19:53.940 --> 03:19:57.739
People are getting owned every day. And you might

03:19:57.739 --> 03:20:02.760
be next. So again, thank you for your time, your

03:20:02.760 --> 03:20:07.299
patronage, and your support. Make it a good and

03:20:07.299 --> 03:20:20.010
safe day. Would you like to join us on the Security

03:20:20.010 --> 03:20:24.569
Box email list? Several of us will post articles,

03:20:24.790 --> 03:20:28.049
several may comment on the articles, and you're

03:20:28.049 --> 03:20:30.889
welcome to join us to talk about what interests

03:20:30.889 --> 03:20:35.170
you. Post articles, join the discussion, and

03:20:35.170 --> 03:20:38.729
maybe learn something that you might not have

03:20:38.729 --> 03:20:43.309
learned before. The subscription process is fairly

03:20:43.309 --> 03:20:48.360
easy. Just send a blank email to thesecuritybox

03:20:48.360 --> 03:20:56.200
-subscribe at 986themix .com or find a link to

03:20:56.200 --> 03:21:01.159
the security box at 986themix .com under the

03:21:01.159 --> 03:21:07.059
list for social media. This service is part of

03:21:07.059 --> 03:21:33.219
986themix's email list. Come join us today. Want

03:21:33.219 --> 03:21:38.200
to join us each week? Well, join us on Team Talk

03:21:38.200 --> 03:21:44.739
on Wednesday, 11 a .m. Pacific Time, 1 p .m.

03:21:44.760 --> 03:21:49.799
Central Time, where you can participate on the

03:21:49.799 --> 03:21:56.399
live taping of The Security Box. What server

03:21:56.399 --> 03:21:59.860
are we going to be on? Great question. We're

03:21:59.860 --> 03:22:03.920
going to be on 986 The Mix's Team Talk server,

03:22:04.319 --> 03:22:11.100
whose information can be found at 986themix .com.

03:22:12.670 --> 03:22:15.829
You do need to have an account on this server,

03:22:16.010 --> 03:22:19.649
and if you don't, follow the instructions to

03:22:19.649 --> 03:22:26.530
get one. So come join us each week. 986themix

03:22:26.530 --> 03:22:31.489
.com, our TeamTalk server in the Security Box

03:22:31.489 --> 03:22:36.489
channel. And thank you so much for listening

03:22:36.489 --> 03:22:50.090
to the podcast edition of our program. We would

03:22:50.090 --> 03:22:58.190
like to thank the following podcasts and or news

03:22:58.190 --> 03:23:05.629
websites for the articles in which we may use

03:23:05.629 --> 03:23:13.430
or blog. You may find links to these under podcasts

03:23:13.430 --> 03:23:19.819
and sources we use. On our website at emailhostsecurity

03:23:19.819 --> 03:23:30.180
.com. Ars Technica. Bleeping Computer. Cybernews

03:23:30.180 --> 03:23:40.500
.com. Cybercrime Radio. CyberScoop. Crabs on

03:23:40.500 --> 03:23:46.180
Security. Kim Commando, the Digital Goddess.

03:23:48.170 --> 03:23:55.950
The Cyber Wire from N2K Networks. And the Fish

03:23:55.950 --> 03:24:04.209
Labs blog. If you have found something that is

03:24:04.209 --> 03:24:06.989
not listed here that we should be looking at,

03:24:07.209 --> 03:24:14.250
please let us know by sending an email with the

03:24:14.250 --> 03:24:20.129
link to the main webpage. You may either send

03:24:20.129 --> 03:24:27.870
your email to jaredrimer at 986themix .com or

03:24:27.870 --> 03:24:34.149
tech, that's t -e -c -h at m -e -n -v -i dot

03:24:34.149 --> 03:24:42.389
o -r -g. Thanks, resources, for all you do to

03:24:42.389 --> 03:24:46.389
put the information out so we can share what

03:24:46.389 --> 03:24:50.540
you and others have to say in this industry.

03:24:51.620 --> 03:24:54.959
Thank you for listening to The Security Box.

03:24:55.780 --> 03:25:01.079
This is Jared Reimer. We hope you enjoyed today's

03:25:01.079 --> 03:25:06.399
program, and we hope to see you again on another

03:25:06.399 --> 03:25:12.299
edition of the program next time. We would like

03:25:12.299 --> 03:25:17.459
to thank the following affiliates. For airing

03:25:17.459 --> 03:25:23.840
our program. The main network. 98 .6 The Mix.

03:25:24.020 --> 03:25:28.959
On the independent channel. If you are airing

03:25:28.959 --> 03:25:32.379
our program. And your network is not listed here.

03:25:32.799 --> 03:25:38.639
And you would like us to give you. Credit for

03:25:38.639 --> 03:25:43.739
airing our program. Please contact me. I would

03:25:43.739 --> 03:25:49.520
like to do my best. to make sure that all affiliates

03:25:49.520 --> 03:25:57.079
get credit for airing the program. Please feel

03:25:57.079 --> 03:26:00.680
free to contact me using the contact information

03:26:00.680 --> 03:26:08.159
given during the program. It is open to all listeners,

03:26:08.280 --> 03:26:15.260
no matter what network you're listening on. Now,

03:26:15.770 --> 03:26:19.690
Stay tuned for a few tracks on the independent

03:26:19.690 --> 03:26:25.629
artist side to round out the podcast. See you

03:26:25.629 --> 03:26:31.290
next week. And thanks again for listening.