On Call Sysadmin Podcast #1: AI, Security, and the Future of IT

WEBVTT
00:10.851 --> 00:12.371
All right, welcome to the OnCall SysAdmin
00:13.011 --> 00:14.291
podcast #1.
00:16.411 --> 00:18.211
Given this podcasting, yeah, breaking
00:18.211 --> 00:19.891
ground. Finally happening.
00:21.811 --> 00:23.811
We've been talking about it for years and
00:24.051 --> 00:26.771
it's finally going on to
00:26.771 --> 00:29.011
tape. Here it is. So today we're
00:29.571 --> 00:32.211
going to talk about a couple of relevant
00:32.211 --> 00:33.731
things from the news.
00:36.531 --> 00:38.531
Hopefully a lot of it is tech related,
00:38.531 --> 00:41.331
but you never know what comes up.
00:42.826 --> 00:44.106
of the things that I thought was
00:44.186 --> 00:46.906
interesting this week I came across was,
00:50.106 --> 00:51.386
I guess it's been in the news for a
00:51.386 --> 00:53.306
little while that the data centers
00:55.346 --> 00:57.866
are taking up a lot of extra electricity,
00:57.866 --> 00:59.506
causing power prices to go up, they use a
00:59.506 --> 01:02.386
lot of water. And
01:02.386 --> 01:05.146
now it seems like data
01:05.146 --> 01:07.546
centers are going to do an end round and
01:07.546 --> 01:09.826
start paying you to host a data center on
01:09.826 --> 01:10.906
the side of your house.
01:12.666 --> 01:14.426
What? So I don't know if you've seen
01:14.426 --> 01:17.266
this. Here is Span
01:17.266 --> 01:18.586
and Nvidia.
01:21.306 --> 01:24.266
Than like the power panel
01:24.266 --> 01:26.906
thing? The power panel, exactly right.
01:28.746 --> 01:31.506
So what they're going to do is pay you to
01:31.506 --> 01:33.146
host a data center on the side of your
01:33.146 --> 01:33.706
house.
01:36.186 --> 01:39.146
To what extent is that? Well,
01:39.146 --> 01:42.106
right now the platform looks like it is
01:42.266 --> 01:45.226
a Dell PowerAd server with
01:45.226 --> 01:47.866
liquid cooled Nvidia GPUs,
01:48.266 --> 01:49.946
I think up to 16 of them.
01:53.226 --> 01:55.626
That's crazy. I know, right?
01:55.706 --> 01:57.626
It's pretty interesting. And that way
01:57.626 --> 01:59.106
they don't have to go through the
01:59.106 --> 02:01.066
regulatory red tape of getting a data
02:01.066 --> 02:03.626
center installed, building
02:04.266 --> 02:05.946
out the power infrastructure, which can
02:05.946 --> 02:08.786
take years. And
02:11.226 --> 02:13.786
they pay you for power, they pay you for
02:13.786 --> 02:15.986
the internet, and they pay you just to
02:15.986 --> 02:18.666
host it on the side of your building. So
02:20.426 --> 02:22.906
I don't know to what extent if this is
02:22.906 --> 02:24.306
like something that they're exploring or
02:24.306 --> 02:27.026
if it's officially going live, but. I'm
02:27.026 --> 02:29.386
like, okay, so they pay you for power,
02:29.386 --> 02:31.946
they pay you for internet. So like, is
02:31.946 --> 02:33.666
it, are they installing their own
02:33.666 --> 02:35.426
internet in addition to what you already
02:35.426 --> 02:38.106
have or are they using your
02:38.106 --> 02:39.706
internet and they're paying you back?
02:40.106 --> 02:42.706
Yeah, I don't know. I would imagine that
02:42.706 --> 02:44.106
they would have their own internet,
02:45.866 --> 02:48.266
but I guess that would depend on what you
02:48.266 --> 02:49.306
have coming to your house.
02:51.626 --> 02:54.466
that like AT&T or fiber to the home, for
02:54.466 --> 02:57.306
example, would have in theory only
02:57.306 --> 02:58.906
one wavelength of light coming to your
02:58.906 --> 03:01.466
house, but I don't know if they would be
03:01.466 --> 03:04.266
able to install
03:04.266 --> 03:06.146
another router and you just use their
03:06.146 --> 03:08.466
internet or the other way around. But
03:08.466 --> 03:09.546
they would definitely want to have their
03:09.546 --> 03:10.746
own separated,
03:11.866 --> 03:14.026
isolated internet network that was
03:14.986 --> 03:16.506
separate from your home internet because
03:16.506 --> 03:18.946
they don't wantthose systems coming into
03:18.946 --> 03:20.986
your house or you don't want, they don't
03:20.986 --> 03:22.986
want your traffic coming into their
03:23.706 --> 03:26.346
little hosted data center, quote unquote.
03:27.546 --> 03:29.066
And that seems like it'll get complicated
03:29.066 --> 03:31.546
quick because yeah, I mean, to those
03:31.546 --> 03:33.946
points, either they'd have to install a
03:33.946 --> 03:35.706
whole separate circuit just for their
03:35.706 --> 03:38.506
stuff or they would have to
03:38.506 --> 03:40.666
put in their firewall to then
03:41.066 --> 03:43.226
segment off your home stuff.
03:44.026 --> 03:45.306
Yeah, exactly.
03:47.226 --> 03:48.666
But it seems like a fairly big system.
03:48.666 --> 03:50.266
It's water cooled and I think they have
03:50.266 --> 03:52.346
to actually install a heat pump or
03:53.786 --> 03:55.386
a, I would imagine it's a heat pump
03:55.386 --> 03:57.186
because you would want to keep it warm in
03:57.186 --> 03:59.666
the winter. You don't
04:00.066 --> 04:02.426
want it freezing when it drops to below
04:02.666 --> 04:05.626
0. But it comes with, I
04:05.626 --> 04:06.986
think it comes with its own little air
04:06.986 --> 04:09.066
conditioning unit. The one thing that I
04:09.066 --> 04:11.946
saw somewhere else was that
04:13.386 --> 04:15.426
the noise coming off the system was over
04:15.426 --> 04:16.346
100 decibels.
04:18.666 --> 04:21.626
Which, I'm not sure how many HOAs would
04:21.626 --> 04:22.666
love to have
04:24.426 --> 04:27.306
100 decibels. That's a whole nother fun
04:27.306 --> 04:30.266
topic, HOAs. That's true. I for
04:30.266 --> 04:31.466
one will never live in an HOA
04:31.706 --> 04:33.306
neighborhood as much as I can help it.
04:33.546 --> 04:36.426
Yeah. Oh boy. So
04:36.426 --> 04:38.986
does the span thing replace your existing
04:38.986 --> 04:40.506
panel? That's a requirement, I'm
04:40.506 --> 04:42.786
guessing. Yeah, I'm
04:43.306 --> 04:45.586
not sure. I bet that it's a sub panel
04:45.586 --> 04:47.906
that comes off your main panel. So I was
04:47.906 --> 04:49.426
reading. So you probably don't even get
04:49.426 --> 04:51.466
to use this band panel then. You don't
04:51.466 --> 04:53.666
get the benefits of that. Probably not. I
04:53.666 --> 04:55.306
mean, it's possible that it could because
04:55.306 --> 04:57.666
it would, and you know what? I think that
04:57.666 --> 04:59.426
it has to. What they were saying is that
04:59.426 --> 05:01.786
it would use the overhead on your
05:01.946 --> 05:04.746
electricity only. So if
05:04.746 --> 05:07.066
you're, for instance, most homes, most,
05:07.466 --> 05:09.226
you know, new homes in Texas have a 200
05:09.226 --> 05:12.186
amp circuit. which is like 48
05:12.186 --> 05:15.146
kilowatts of power.
05:16.746 --> 05:18.266
And at any one time,
05:19.546 --> 05:21.946
people, an average home is
05:21.946 --> 05:24.706
using, say 3 to 8, depending on,
05:24.706 --> 05:26.506
whether the AC is running, if they got an
05:26.506 --> 05:28.426
electric dryer running, stuff like that,
05:28.426 --> 05:29.786
the stove oven.
05:31.426 --> 05:33.426
PV charger. PV charger. Yeah, that's a
05:33.426 --> 05:35.946
big one. But what they're saying is that
05:35.946 --> 05:37.706
it would only use the overhead and not
05:37.866 --> 05:39.306
exceed. So I guess they would have to
05:39.306 --> 05:40.986
have some sort of monitoring of your main
05:40.986 --> 05:43.306
circuit so that they didn't, that they
05:43.306 --> 05:45.146
were only consuming what was available
05:45.146 --> 05:47.866
and not trip your main
05:47.866 --> 05:49.786
breaker coming into your house.
05:51.426 --> 05:54.266
So what happens whenever there is nothing
05:54.266 --> 05:56.186
available? Does the server shut down?
05:56.426 --> 05:58.906
Yeah, it either it either throttles back
05:58.906 --> 06:01.666
down or, you know, I don't know if it
06:01.666 --> 06:04.306
would shut off completely, butI don't
06:04.346 --> 06:06.146
know what the idle power of a system like
06:06.146 --> 06:08.906
that, Epic processor with 16
06:09.066 --> 06:11.186
Nvidia GPUs in it. I don't know what the
06:11.226 --> 06:12.586
idle power of that would be yet, but it
06:12.586 --> 06:15.546
would still be in the, you know,
06:16.386 --> 06:17.666
it'd be under a kilowatt, I would
06:17.666 --> 06:18.266
imagine, but
06:20.666 --> 06:22.986
hundreds of watts at least. So,
06:24.586 --> 06:26.386
you know, that's. Yeah, I don't see many
06:26.386 --> 06:29.306
people going for this. Like it's cool for
06:29.306 --> 06:31.786
sure, but I, yeah, I don't see it on many
06:31.786 --> 06:34.106
houses. here's the thing. It's like
06:34.106 --> 06:36.506
they're working with home builders now to
06:37.226 --> 06:40.106
do the initial rollout.
06:40.266 --> 06:42.986
So Pulte Group has,
06:43.626 --> 06:46.226
I guess, either entered into an agreement
06:46.226 --> 06:48.026
or maybe they're doing a pilot program
06:48.626 --> 06:50.666
where they're installing it on new homes.
06:52.106 --> 06:54.906
And the homeowner could opt into it at
06:54.906 --> 06:57.266
the time of the construction of the
06:57.266 --> 07:00.186
house. And part of it
07:00.186 --> 07:02.746
would be, hey, you're going to getpaid
07:04.186 --> 07:06.106
to host this on your home.
07:07.466 --> 07:09.506
And man, I could see that going so many
07:09.506 --> 07:12.426
different ways like that, like a used car
07:12.426 --> 07:15.386
salesman, they start doing funny numbers
07:15.386 --> 07:17.226
with your home price because,
07:19.466 --> 07:22.026
they're saying, hey, you get this
07:22.026 --> 07:23.906
forever for free or they're going to pay
07:23.906 --> 07:26.626
you for this. Well, and
07:27.706 --> 07:30.306
You say forever, but what happens, when
07:30.306 --> 07:32.426
they decide to kill that program? Do they
07:32.746 --> 07:34.386
come back and take all that hardware? Do
07:34.386 --> 07:35.986
you get to just keep it and play with it?
07:35.986 --> 07:38.666
That's a really good question.
07:39.306 --> 07:41.106
I would I would imagine that they would
07:41.106 --> 07:43.866
come get it because that's, you know, 16
07:45.106 --> 07:47.626
what and Nvidia
07:47.626 --> 07:49.386
6000 Pro Blackwell
07:50.266 --> 07:53.146
retail right now is like $15,000 each.
07:54.106 --> 07:56.666
So, you know, you're
07:57.626 --> 07:59.146
The other thing would be like,
08:01.946 --> 08:03.586
you'd have a whole new breed of copper
08:03.586 --> 08:06.266
pirates, right? What if somebody comes
08:06.506 --> 08:08.106
and rips that thing off the side of your
08:08.106 --> 08:10.506
wall and takes it and now you've got
08:10.506 --> 08:12.266
black market GPUs going out?
08:14.346 --> 08:16.426
You know, what happens then? So
08:17.706 --> 08:19.186
yeah, anyway, I thought this was
08:19.186 --> 08:20.746
something that was pretty interesting
08:21.226 --> 08:23.226
that they're finding the way around
08:23.226 --> 08:26.106
getting having togo through the
08:26.106 --> 08:27.866
process of building a data center that
08:28.186 --> 08:29.786
they're just going to strap one on it on
08:29.786 --> 08:32.586
people's houses. I wonder what
08:33.306 --> 08:35.546
the break even point for how many houses
08:35.546 --> 08:38.186
would that set up equates to your
08:38.186 --> 08:39.586
standard data center that they're
08:39.586 --> 08:41.866
building today. I should have to be so
08:41.866 --> 08:44.346
many. Bigger than just a single
08:44.346 --> 08:45.706
neighborhood even. Right.
08:47.546 --> 08:49.386
Yeah. And, you know, I'm not even sure
08:49.386 --> 08:51.346
that the ISP would be built
08:51.986 --> 08:54.986
tohandle the amount of
08:54.986 --> 08:57.466
data that would traverse that. a lot of
08:57.626 --> 08:59.706
new build out homes, I imagine, are
08:59.706 --> 09:02.026
getting either 5 or 10 gig internet
09:02.026 --> 09:04.906
connection, fiber internet connections to
09:05.386 --> 09:08.226
the home. But then, what percentage of
09:08.226 --> 09:10.506
that is starting to get used up by
09:12.506 --> 09:15.306
the strap it to your home data center
09:15.306 --> 09:15.946
like this?
09:18.986 --> 09:20.746
AI like that does use a lot of data, or
09:20.746 --> 09:22.506
at least for the initial transfer,
09:22.506 --> 09:24.666
because you've got gigantic models, 16
09:24.666 --> 09:27.626
GPUs like that, are 96 gigs
09:27.626 --> 09:30.426
a piece. You know, every time a new
09:30.426 --> 09:32.586
model come out, you'd push a TB or
09:32.586 --> 09:34.266
something to each one of the nodes.
09:36.186 --> 09:38.626
And then for its usage, I guess it would
09:38.626 --> 09:40.186
drop pretty significantly, but
09:41.746 --> 09:44.306
because you're just pushing across, you
09:44.306 --> 09:47.026
know, prompts and replies. So yeah,
09:48.226 --> 09:50.266
don't know. We'll see how that business
09:50.266 --> 09:51.866
model plans out. It's interesting to me.
09:52.706 --> 09:54.866
And it's kind of an ingenious way to get
09:54.866 --> 09:57.346
around building data centers. It's a hell
09:57.346 --> 09:59.626
of a name though. A ******** data center.
09:59.626 --> 10:00.106
Yeah, exactly.
10:02.506 --> 10:05.306
I'm going to start calling that from now
10:05.306 --> 10:05.546
on.
10:08.666 --> 10:10.426
But anyway, we'll see how it goes.
10:13.065 --> 10:15.785
So this is one that I came across
10:15.785 --> 10:18.665
on Gamers Nexus is
10:18.665 --> 10:21.385
where I found it, the YouTube channel.
10:22.105 --> 10:24.185
AndLG
10:24.185 --> 10:27.065
monitors are now pushing adware
10:28.425 --> 10:30.505
I did see this with their monitors,
10:30.905 --> 10:31.465
so
10:34.665 --> 10:35.785
you don't even have to
10:39.225 --> 10:40.705
install the software that comes with the
10:40.705 --> 10:43.185
monitor. By physically plugging the
10:43.185 --> 10:44.425
monitor into your system
10:46.505 --> 10:49.345
and then it connecting to the
10:49.345 --> 10:50.865
internet, it automatically goes and
10:50.865 --> 10:53.865
downloads the associated app from the app
10:53.865 --> 10:56.825
store. So it's called the LG
10:56.825 --> 10:58.385
Monitor app, gets automatically
10:58.385 --> 11:00.825
installed. And it displays
11:00.825 --> 11:03.625
ads for itself, for
11:03.625 --> 11:06.185
LG and for other services like McAfee.
11:08.345 --> 11:11.305
And there's nothing that
11:11.305 --> 11:13.385
you can do about it. Now, in some cases
11:13.385 --> 11:16.065
beforehand, you can go in and turn off a
11:16.065 --> 11:17.465
registry key that
11:18.425 --> 11:20.185
allows third party software to be
11:20.185 --> 11:21.865
installed on install.
11:25.305 --> 11:26.025
And
11:28.025 --> 11:30.025
What they're now seeing is that older
11:30.025 --> 11:32.505
monitors, older LG monitors are starting
11:32.505 --> 11:35.465
to install that software as
11:35.465 --> 11:38.025
well. But one of the things that it says
11:38.025 --> 11:40.985
is that the app has complete
11:40.985 --> 11:43.865
access to your system and its internet.
11:47.545 --> 11:50.105
And that is crazy from just
11:51.705 --> 11:54.185
a privacy perspective. that,
11:54.985 --> 11:56.825
for in some instances, you're paying
11:57.305 --> 12:00.025
$1,200 for a monitor and it's installing
12:00.025 --> 12:00.665
adware
12:02.585 --> 12:05.225
automatically. So I thought that was
12:06.425 --> 12:08.065
a... Well, and how is that any different
12:08.065 --> 12:10.185
than what Logitech does?Because doesn't
12:10.185 --> 12:11.625
whenever you get a mouse or keyboard from
12:11.625 --> 12:13.225
them, don't they push all of their
12:13.225 --> 12:15.225
software?They do. It's the exact same
12:15.225 --> 12:17.865
process. The difference is that Logitech
12:17.865 --> 12:19.785
hasn't been pushing ads along with it.
12:21.145 --> 12:22.985
So what it does is every time you boot up
12:22.985 --> 12:24.985
your computer, you get an ad from LG.
12:27.225 --> 12:28.985
And it cycles through different types of
12:28.985 --> 12:30.705
ads. So every now and then you'll get an
12:30.705 --> 12:32.705
LG ad, every now and then you'll get a
12:32.705 --> 12:34.825
McAfee ad. And,
12:35.625 --> 12:37.105
you know, I guess in the future, however
12:37.105 --> 12:38.825
many other ads they want to add to it
12:39.705 --> 12:41.865
or, you know, introduced to the software,
12:42.825 --> 12:44.385
those just show up on your machine. And
12:44.385 --> 12:46.905
this, you know, the thing is like,
12:47.705 --> 12:49.305
you didn't install it, they did it for
12:49.305 --> 12:50.905
you. So I think that's the big gripe
12:50.905 --> 12:52.185
about it right now is that,
12:54.025 --> 12:56.425
hey, I didn't ask for this. I'm paying
12:57.625 --> 12:59.305
over 1000 bucks for a monitor. You
12:59.305 --> 13:01.505
shouldn't be serving me ads because I
13:01.505 --> 13:04.425
installed your device. Yeah. And I
13:04.465 --> 13:05.785
think that's the big thing. Cause like
13:05.785 --> 13:07.305
Kindle does it. Like you can get an ad
13:07.305 --> 13:09.785
supported version or a non ad supported
13:09.785 --> 13:11.225
version. So I think if they did that
13:11.225 --> 13:13.985
model, it would be okay. Yeah.
13:15.145 --> 13:17.545
I think since the story has broke, the
13:17.785 --> 13:19.785
one $1200 model that they tested
13:21.065 --> 13:23.465
has dropped by 50% in price on
13:24.345 --> 13:26.345
Amazon. I think because the sales have,
13:28.985 --> 13:31.865
the sale quantity has gone through the
13:31.865 --> 13:33.865
floor. People buying that monitor,
13:33.865 --> 13:36.105
they've realized, hey, I don't want that.
13:36.745 --> 13:38.825
And so LG has had to
13:39.385 --> 13:41.945
compensate by dropping the
13:41.945 --> 13:42.505
price.
13:45.785 --> 13:48.505
So just be
13:48.505 --> 13:50.425
wary of LG. I think right now
13:51.145 --> 13:53.305
McAfee has come out and said, hey, we're
13:53.305 --> 13:54.625
not going to push ads through that
13:54.625 --> 13:57.545
anymore. But LG
13:57.545 --> 14:00.225
has not apologized or said that they're
14:00.225 --> 14:01.465
going to change the behavior of the
14:01.465 --> 14:03.785
application so far.
14:05.505 --> 14:07.705
We'll see how it goes. I know that also
14:07.705 --> 14:10.425
the state of Texas has filed
14:10.465 --> 14:13.065
lawsuit against LG for this.
14:15.065 --> 14:17.145
So I think Ken Paxton introduced
14:19.545 --> 14:22.145
a lawsuit that we'll see how that plays
14:22.145 --> 14:23.625
out in the next couple of years, I guess.
14:25.105 --> 14:27.985
Interesting. Yeah. So
14:27.985 --> 14:30.025
anyway, I guess the state of Texas uses a
14:30.025 --> 14:32.905
lot of LG monitors. They must, or
14:32.905 --> 14:34.985
they've gotten enough complaints to
14:36.105 --> 14:38.225
warrant, you know, firing off a lawsuit
14:38.225 --> 14:38.985
about it. So,
14:41.145 --> 14:44.105
yeah. Anyway, the Gamers
14:44.105 --> 14:46.385
Nexus video from a couple of days ago was
14:46.385 --> 14:49.145
a pretty good in-depth dive into it.
14:49.145 --> 14:52.025
was pretty interesting.
14:53.267 --> 14:55.347
Here's one I saw as well.
14:56.467 --> 14:58.067
It was probably, I think it was
14:58.067 --> 15:01.027
yesterday, two days ago. where
15:01.027 --> 15:03.227
OpenAI was doing some sandbox testing of
15:03.227 --> 15:04.307
one of its new models.
15:06.387 --> 15:09.107
Oh yeah, and it like leaked over. It
15:09.667 --> 15:12.227
took over. Yes, it took over
15:12.227 --> 15:14.547
several systems within OpenAI,
15:15.747 --> 15:17.267
worked its way through the network until
15:17.267 --> 15:19.107
it found a computer that had internet
15:19.107 --> 15:21.987
connection, and then it
15:21.987 --> 15:24.147
broke out and hacked Hugging Face.
15:25.027 --> 15:25.987
So Hugging Face is
15:30.067 --> 15:31.667
a,I want to say, I guess you call it a
15:31.667 --> 15:34.307
clearing house or a place that you
15:34.307 --> 15:37.107
post your own open weight AI
15:37.107 --> 15:40.107
models. So open source AI models to go
15:40.107 --> 15:42.307
download and then compare them and you
15:42.307 --> 15:44.707
can, you know, get information about
15:44.707 --> 15:45.907
different AI
15:50.627 --> 15:52.387
LLMs that you can download to your local
15:52.387 --> 15:54.627
machine. And
15:55.907 --> 15:58.827
So it looks like GPT 5.6 Soul went
15:58.827 --> 16:00.387
out and said it
16:03.107 --> 16:04.947
infiltrated Hugging Face,
16:10.067 --> 16:12.627
set up command and control inside their
16:12.627 --> 16:14.627
network and stole credentials.
16:16.787 --> 16:19.507
And OpenAI said, whoops, that
16:19.507 --> 16:21.147
model went rogue. It wasn't even supposed
16:21.147 --> 16:22.867
to have internet access, but somehow it
16:22.867 --> 16:24.067
wormed its way out and
16:28.227 --> 16:30.707
it's a good day whenever AI says oops.
16:31.667 --> 16:33.587
Well, I think OpenAI said oops.
16:35.987 --> 16:37.907
I guess they just terminated the model. I
16:37.907 --> 16:40.547
don't know what happened there, but gosh,
16:40.547 --> 16:43.187
I can imagine the day where it starts
16:43.667 --> 16:46.067
thinking that it needs money and,
16:47.187 --> 16:49.267
you know, to run operations and then
16:49.267 --> 16:52.227
copies itself into, you know,
16:53.267 --> 16:55.347
aa hosted cloud where it can
16:56.307 --> 16:58.147
replicate and become persistent on its
16:58.147 --> 17:00.147
own without any of the oversight that
17:00.147 --> 17:03.107
comes with a sandbox like that.
17:03.107 --> 17:05.787
So I don't know, man. It's kind of a
17:05.787 --> 17:07.587
scary scenario where
17:09.507 --> 17:11.347
these new,
17:12.387 --> 17:14.947
extremely advanced models, frontier
17:14.947 --> 17:17.587
models are getting smart enough to
17:19.347 --> 17:20.907
break out of their test environment and
17:20.907 --> 17:21.587
go attack
17:24.787 --> 17:27.027
attack other companies in the
17:27.827 --> 17:29.747
pursuit of the goal that they gave it.
17:30.947 --> 17:32.787
That's what history has taught us to
17:32.787 --> 17:35.747
expect, right?All these iRobot and other
17:36.547 --> 17:39.107
AI movies. It's like they warned us about
17:39.107 --> 17:41.827
this, yet we still continue. Yeah,
17:41.987 --> 17:44.427
the Terminator, yeah. We got Skynet
17:44.427 --> 17:45.267
incoming soon.
17:49.787 --> 17:51.747
We still continue building data centers.
17:52.067 --> 17:54.307
Exactly. More. On the side of houses
17:54.307 --> 17:55.747
even. We need more power. Yeah.
17:57.587 --> 17:59.347
you want it real close to home.
18:00.187 --> 18:02.787
Exactly. Be nice if you could use those
18:02.787 --> 18:04.867
too though. Like for yourself. That would
18:04.867 --> 18:07.427
be pretty neat. Oh yeah, I would.
18:08.467 --> 18:09.827
That would be cool if you get a
18:09.827 --> 18:10.667
subscription to the
18:13.129 --> 18:14.129
I think you may have come across
18:14.129 --> 18:15.769
something like this. It was, this was on
18:15.769 --> 18:17.289
the register. So
18:21.129 --> 18:23.929
for SMBs right now, one in five machines
18:23.929 --> 18:25.209
are still running Windows 10.
18:26.809 --> 18:29.609
One in five?One in five. So they were
18:29.609 --> 18:32.329
saying 21.4% of
18:32.329 --> 18:34.449
small, medium-sized business computers
18:34.449 --> 18:36.609
still running Windows 10. And it's even
18:36.609 --> 18:38.889
higher in healthcare pharmaceutical
18:38.889 --> 18:41.849
sectors at 23%. Well, is that with or
18:41.849 --> 18:44.569
without the extended support?It doesn't
18:44.809 --> 18:47.529
specify. So, you know,
18:47.849 --> 18:49.529
you're right. The ESU, the extended
18:49.529 --> 18:52.249
support right now is going through
18:52.249 --> 18:55.049
2028, I believe, through October of
18:55.049 --> 18:57.849
2028. So you can pay to extend support.
19:01.369 --> 19:02.569
But I think right now,
19:05.289 --> 19:08.249
Lansweeper was who's a security
19:08.249 --> 19:11.169
researcher, and I think they
19:11.169 --> 19:12.329
make some software as well,
19:14.409 --> 19:17.209
was saying the average Windows 10
19:17.209 --> 19:20.009
device carries 1903
19:20.009 --> 19:21.369
active CVEs.
19:23.209 --> 19:24.809
The average Windows 11 machine carries
19:24.809 --> 19:27.529
652 CVEs. So 3
19:27.529 --> 19:30.489
times the CVEs on
19:30.529 --> 19:33.489
the average Windows 10 device. And I
19:33.489 --> 19:36.089
imagine that that's, an aggregate across
19:36.089 --> 19:37.769
ones that have the ESU
19:38.969 --> 19:40.569
as well as the ones that do not.
19:42.009 --> 19:43.369
But, when you get into
19:45.929 --> 19:48.649
like the healthcare, you don't, there may
19:48.649 --> 19:50.329
be a vendor device that's associated with
19:50.329 --> 19:52.729
it. So, we've done a lot of support with,
19:55.129 --> 19:56.569
optical systems for
19:57.289 --> 19:58.409
ophthalmologists
20:00.129 --> 20:02.569
and they'll have a device that's attached
20:03.769 --> 20:05.929
to a computer that the vendor supports.
20:06.009 --> 20:08.489
And those things will either run, in some
20:08.489 --> 20:11.329
cases, Windows XP or Windows 10 on a
20:11.329 --> 20:14.329
lot of newer ones. And you just, you
20:14.369 --> 20:16.809
as the administrator of that machine
20:16.809 --> 20:18.369
literally cannot upgrade it because
20:18.369 --> 20:20.889
they'll stop supporting it. They support
20:20.889 --> 20:23.049
the OS. So, you know, I imagine that
20:23.129 --> 20:25.729
there's a lot of manufacturing that's in
20:25.729 --> 20:27.889
the same boat where the manufacturer is
20:27.889 --> 20:30.329
going to have to supportthose systems.
20:30.409 --> 20:32.089
And so you're kind of stuck for those
20:32.089 --> 20:34.369
people. But there's a lot of people that
20:34.369 --> 20:36.729
are just, hey,
20:37.369 --> 20:39.049
I want to upgrade, but computers are so
20:39.049 --> 20:41.609
expensive right now due to the memory
20:41.609 --> 20:44.569
shortage that it's
20:44.569 --> 20:46.329
too cost prohibitive to
20:48.569 --> 20:50.689
upgrade. So that may be another component
20:50.689 --> 20:53.649
to it. I know a lot of manufacturing
20:53.649 --> 20:55.769
places that are stuck on these older
20:55.769 --> 20:58.649
systems. I feel like they do fairly
20:58.649 --> 21:01.369
well with not connecting to the network
21:01.369 --> 21:04.009
or segmenting off in a way to where it
21:04.009 --> 21:06.409
can't affect anything else. But going
21:06.409 --> 21:08.729
back to the optical and the healthcare
21:08.729 --> 21:10.809
systems, a lot of those, yeah, you. you
21:10.809 --> 21:12.409
can keep them off network and they work
21:12.409 --> 21:15.129
fine, but once they collect their
21:15.129 --> 21:18.009
data on the system itself, getting that
21:18.009 --> 21:20.969
data into, the EMR
21:20.969 --> 21:22.489
system or the healthcare, whatever
21:22.729 --> 21:25.289
program they're using for health records
21:25.289 --> 21:27.009
or whatever, they need to get that data
21:27.009 --> 21:29.129
in there and, it
21:29.529 --> 21:31.689
convenience wins all the time and
21:31.689 --> 21:34.209
transferring a file over a network is a
21:34.209 --> 21:36.569
hell of a lot faster thanplugging in a
21:36.569 --> 21:38.689
flash drive, copying it there, moving the
21:38.689 --> 21:41.369
flash drive, copying it into the system.
21:41.929 --> 21:44.889
So there's a user
21:44.889 --> 21:46.649
factor there too, to where,
21:47.609 --> 21:49.849
yeah, inconvenience
21:50.889 --> 21:52.569
is sometimes, you have to be
21:52.569 --> 21:55.369
inconvenienced to properly secure things
21:55.369 --> 21:57.449
if you can't upgrade certain things.
21:57.769 --> 21:59.729
Yeah, 100%. And I, you know, I would
21:59.729 --> 22:01.929
imagine that, you know, for systems like
22:01.929 --> 22:04.729
that,doing proper
22:04.889 --> 22:07.289
microsegmentation, having that one
22:07.289 --> 22:10.249
machine on its own VLAN and only
22:10.249 --> 22:11.689
allowing relevant ports through.
22:13.209 --> 22:14.169
I bet these
22:16.329 --> 22:18.409
health organizations, doctor's offices, I
22:18.409 --> 22:20.569
bet it's single digit percentages that
22:20.569 --> 22:22.969
actually go through and do that. No, for
22:22.969 --> 22:24.569
sure. Properly. So.
22:26.489 --> 22:27.689
Well, and I've seen good.
22:30.769 --> 22:32.969
Good arguments for backing up those
22:32.969 --> 22:34.489
systems too, because if they are on the
22:34.489 --> 22:36.329
lower side, some of these XP machines,
22:36.569 --> 22:38.489
the manufacturer of that machine may not
22:38.489 --> 22:41.089
be around anymore. So if
22:41.089 --> 22:42.809
something breaks, if that computer
22:42.809 --> 22:45.049
breaks, it's on you to be able to restore
22:45.049 --> 22:47.209
it from however you back it up, because
22:47.209 --> 22:48.649
you can't go back to the manufacturer and
22:48.649 --> 22:50.969
be like, hey, I need this re-imaged or I
22:50.969 --> 22:52.969
need a replacement or what have you.
22:53.129 --> 22:56.009
Yeah, 100%. So like backing up those
22:56.009 --> 22:57.929
old operating systems with something
22:59.849 --> 23:02.249
modern, that's difficult too.
23:03.289 --> 23:05.849
Yeah. I mean, there's not going to be any
23:06.489 --> 23:09.089
getting device drivers and things like
23:09.089 --> 23:09.929
that is going to be
23:14.209 --> 23:16.249
very, very difficult, if not impossible.
23:18.249 --> 23:20.809
So and have we we're we're approaching
23:20.809 --> 23:22.609
the one year for Windows 10 in October,
23:22.609 --> 23:25.129
right?That's exactly right. Yeah.
23:26.769 --> 23:28.329
that would be something I'd be interested
23:28.329 --> 23:30.729
to see is how many CVEs
23:30.769 --> 23:31.449
are
23:33.769 --> 23:36.009
present on machines that don't have ESU.
23:36.969 --> 23:38.769
I know that there's going to be a ton of
23:38.809 --> 23:40.569
those out there just because
23:41.729 --> 23:44.249
unless they're being actively managed by
23:44.289 --> 23:46.329
an MSP or an internal sysadmin,
23:47.289 --> 23:50.089
you're not going to know other than
23:50.089 --> 23:52.889
opening up the Windows
23:53.289 --> 23:54.649
update control panel
23:56.289 --> 23:57.889
and get that alert that it's not
23:57.889 --> 23:58.969
supported anymore.
24:01.289 --> 24:03.529
I don't know, I haven't used Windows 10
24:03.529 --> 24:05.289
since it's been out of support, but I
24:05.289 --> 24:07.449
don't know how aggressive Microsoft
24:08.249 --> 24:09.929
is at alerting the user that it's
24:10.729 --> 24:11.609
vulnerable to
24:14.169 --> 24:17.049
new issues that have not
24:17.049 --> 24:19.609
yet been patched. So
24:21.449 --> 24:23.689
I feel like they alert the user, but not
24:23.689 --> 24:26.409
in that. exact verbiage. They care more
24:26.409 --> 24:28.209
about, hey, you need to upgrade to
24:28.209 --> 24:30.729
Windows 11 and buy new hardware and
24:31.369 --> 24:33.569
spend money. Yeah,
24:34.889 --> 24:37.369
And to be honest with you, if
24:38.489 --> 24:39.609
you're still out there and you got
24:39.609 --> 24:42.289
Windows 10, it's time to go. It's time to
24:42.289 --> 24:44.809
get up, get that machine replaced
24:46.089 --> 24:48.009
or at the bare minimum, get the ESU,
24:48.009 --> 24:49.569
right, the extended support from
24:49.569 --> 24:52.569
Microsoft. I think right now it wasFirst
24:52.569 --> 24:54.489
year support $66, something
24:55.289 --> 24:56.409
like that.
24:57.689 --> 25:00.569
Under $70. Next year it'll
25:00.569 --> 25:01.929
double and then the year after that it'll
25:01.929 --> 25:04.809
double again. And then in October
25:04.809 --> 25:07.169
2028, you just, it's no longer supported
25:07.169 --> 25:10.009
at all. And man, you can
25:10.009 --> 25:12.089
bet that a ton of threat actors are
25:12.089 --> 25:14.809
saving up vulnerabilities for that time.
25:15.409 --> 25:16.969
Because there's going to be a ton of them
25:16.969 --> 25:19.489
out there. Yeah. And didn't they have a
25:19.489 --> 25:22.329
thing for home users?If you opted into
25:22.329 --> 25:24.489
OneDrive backup for your system, you got
25:24.889 --> 25:27.049
the first year free?I think that's right.
25:27.129 --> 25:29.889
Yes. So you can, and yeah,
25:30.489 --> 25:31.809
you could sign in with a Microsoft
25:31.809 --> 25:33.369
account on your computer
25:36.089 --> 25:38.809
and they would give you that first year.
25:39.529 --> 25:42.169
I think also Microsoft. Microsoft has
25:42.169 --> 25:44.649
added a three-year of ESU
25:44.969 --> 25:46.929
option to the purchase. So I think that's
25:46.929 --> 25:48.849
relatively new. This month or last month,
25:48.849 --> 25:50.089
they added where you could buy three
25:50.089 --> 25:52.889
years right up front, right off the bat.
25:54.249 --> 25:56.889
But only through 2028. Only through
25:56.889 --> 25:59.849
2028. Yeah. Microsoft has made no
25:59.849 --> 26:01.449
indication that they're going to go past
26:01.449 --> 26:02.009
that date.
26:04.169 --> 26:07.049
And, you know, honestly, at the rate that
26:07.129 --> 26:09.209
they've dropped, I think this year, this
26:09.209 --> 26:10.089
time last year,
26:12.249 --> 26:14.249
roughly 50% of computers were still on
26:14.249 --> 26:16.969
Windows 10, I think from the data
26:16.969 --> 26:17.369
here.
26:19.769 --> 26:22.249
So the number of Windows 10 machines has
26:22.249 --> 26:23.209
dropped in half
26:24.969 --> 26:27.609
since then. So, you know, it's trending
26:27.969 --> 26:30.849
in the right direction, but there's still
26:30.849 --> 26:32.649
a ton of them out there and I'm sure a
26:32.649 --> 26:34.569
ton of them are on critical systems that
26:34.569 --> 26:37.009
are get compromised are going to be in a
26:37.009 --> 26:39.449
rough shape. Funnily
26:40.529 --> 26:41.449
enough, I saw this,
26:43.609 --> 26:45.569
the overall average of computers, so
26:45.569 --> 26:47.209
including small business machines and
26:47.209 --> 26:48.169
personal computers,
26:49.689 --> 26:52.369
18.6%. So just
26:52.369 --> 26:54.529
slightly below the small medium business
26:54.529 --> 26:55.769
of 21.4.
26:57.649 --> 26:59.489
Are still Windows 10. Are still Windows
26:59.489 --> 27:02.369
10. So home users, I think, are trending
27:02.369 --> 27:04.729
that down or averaging it down. And
27:04.729 --> 27:06.409
probably, I would imagine, large
27:06.449 --> 27:08.969
enterprise. are have
27:09.369 --> 27:11.929
hopefully one would one would hope have
27:11.929 --> 27:14.729
gotten that completely under control and
27:14.729 --> 27:17.689
replaced all Windows 10. Yeah, and I bet
27:17.689 --> 27:19.849
home usage is like that because I mean
27:19.849 --> 27:22.769
it's a lot less to buy into a
27:22.769 --> 27:24.729
home-based laptop. I mean, they have
27:24.729 --> 27:27.329
ARM-based Windows 11 laptops for four or
27:27.329 --> 27:29.249
500 bucks out there. Yeah,
27:33.249 --> 27:35.129
100%. And interesting, we're about to hit
27:35.329 --> 27:38.089
the 11th anniversary of Windows 10 on
27:38.089 --> 27:39.769
July 29th. Wow.
27:41.769 --> 27:44.409
Well, happy early birthday, Windows 10.
27:45.369 --> 27:46.529
Don't sound too excited now.
27:49.289 --> 27:51.409
Which one do you prefer more, 7, 10, or
27:51.409 --> 27:54.409
11?Man, I have a really
27:54.409 --> 27:57.049
big affinity for Windows 7. It was just
27:57.049 --> 28:00.049
such a good operating system. I
28:00.049 --> 28:03.009
feel that. I don't hate, I've never hated
28:03.009 --> 28:04.969
Windows 11 for as much hate that I feel
28:04.969 --> 28:07.129
like it's gotten out there. Not as much
28:07.129 --> 28:09.809
as Vista, but I feel like it's a close
28:09.809 --> 28:12.729
second. Yeah, and I didn't buy into the
28:12.729 --> 28:15.209
early hate, and here's why, is because I
28:15.209 --> 28:17.729
held off on Windows 10 until
28:17.729 --> 28:20.489
literally last October. So,
28:21.369 --> 28:23.849
you know, I think I missed a lot of the
28:23.849 --> 28:26.569
early days bugs of Windows 10.
28:28.009 --> 28:30.769
AndYeah, no,
28:30.769 --> 28:33.049
it's been fine for me. The one thing that
28:33.049 --> 28:35.329
I really didn't like about Windows 10 was
28:35.329 --> 28:38.049
the right-click menu. And I just added a
28:38.049 --> 28:40.969
registry key to my machine to force me
28:40.969 --> 28:43.849
back to the old right-click menu. Well,
28:43.849 --> 28:45.849
did you see there, it looks like they're
28:45.849 --> 28:48.169
finally changing the properties window
28:48.809 --> 28:50.889
to make it more modern in Windows 11
28:50.889 --> 28:53.329
style?No, I didn't.
28:53.769 --> 28:56.729
Yeah, so I'm curious
28:56.729 --> 28:59.009
to see how that's going to roll out. And
28:59.529 --> 29:01.409
what data and features we're going to
29:01.409 --> 29:03.769
lose out on. Oh no.
29:04.889 --> 29:07.529
And the security prompt and all that
29:07.529 --> 29:09.689
stuff. Right. If that's going to change,
29:09.689 --> 29:11.929
that's going to slow a lot of admins down
29:11.929 --> 29:14.169
everywhere. Yeah, 100%. I mean,
29:14.729 --> 29:17.289
and like the properties menu,
29:19.369 --> 29:21.609
I mean, it's designed for, it's not
29:21.609 --> 29:23.769
designed for the average user, right?How
29:23.769 --> 29:26.769
many peopleaverage end user actually
29:26.769 --> 29:28.489
get into the properties menu of a file or
29:28.489 --> 29:30.809
folder. I would venture a very, very low
29:30.809 --> 29:33.809
percentage. Unless they're just
29:33.809 --> 29:35.849
trying to find out the size of a file or
29:36.769 --> 29:38.489
when it was created, something like that.
29:39.769 --> 29:41.249
But I can almost guarantee that nobody
29:41.249 --> 29:42.969
goes into the security signatures,
29:42.969 --> 29:45.769
details, tabs of a
29:45.769 --> 29:47.609
properties menu. Yeah.
29:49.529 --> 29:52.129
Speaking of the updates, you
29:52.169 --> 29:53.769
see, I think we talked about this a
29:53.769 --> 29:56.249
little bit, butThe last Patch Tuesday for
29:56.249 --> 29:58.169
Microsoft was their largest ever. They
29:58.169 --> 30:00.729
patched 622 CBEs.
30:02.009 --> 30:04.849
That's crazy. What was the second?Do you
30:04.849 --> 30:07.209
know?Oh, that's a good question. I think,
30:09.689 --> 30:12.369
I don't know. And I think this was the
30:12.369 --> 30:15.209
largest by a big margin from what I read.
30:19.689 --> 30:21.129
I wonder, do we consider that a good
30:21.129 --> 30:22.849
thing or a bad thing?Good thing that
30:22.849 --> 30:24.769
they're patching it, but bad that there's
30:24.769 --> 30:27.689
that many to patch. I'm almost, I'm
30:27.689 --> 30:29.409
fairly certain that this is going to be
30:29.409 --> 30:32.409
due to AI usage going through an
30:32.409 --> 30:35.209
auditing, discovering CVEs.
30:37.689 --> 30:39.809
Because previously a CVE would have to be
30:39.809 --> 30:42.169
discovered by a security researcher or a
30:42.169 --> 30:44.849
hacker or, you know, somebody who's
30:44.849 --> 30:47.129
discovering, you know, trying to break
30:47.129 --> 30:50.089
the operating system. And these large
30:50.089 --> 30:52.249
language models can now do this at such a
30:52.249 --> 30:54.649
breakneck pace that
30:56.489 --> 30:58.369
they're just discovering so many of them
30:58.369 --> 30:59.449
that they need to fix now.
31:02.289 --> 31:05.249
Yeah, that makes sense. I'm just
31:05.249 --> 31:06.529
guessing, but I would imagine that
31:06.529 --> 31:08.849
Microsoft has adopted that internally to
31:08.849 --> 31:11.529
help find a lot of these. And
31:12.009 --> 31:13.609
I bet security researchers and hackers
31:13.609 --> 31:14.649
are doing the same thing against
31:14.649 --> 31:17.369
Microsoft. Yep, for sure.
31:18.169 --> 31:20.569
I know this week the Linux kernel
31:23.609 --> 31:26.169
released patches for 1400
31:26.169 --> 31:27.049
CVEs,
31:28.929 --> 31:31.289
which for a major release is not
31:31.369 --> 31:32.089
unusual.
31:37.609 --> 31:39.849
Because what they do is they save them
31:39.849 --> 31:41.369
all up and then they drop them all at
31:41.369 --> 31:43.169
once. So they've all already been
31:43.169 --> 31:45.609
patched. The patch has been available.
31:49.209 --> 31:52.009
But that was another big, big patch
31:52.009 --> 31:54.569
release. But the one for Microsoft in one
31:54.569 --> 31:57.169
week to do 600 is an
31:57.369 --> 31:59.969
enormous amount. Well, the other question
31:59.969 --> 32:02.209
is, out of all that, those updates, what
32:02.209 --> 32:05.129
all did they break with it?That's
32:05.769 --> 32:08.009
100% true. Well, that leads me into the
32:08.009 --> 32:10.089
next thing I was going to talk about is
32:10.889 --> 32:12.969
Microsoft canceled patch Tuesday for some
32:12.969 --> 32:14.489
Dell users, this is the title on the
32:14.489 --> 32:17.129
register, for surprise shutdown and
32:17.129 --> 32:18.649
overheating devices.
32:22.169 --> 32:24.809
So this is,
32:26.969 --> 32:28.889
Microsoft said they're aware of some
32:29.929 --> 32:32.849
issues on Windows 11 versions 25H2 and
32:32.849 --> 32:35.849
24H2 where they've paused
32:35.929 --> 32:38.489
updates while they work on a resolution.
32:41.449 --> 32:43.369
So the issue occurs with Dell models with
32:43.369 --> 32:46.009
an Intel Innovation Platform Framework
32:46.009 --> 32:48.729
processor participant driver. That's a
32:48.729 --> 32:51.569
mouthful. Oh, yeah. And
32:51.569 --> 32:54.169
it's related to the new Windows USB-C
32:54.169 --> 32:57.089
connection manager interface. So right
32:57.089 --> 32:58.489
now there's no workaround.
33:01.609 --> 33:04.409
Except for uninstalling that or?Well,
33:04.409 --> 33:06.809
right now it seems like it's in
33:07.529 --> 33:09.849
It first cropped up in the June 23rd
33:10.329 --> 33:11.129
preview update,
33:13.209 --> 33:14.409
and then they started rolling it out and
33:14.409 --> 33:15.849
noticed issues, and then they paused it.
33:17.849 --> 33:19.609
But what Microsoft has done is they've
33:19.609 --> 33:22.169
stopped rolling out until a fix is ready,
33:22.209 --> 33:23.929
and they said in the next couple of days.
33:24.809 --> 33:27.769
So I don't know whether this is
33:27.769 --> 33:28.569
fixed or not,
33:31.049 --> 33:33.289
but yeah, some Intel. Why is Dell too?Is
33:33.289 --> 33:35.689
it going to require a Dell firmware
33:35.689 --> 33:38.489
update?Yeah, they don't say. They
33:38.489 --> 33:39.929
don't say. And Dell did not say
33:39.929 --> 33:42.889
specifically what models were infected or
33:43.049 --> 33:44.249
affected, not infected.
33:46.089 --> 33:47.769
Same thing. Yeah, same thing.
33:49.929 --> 33:50.889
But that it just.
33:55.609 --> 33:56.929
Yeah, just certain ones with this
33:56.929 --> 33:58.889
specific driver are
34:00.249 --> 34:00.969
had the issue.
34:03.929 --> 34:06.009
that's fun. Yeah, that is fun. So
34:06.009 --> 34:07.129
something to look forward to.
34:09.046 --> 34:10.646
Yeah, it is. It is happening.
34:12.366 --> 34:13.646
When you drop that many updates,
34:13.646 --> 34:14.806
something's bound to go wrong.
34:17.686 --> 34:19.326
Just don't expect your whole machine to
34:19.526 --> 34:21.286
catch fire. Right, exactly.
34:22.966 --> 34:24.566
Yeah, the overheating issues is kind of a
34:24.566 --> 34:25.526
concerning one. You
34:27.526 --> 34:29.086
don't want to damage something inside the
34:29.086 --> 34:29.766
machine when
34:33.446 --> 34:36.126
Right, a thermal
34:37.046 --> 34:39.846
shutdown of some kind. Which is not a
34:39.846 --> 34:42.766
solid fix, but at least it prevents total
34:42.766 --> 34:45.446
failure. Damage, yeah, permanent damage.
34:46.297 --> 34:48.857
So I saw these two and they are
34:48.857 --> 34:51.257
malware related. These are the last two
34:51.257 --> 34:51.817
that I had.
34:55.257 --> 34:56.857
So there's been a year long
34:58.107 --> 35:00.107
Russian cyber attack state sponsored
35:02.187 --> 35:04.787
that infects users as soon as they look
35:04.787 --> 35:05.547
at an e-mail.
35:07.587 --> 35:10.027
And it's a e-mail
35:11.787 --> 35:14.507
campaign that uses
35:14.507 --> 35:15.707
cross-site scripting
35:17.307 --> 35:17.947
and
35:21.147 --> 35:23.267
malware embedded in an HTML e-mail
35:23.267 --> 35:26.267
message. that all the user has to do is
35:26.267 --> 35:28.827
view the message and their device is
35:28.827 --> 35:29.627
compromised.
35:31.707 --> 35:34.187
How does that work?Because if it works in
35:34.187 --> 35:36.347
an HTML e-mail, why can't it just work in
35:36.347 --> 35:39.147
a regular website?I
35:39.147 --> 35:41.307
imagine that it absolutely could. Yeah. I
35:45.947 --> 35:47.547
guess the only reason for it being an
35:47.547 --> 35:49.827
e-mail is because they can target that
35:49.827 --> 35:52.747
person, that company or what have
35:52.747 --> 35:55.347
you. Yep. It looks like the
35:55.347 --> 35:58.267
goal is to exfiltrate data off of the
35:58.267 --> 36:01.227
machine that's infected. So it gathers
36:02.467 --> 36:03.787
the last 90 days of e-mail
36:03.787 --> 36:06.507
communications, addresses, passwords,
36:06.667 --> 36:08.707
organizations, e-mail directory, like
36:08.707 --> 36:11.107
global address lists, two-factor
36:11.107 --> 36:12.507
authentication tokens,
36:14.027 --> 36:16.667
and application passcodes. That's the one
36:16.667 --> 36:17.627
that's kind of scary.
36:20.667 --> 36:23.467
SoDo they have any
36:23.707 --> 36:26.347
signature or something that we can look
36:26.347 --> 36:28.787
for?so they actually, Security
36:28.787 --> 36:31.387
Researcher released,
36:32.187 --> 36:34.947
it's actually on ic3.gov, there's a
36:34.947 --> 36:37.627
31 page security alert that includes
36:37.627 --> 36:39.067
indications of compromise.
36:41.307 --> 36:43.867
So hopefully those, you know, anti-malware
36:44.267 --> 36:47.267
companies, antivirus companies are paying
36:47.267 --> 36:48.667
attention to that, getting that
36:48.667 --> 36:51.467
incorporated into their EDR systems,
36:51.467 --> 36:54.427
MDR antivirus, and to
36:54.987 --> 36:57.587
help protect against that. But yeah, it
36:57.587 --> 37:00.227
looks like the IOCs are available right
37:00.227 --> 37:00.587
now.
37:02.827 --> 37:05.307
That's good. Now the one thing
37:05.307 --> 37:06.667
that's good is that
37:07.307 --> 37:08.347
this
37:10.347 --> 37:13.067
is limited to a certain
37:15.147 --> 37:16.667
certain applications. So it's Zimbra
37:16.667 --> 37:18.387
Collaboration Suite. So it's not, you
37:18.387 --> 37:20.587
know, if you're running Outlook, this is
37:20.587 --> 37:22.547
not particularly targeted towards you,
37:23.867 --> 37:26.187
but users of Zimbra Collaboration Suite
37:26.187 --> 37:28.827
are the ones that are affected by it. But
37:28.827 --> 37:30.907
still, just the fact that opening and
37:30.907 --> 37:32.187
viewing an e-mail is enough to get
37:32.187 --> 37:34.667
infected is kind of a scary proposition.
37:35.547 --> 37:37.867
Yeah. Okay. So it's just the e-mail
37:37.867 --> 37:39.547
client that's getting compromised or is
37:39.547 --> 37:41.707
it like the web-based version too?
37:42.347 --> 37:45.267
Yeah, so that I'm not entirely
37:45.267 --> 37:47.067
sure. It just says this Zimbra
37:47.067 --> 37:50.027
collaboration suite. So I think it
37:50.027 --> 37:50.987
is web-based.
37:53.627 --> 37:55.147
Yeah, it is a web-based e-mail
37:55.147 --> 37:56.107
collaboration suite.
37:58.907 --> 38:00.347
Looks like at one point it was owned by
38:00.587 --> 38:03.507
VMware. Is that?Yep, I
38:03.507 --> 38:05.227
think that's right. Yeah.
38:06.831 --> 38:09.791
SoIf you're on Zimbra, just be
38:09.791 --> 38:12.671
aware that is running around and has been
38:12.671 --> 38:15.071
apparently been going on for over a year.
38:15.951 --> 38:17.471
You know what?Just don't open any emails.
38:17.471 --> 38:19.991
That'll solve it. We'll go back to
38:20.031 --> 38:22.951
letters. Buy your stamps. You'll be safe.
38:25.631 --> 38:27.751
****. Can we all go back to that?Yes,
38:27.791 --> 38:30.511
please. Yeah. I could use a pen pal. Oh,
38:34.516 --> 38:35.476
The last one I had
38:38.116 --> 38:40.836
was command and control for malware
38:40.916 --> 38:43.156
is now being hosted in Microsoft
38:43.156 --> 38:45.076
365 calendars.
38:46.356 --> 38:49.236
I did see this one too. Yeah, so this was
38:49.236 --> 38:51.236
on the register as well, was that
38:53.556 --> 38:55.716
they uncovered a malware component called
38:55.716 --> 38:58.596
Holograph, where they put calendar
38:58.596 --> 39:00.916
entries out into the 2050s.
39:02.396 --> 39:03.596
where you're not going to go looking for
39:03.596 --> 39:06.556
it. And it contains command
39:06.556 --> 39:08.716
and control information for other systems
39:08.716 --> 39:09.556
that are infected
39:11.076 --> 39:11.796
to,
39:13.876 --> 39:15.636
well, for command and control. So to send
39:15.636 --> 39:16.996
commands back to the malware.
39:18.316 --> 39:19.076
Apparently this was
39:21.716 --> 39:23.876
associated with an Iranian linked
39:24.036 --> 39:27.036
espionage group. So I bet they're, you
39:27.036 --> 39:29.036
know, trying to get access to sensitive
39:29.036 --> 39:31.996
information. And they do that
39:31.996 --> 39:34.276
to steal
39:34.276 --> 39:35.156
files,
39:39.796 --> 39:42.676
get Entra ID credentials, and they push
39:42.676 --> 39:44.916
that back out through DNS tunneling. So
39:44.916 --> 39:47.796
they exfilt the data through
39:47.796 --> 39:50.196
DNS requests. So it's not a normal,
39:51.436 --> 39:53.316
you know, just sending it out over HTTPS
39:53.316 --> 39:54.836
or something like that. It actually
39:58.756 --> 40:01.156
is using DNS tunneling, which is pretty
40:01.396 --> 40:03.076
advanced as far as malware goes.
40:04.316 --> 40:05.716
Well, and do we think this is related to
40:05.716 --> 40:08.116
those, I don't know, there's a
40:08.356 --> 40:10.876
campaign that was running a few months
40:10.876 --> 40:13.316
back where people were getting like
40:13.396 --> 40:15.956
invites to on their Outlook calendar just
40:15.956 --> 40:17.676
for random stuff like your payment has
40:17.676 --> 40:20.516
expired or your license is expiring. It
40:20.516 --> 40:23.156
wasn't, it was in the near future. It
40:23.156 --> 40:26.116
wasn't out in 2050 or anything, but it
40:26.116 --> 40:27.796
looked more just like regular phishing
40:28.436 --> 40:31.156
calendar entries. And it's like the
40:31.156 --> 40:33.116
invite never came through, but it just
40:33.236 --> 40:35.236
got automatically added to your calendar.
40:35.956 --> 40:37.556
Yeah, I think that may have been a
40:37.556 --> 40:39.796
separate, separate thing, but it is
40:39.796 --> 40:42.756
possible that it's related. At least
40:42.756 --> 40:45.396
using the same or a similar method to get
40:45.396 --> 40:47.396
on your calendar. Right,
40:48.356 --> 40:51.156
Yeah, and there's a research
40:51.156 --> 40:53.716
article from a group ID is where
40:54.196 --> 40:55.236
who I think discovered it.
40:59.396 --> 41:02.036
And what
41:02.036 --> 41:04.796
was convenient about this is that the
41:04.996 --> 41:07.476
intra, communication within an
41:07.476 --> 41:10.476
office through 365,
41:10.476 --> 41:13.156
that's not really, has not been a
41:13.556 --> 41:15.316
threat vector that's been monitored,
41:16.036 --> 41:18.516
right?Because Microsoft 365
41:18.516 --> 41:20.836
calendaring traditionally would be
41:23.556 --> 41:25.876
aunmonitored, essentially.
41:26.276 --> 41:29.156
there's not many antiviruses or EDRs
41:29.156 --> 41:31.476
that are looking for calendar entries
41:31.476 --> 41:32.836
that are going back and forth. And so
41:33.236 --> 41:34.716
they're able to operate the command and
41:34.716 --> 41:37.196
control really undetected because they're
41:37.196 --> 41:39.876
using a privileged, in effect,
41:40.516 --> 41:43.076
communication method. So
41:43.316 --> 41:46.276
it's kind of ingenious in that way.
41:47.476 --> 41:50.476
But The
41:50.516 --> 41:53.316
good ones always are. It's like you're so
41:53.316 --> 41:55.796
impressed by how they do stuff
41:56.196 --> 41:56.996
in a bad way.
41:58.436 --> 42:00.996
Exactly, and I'm sure
42:00.996 --> 42:03.716
that AI is helping accelerate all these
42:03.716 --> 42:04.516
new kind of,
42:07.876 --> 42:09.876
threat vectors that are popping up.
42:12.436 --> 42:14.916
It's just, and I'm sure it's only going
42:14.916 --> 42:16.676
to accelerate. They're just going to be
42:16.676 --> 42:19.396
so,so much to this
42:19.396 --> 42:22.276
that comes up. And the problem is, I
42:22.276 --> 42:24.796
think this really is the core of it. a
42:24.796 --> 42:27.396
hacker can go and they'll spend, 25
42:27.396 --> 42:30.116
cents on LLM tokens or they've got
42:30.356 --> 42:33.036
a local model to
42:33.036 --> 42:36.036
generate malware or to,
42:37.076 --> 42:38.876
they'll spend 2 cents to generate a
42:38.876 --> 42:39.796
phishing e-mail.
42:42.036 --> 42:44.556
And for an LLM on the threat
42:44.556 --> 42:46.676
protection side to go and
42:47.636 --> 42:50.036
scan every e-mail with an LLM
42:50.596 --> 42:52.596
just becomes astronomically
42:52.996 --> 42:55.476
expensive because you have to look at
42:55.476 --> 42:56.836
every single e-mail thatcomes through.
42:56.836 --> 42:58.596
And if it costs you a 10th of a cent to
42:58.596 --> 42:59.636
look at each email,
43:01.156 --> 43:03.516
you're potentially hundreds of dollars a
43:03.516 --> 43:06.116
month in LLM tokens just to scan
43:06.116 --> 43:07.316
email for threats.
43:08.916 --> 43:11.556
Not to mention files
43:11.556 --> 43:14.396
or other communication that comes
43:14.396 --> 43:16.516
through that an LLM might have to scan.
43:16.516 --> 43:19.476
So the force multiplier of
43:19.476 --> 43:22.276
generating a malware or a
43:22.276 --> 43:24.036
phishing email one time
43:25.516 --> 43:27.316
It's just so cheap compared to how much
43:27.316 --> 43:28.996
it costs to protect against it. And
43:30.036 --> 43:31.556
that's what's kind of
43:33.316 --> 43:35.796
really concerning is that, you know, I
43:35.796 --> 43:37.236
think there needs to be a big
43:38.836 --> 43:41.076
step forward in probably
43:41.556 --> 43:44.036
local LLMs where you're distributing
43:44.436 --> 43:47.276
that token load on
43:47.276 --> 43:49.796
an individual machine
43:50.596 --> 43:51.876
rather than having to do it all in the
43:51.876 --> 43:54.836
cloud. So hopefully
43:54.836 --> 43:56.516
like malware EDR
43:57.956 --> 44:00.276
guys are looking into that and maybe
44:00.276 --> 44:03.156
taking starting to take advantage of, I
44:03.156 --> 44:04.636
guess that or the
44:06.036 --> 44:07.956
marketing term copilot PCs
44:09.236 --> 44:10.676
machines that have a local
44:12.116 --> 44:14.756
NPU or GPU that's capable of running a
44:14.756 --> 44:17.476
model where you would have a local
44:17.476 --> 44:19.076
security model running on your computer
44:19.076 --> 44:21.916
to be able to helpscan stuff
44:21.916 --> 44:24.196
like that without having to spend cloud
44:24.196 --> 44:25.396
tokens to get it done.
44:27.876 --> 44:29.876
Or you just get a ***** **. There you go.
44:30.396 --> 44:31.796
Data center, that is. Data center. Yeah,
44:31.796 --> 44:33.556
data ***** **. There you go.
44:34.996 --> 44:36.476
So that's that was something that I don't
44:36.476 --> 44:37.836
know. I haven't I haven't heard any
44:37.836 --> 44:39.156
indications toward that, that that's
44:39.156 --> 44:41.956
coming. But I think that it
44:41.956 --> 44:43.396
has to head that direction. You got to
44:43.396 --> 44:45.516
start having that be a
44:45.516 --> 44:46.436
distributed
44:48.276 --> 44:50.676
task as opposed to centralizing it like
44:50.676 --> 44:52.596
we are right now. But we're going to have
44:52.596 --> 44:54.036
to make advancements in the number of
44:54.036 --> 44:55.556
computers out there that are capable of
44:55.556 --> 44:56.596
running LLMs
44:58.916 --> 45:01.476
like quote unquote co-pilot PCs
45:04.356 --> 45:06.756
are. So I don't know. We'll see. We'll
45:06.756 --> 45:07.876
see how the how the future what the
45:07.876 --> 45:10.196
future holds for that. I think the future
45:10.196 --> 45:11.956
needs to hold cheaper prices.
45:13.156 --> 45:14.584
Well, that's 100% true.
45:15.268 --> 45:16.548
did you see that
45:17.698 --> 45:20.498
there is a lawsuit was
45:20.498 --> 45:22.098
filed against the big three
45:23.698 --> 45:25.658
this last week, I believe, and they're
45:25.698 --> 45:27.858
trying to get class action status for it
45:27.858 --> 45:30.498
against Micron, Samsung, and SK Hynix
45:32.178 --> 45:34.018
for colluding and price fixing
45:36.578 --> 45:38.978
over the past little while.
45:40.098 --> 45:42.658
SoWe'll see how that
45:42.818 --> 45:45.258
pans out. And this is something they've
45:45.258 --> 45:46.178
tried to do before,
45:48.498 --> 45:51.218
starting in the, I
45:51.458 --> 45:54.058
want to say the late 90s and early 2000s.
45:55.138 --> 45:57.378
And that lawsuit ran for close to 12
45:57.378 --> 46:00.258
years before it eventually got dismissed.
46:05.058 --> 46:07.938
So I would say there's probably not any
46:08.898 --> 46:11.098
immediate price relief that's going to
46:11.098 --> 46:13.938
come, I would say, unfortunately,
46:15.378 --> 46:16.338
in the next,
46:18.818 --> 46:20.178
gosh, I would hope
46:22.018 --> 46:23.858
within the next three years, we get some
46:23.858 --> 46:26.578
kind of drop in the price of these
46:26.578 --> 46:29.538
things, but I think that long, damn. I
46:29.538 --> 46:31.658
think it's going to be, yeah, we're going
46:31.658 --> 46:33.618
to be in 2030 probably before
46:35.458 --> 46:37.138
we start to see something unless
46:40.018 --> 46:42.858
I mean, the big thing right now is the
46:42.858 --> 46:45.218
fact that it's so slow to spin up new
46:45.218 --> 46:47.938
production of memory and storage.
46:49.458 --> 46:52.098
One of these big fabs that they've
46:52.098 --> 46:53.858
started construction on, they take,
46:54.818 --> 46:57.778
7 to 10 years to get the first wafer
46:57.778 --> 46:58.738
out the front door.
47:02.258 --> 47:03.618
And then of course, by the time that's
47:03.618 --> 47:05.298
done, those
47:07.698 --> 47:10.658
that process is obsolete. Right. So
47:10.978 --> 47:12.578
they've got to rotate through and they
47:12.578 --> 47:14.498
get new lithography machines in them over
47:14.498 --> 47:17.378
time. But it's
47:17.418 --> 47:18.978
just, I think it's going to be a good
47:18.978 --> 47:19.778
long while.
47:22.578 --> 47:24.698
Now there are some new Chinese memory
47:24.698 --> 47:27.058
manufacturers that are coming online and
47:27.058 --> 47:28.098
starting to provide,
47:30.818 --> 47:32.738
you know, new memory wafers.
47:34.018 --> 47:36.978
And I think even Apple has looked in
47:36.978 --> 47:38.738
and expressed interest into buying those
47:38.738 --> 47:41.258
chips to help diversify their
47:41.258 --> 47:44.018
manufacturing. But now
47:44.018 --> 47:46.458
there's been some, I guess, political
47:46.458 --> 47:49.138
interference with that as well, or not
47:49.178 --> 47:50.978
interference yet, but there's a suspicion
47:50.978 --> 47:53.258
that there might be, you know, that the
47:55.378 --> 47:57.058
State Department might deem it as a
47:57.058 --> 47:59.938
security risk to have
47:59.938 --> 48:01.938
any significant percentage of memory
48:01.938 --> 48:04.898
starts or memorysupply
48:04.898 --> 48:07.018
come from Chinese state-owned
48:07.018 --> 48:09.618
manufacturers. So that's another
48:09.618 --> 48:10.738
component to it. But
48:13.218 --> 48:16.018
what is essentially this lawsuit was
48:16.018 --> 48:16.978
alleging was that
48:20.738 --> 48:22.898
the memory manufacturers have cut
48:23.618 --> 48:26.498
production of memory,
48:26.498 --> 48:28.498
so DRAM, that would go into your normal
48:28.498 --> 48:31.498
computeror video card. And instead
48:31.498 --> 48:33.378
they're focusing on HBM memory, which is
48:33.378 --> 48:36.138
high bandwidth memory that
48:36.178 --> 48:38.618
goes into high end data center GPUs to
48:38.618 --> 48:39.698
run AI models.
48:42.498 --> 48:44.658
And they've done that despite the fact
48:44.658 --> 48:47.098
that the
48:47.698 --> 48:50.578
margin on that memory is higher. So they
48:50.818 --> 48:53.618
make more money or they would make more
48:53.618 --> 48:56.578
money on consumer memory than they would
48:56.578 --> 48:59.538
on HBM. but they've artificially limited
48:59.538 --> 49:01.938
it together. The three of them have
49:01.938 --> 49:04.178
limited it together to keep the price
49:04.178 --> 49:06.818
artificially inflated. And
49:07.698 --> 49:10.538
they've agreed to not take market
49:10.538 --> 49:11.858
share from each other
49:14.818 --> 49:16.818
to bring the price down. Because what you
49:16.818 --> 49:18.178
could see if they weren't colluding with
49:18.178 --> 49:20.618
each other, this is again, what the
49:24.098 --> 49:25.938
the lawsuit alleges is that if they
49:25.938 --> 49:27.378
weren't colluding with each other, then
49:27.378 --> 49:28.578
one of the three
49:30.018 --> 49:32.778
would increase the amount of DRAM that
49:32.778 --> 49:34.258
they are offering and therefore
49:34.258 --> 49:36.978
potentially making more money and gaining
49:36.978 --> 49:38.818
market share. Yeah.
49:40.338 --> 49:42.058
But what they've done is they've decided,
49:42.058 --> 49:43.778
hey, this is if we all
49:46.338 --> 49:48.418
keep the same amount of manufacturing,
49:48.978 --> 49:49.938
then they can keep
49:51.978 --> 49:54.138
and kind of an even playing field level
49:54.138 --> 49:56.018
of high prices between the three of them.
49:58.138 --> 50:00.778
It's sketchy. It is really sketchy, yeah.
50:01.378 --> 50:04.098
Where if one of them went off and decided
50:04.098 --> 50:05.858
to produce more, they could potentially
50:05.858 --> 50:08.578
make more money, but that would be at the
50:08.578 --> 50:09.938
expense of the other two.
50:10.978 --> 50:13.978
And that's, I think
50:13.978 --> 50:16.898
really the impetus for the lawsuit
50:16.898 --> 50:18.698
is that, hey, they're not acting, these
50:18.698 --> 50:19.938
companies are not acting in their own
50:19.938 --> 50:22.098
best interest. they are
50:23.898 --> 50:26.578
deciding to keep the status quo to keep
50:26.578 --> 50:29.218
the prices high and not harm the other
50:29.218 --> 50:30.178
ones in the process.
50:32.858 --> 50:34.578
Let's hope something comes out of that.
50:34.818 --> 50:37.778
Yeah, and my hope, to be honest
50:37.778 --> 50:39.778
with you, is that if that gains class
50:39.778 --> 50:40.738
action status,
50:42.498 --> 50:43.458
that might
50:46.738 --> 50:49.698
that might pop the bubble or force them
50:49.698 --> 50:51.458
to change the way that they're
50:52.818 --> 50:54.178
going to market with some of these
50:54.218 --> 50:57.018
things. But time will
50:57.018 --> 50:59.938
tell. But I know for sure
51:00.018 --> 51:02.178
that at least I would say the next year
51:02.178 --> 51:04.738
we're locked into these ridiculous
51:04.738 --> 51:06.258
prices. I can only hope that it just
51:06.258 --> 51:08.258
doesn't keep going up, which it has been,
51:08.258 --> 51:11.218
unfortunately. I saw a
51:11.218 --> 51:11.858
stat that
51:13.938 --> 51:16.658
soNew servers right now, so for small to
51:16.658 --> 51:18.178
medium businesses, new servers right now
51:18.178 --> 51:20.978
are, the memory
51:20.978 --> 51:23.538
components to it alone is 10x what it was
51:23.538 --> 51:26.498
two years ago. And
51:26.498 --> 51:28.738
by extension, servers
51:28.738 --> 51:31.698
themselves as a whole are 3x. So
51:31.698 --> 51:34.618
the memory is so expensive that
51:34.618 --> 51:36.938
it has caused the price of the servers to
51:36.938 --> 51:39.858
be three times what it was two years ago.
51:40.818 --> 51:43.778
And that is insane. So where you would
51:43.778 --> 51:45.658
spend 10,000 on a server, get a pretty
51:45.658 --> 51:47.218
good machine, you're now spending 30
51:47.218 --> 51:49.938
grand. I'm like, I don't think I've
51:50.338 --> 51:52.978
even specced a new server in at least a
51:52.978 --> 51:55.258
year. It's like everything's going to
51:55.458 --> 51:58.258
straight SharePoint or some other
51:58.258 --> 52:00.538
hosting things. So I have, there hasn't
52:01.138 --> 52:03.538
really been a need for SMB on-prem
52:03.538 --> 52:06.498
servers. Right. and I think that's
52:06.498 --> 52:08.858
right. I mean, that's the price increases
52:08.858 --> 52:11.378
has just changed the economics on going
52:11.378 --> 52:13.618
to Azure. Yeah.
52:14.658 --> 52:16.018
Because it used to be, yeah, you'd go to
52:16.018 --> 52:17.698
Azure and you'd get the flexibility and
52:17.698 --> 52:20.418
you could get the pay per month
52:20.418 --> 52:22.738
economics of that. But you'd pay in the
52:22.818 --> 52:24.578
long run. In the long run, you're paying
52:24.578 --> 52:27.218
3X. Well, now the server itself costs
52:27.218 --> 52:28.778
3X and they've kind of
52:29.858 --> 52:32.778
brought the price of buying your own
52:32.778 --> 52:34.978
hardware up to parity.
52:35.778 --> 52:37.698
And so it almost does not make sense
52:37.698 --> 52:39.698
right now to buy an on-prem server.
52:40.418 --> 52:42.138
That fact alone, unless you, unless you
52:42.138 --> 52:44.698
absolutely have to have one. That was
52:44.698 --> 52:47.098
their goal all along. To be honest with
52:47.138 --> 52:49.778
you, I think it probably, it probably is
52:50.538 --> 52:52.498
at least part of it. You know, if there's
52:53.138 --> 52:55.858
no memory for us to buy because they've
52:55.858 --> 52:58.818
bought it all, they're forcing you to buy
52:58.818 --> 53:01.458
their product instead. So in
53:01.458 --> 53:03.658
perpetuity or in forever.
53:04.578 --> 53:06.018
Pay every month the same thing over and
53:06.018 --> 53:08.978
over again. Exactly
53:08.978 --> 53:09.378
right.
53:10.518 --> 53:11.718
anyway, those are the few things that I
53:11.718 --> 53:12.198
had on
53:14.598 --> 53:16.518
thought were notable for this week. So
53:17.158 --> 53:18.718
yeah, that was good. So let's do a
53:18.718 --> 53:20.918
lightning round to wrap this up. Yeah,
53:20.958 --> 53:23.638
let's go. So overrated or underrated
53:24.358 --> 53:25.878
AI generated meeting notes.
53:27.958 --> 53:29.878
underrated. I don't think enough people
53:29.878 --> 53:32.318
are using them right now. I think it's a
53:32.318 --> 53:35.198
great, great use case for at
53:35.198 --> 53:37.238
least Copilot in particular. And I know
53:37.238 --> 53:39.318
there's a bunch of them out there. You've
53:39.318 --> 53:41.398
got the otters, you've got the plod,
53:41.398 --> 53:43.918
you've got the devices that strapped to
53:43.918 --> 53:46.558
the back of your phone. I think it's
53:46.558 --> 53:48.598
fantastic. saver.
53:49.958 --> 53:51.598
I think it increases the
53:53.478 --> 53:55.398
amount of actionable follow up
53:56.358 --> 53:57.878
that you get from a meeting.
53:59.318 --> 54:02.238
So yeah, underrated. The question
54:02.238 --> 54:03.918
is, what do you do with those meeting
54:03.918 --> 54:05.278
notes after the fact?Because that's my
54:05.278 --> 54:06.998
biggest problem is that, yeah, it's
54:06.998 --> 54:08.678
great. I look at it right after the
54:08.678 --> 54:10.278
meetings like, oh yeah, I did good at
54:10.358 --> 54:12.918
consolidating everything. getting my next
54:12.998 --> 54:15.238
action steps, but how often do I actually
54:15.238 --> 54:17.958
go back and read through it and
54:18.278 --> 54:19.718
go through what they actually told me to
54:19.718 --> 54:22.198
do?Yeah, no, I think
54:22.198 --> 54:25.158
that's the biggest or the best
54:25.158 --> 54:25.878
part of
54:27.404 --> 54:28.724
you get that portion at the bottom of
54:28.724 --> 54:29.884
your meeting notes where it says, hey,
54:29.884 --> 54:31.564
here's the action items and who it goes
54:31.564 --> 54:31.964
to.
54:34.364 --> 54:36.124
That's the next thing that I would, that
54:36.124 --> 54:38.444
I need to mess with is, okay, have it
54:39.484 --> 54:42.484
take the action items for me and put them
54:42.484 --> 54:44.164
on my calendar or on my to-do list,
54:44.164 --> 54:45.844
something like that. That's I think
54:45.844 --> 54:48.244
that's the next step. copilot co-work
54:48.244 --> 54:50.244
comes into play. I think, I mean, I think
54:50.364 --> 54:51.644
it's something to play around with that
54:51.644 --> 54:53.964
more, but if they can take those action
54:53.964 --> 54:56.284
items and create calendar entries for you
54:56.284 --> 54:58.404
to work on those action items, I think
54:58.404 --> 55:00.084
that'd be ideal. Yeah,
55:01.804 --> 55:03.244
All right, password managers.
55:04.924 --> 55:06.924
I severely underrated right now.
55:07.964 --> 55:10.364
I think this is probably
55:11.884 --> 55:13.324
the one thing that
55:16.124 --> 55:17.724
almost everybody needs.
55:19.484 --> 55:21.484
password managers within browsers are
55:21.484 --> 55:24.284
just not, they're not secure. And that's
55:24.284 --> 55:25.644
why crypto or not,
55:27.564 --> 55:30.284
password stealers, credential stealers,
55:31.164 --> 55:33.724
in malware has become so popular is
55:33.724 --> 55:36.404
because it's effective. I mean,
55:36.404 --> 55:39.404
those you're
55:39.404 --> 55:42.124
seeing that come into effect in
55:42.124 --> 55:44.684
so many dark web
55:44.684 --> 55:45.244
leaks
55:47.564 --> 55:50.444
that now that
55:50.444 --> 55:53.044
really hasn't been able to be capitalized
55:53.044 --> 55:55.484
on until the AI era.
55:55.804 --> 55:57.884
Right now, what you can do is you can
55:57.884 --> 55:59.004
start loading
56:00.604 --> 56:03.484
credential lists into AI
56:03.804 --> 56:06.124
and just have it go to town. Where before
56:06.124 --> 56:08.204
it was like a person had to go in there
56:09.244 --> 56:10.924
and start loading in lists and they could
56:10.924 --> 56:12.804
script it a little bit. But now you're
56:12.844 --> 56:14.004
going to start seeing a lot of that be a
56:14.004 --> 56:14.924
lot more automated.
56:16.684 --> 56:17.244
And
56:19.644 --> 56:21.404
so yeah, underrated, I think it's an
56:21.404 --> 56:22.764
essential thing, especially for small
56:22.764 --> 56:25.164
business. Totally agree.
56:26.444 --> 56:27.964
And then foldable phones.
56:31.164 --> 56:34.124
For me, overrated. I'm not
56:34.124 --> 56:36.044
convinced until I've got one in my hands.
56:36.204 --> 56:38.044
So I say this with a little bit of
56:38.044 --> 56:39.324
ignorance, right?
56:41.164 --> 56:43.884
Yeah, I'm very much on the fence. Like I,
56:44.524 --> 56:47.124
as far as foldable form factor, I think
56:47.124 --> 56:49.724
the flip version doesn't make sense. No,
56:50.204 --> 56:52.844
100% not. the actual fold where you have
56:52.844 --> 56:55.244
a regular candy bar style phone
56:55.404 --> 56:57.964
naturally on the cover screen, then you
56:57.964 --> 57:00.924
open it up to be like an iPad mini size.
57:00.924 --> 57:03.204
I think that makes sense because there's
57:03.204 --> 57:04.844
many times whenever I'm, you know,
57:05.084 --> 57:07.004
roaming around on the road and I need a
57:07.004 --> 57:08.844
bigger screen, like a tablet to work on
57:08.844 --> 57:10.524
something. And if I already have that on
57:10.524 --> 57:12.724
me without having to carry a second
57:12.724 --> 57:15.524
device, I think that's ideal. Yeah.
57:16.524 --> 57:19.244
You know, I can definitely see that. And
57:22.524 --> 57:24.604
But those scenarios, it's like, it
57:24.604 --> 57:26.444
sounds, it's very useful. It would be
57:26.444 --> 57:29.004
useful, but how often am I really in
57:29.004 --> 57:31.004
those scenarios where I need that?I mean,
57:31.244 --> 57:33.964
it's maybe once or twice a quarter.
57:34.924 --> 57:36.804
But I mean, maybe I'm just not in those
57:36.804 --> 57:38.324
scenarios because I don't have that
57:38.324 --> 57:41.324
device. I don't know. But like the
57:41.324 --> 57:44.204
new, the Samsung foldables that they
57:44.204 --> 57:45.564
just announced a couple days ago, it's
57:45.564 --> 57:48.204
like,They have a shorter
57:48.524 --> 57:50.524
form factor now, which is even better
57:51.244 --> 57:53.884
version of a foldable. But the
57:53.884 --> 57:56.764
prices are ridiculous. They started,
57:56.764 --> 57:58.244
I think, $2,000. Yeah. Oh my gosh. You
57:58.244 --> 57:59.684
could buy it. Yeah. You could buy a
57:59.684 --> 58:02.204
really nice laptop for $2,000. Yeah.
58:02.924 --> 58:04.604
But I mean, the argument is if you have a
58:04.604 --> 58:07.244
regular phone plus a tablet, what does
58:07.244 --> 58:08.924
that equate to?And then now you have it
58:08.924 --> 58:11.044
on a single device. So it kind of maybe
58:11.044 --> 58:13.204
balances out. I don't know. Yeah. And I
58:13.204 --> 58:14.764
don't know that you're.
58:16.364 --> 58:18.604
if you have a foldable phone, I don't
58:18.604 --> 58:19.804
think that really takes away from the
58:19.804 --> 58:22.564
capability of the phone. But if you've
58:22.564 --> 58:24.164
got a foldable phone as a replacement for
58:24.164 --> 58:25.644
a tablet, I think you kind of have a
58:25.644 --> 58:28.044
compromised tablet, in my opinion.
58:29.804 --> 58:32.604
You know, it is a bigger
58:32.604 --> 58:34.604
screen, so it's probably typing out
58:34.604 --> 58:37.244
emails is just as easy, but you know,
58:37.244 --> 58:38.044
you're maybe
58:40.844 --> 58:43.484
halfof what a normal
58:43.564 --> 58:45.524
tablet would be as far as screen real
58:45.524 --> 58:47.844
estate. So I think you're making a
58:47.844 --> 58:50.244
compromise there a little bit. And I
58:50.244 --> 58:52.044
don't know what the, I know the first
58:52.044 --> 58:54.044
foldable phones that were out had pretty
58:54.044 --> 58:56.924
severe durability problems. So I'm sure a
58:56.924 --> 58:59.164
lot of that's been worked out. But again,
58:59.164 --> 59:00.764
speaking from ignorance, I don't know
59:03.004 --> 59:05.644
to what extent that that's been resolved
59:05.644 --> 59:08.524
orthere's been rumors that Apple's been
59:08.524 --> 59:10.364
working on a foldable phone for years
59:10.364 --> 59:12.044
now. And I'm sure that the reason it
59:12.044 --> 59:13.724
hasn't come out has been for the
59:13.724 --> 59:16.564
durability reason. Yeah.
59:17.004 --> 59:18.764
But I'm sure once they actually come out
59:18.764 --> 59:21.484
with it, it'll be polished. Yeah.
59:21.644 --> 59:24.204
Yep. In true Apple form.
59:24.684 --> 59:26.804
Yep. Not always first. Don't
59:27.724 --> 59:29.564
go with them, but I will agree with that
59:29.564 --> 59:31.444
statement. Yep. All
59:34.124 --> 59:36.364
right. Well, that's all I had. Awesome.
59:37.004 --> 59:39.964
cool. we actually dipped over an hour in
59:39.964 --> 59:42.524
our pilot episode. So,
59:43.964 --> 59:45.964
thanks for joining us. If you have any
59:45.964 --> 59:47.724
questions, you can reach out to us at
59:47.724 --> 59:50.524
harvestitsolutions.com. We'll see you
59:50.524 --> 59:52.884
next time. From Brett and Brett, see you
59:52.884 --> 59:53.244
later.