WEBVTT - Tech Friday w/ Dave Hatter - Sponsored by Intrust IT - 10/16/2026

0:00:00.030 --> 0:00:03.070
<v Speaker 1>Station.

0:00:03.090 --> 0:00:08.709
<v Speaker 2>631-55-KRCD talk station. InTrustIT.com. If you're a business owner, I

0:00:08.730 --> 0:00:10.660
<v Speaker 2>bet you have computers and I bet you need best

0:00:10.700 --> 0:00:13.620
<v Speaker 2>practices put in place to avoid all of the pitfalls

0:00:13.680 --> 0:00:18.060
<v Speaker 2>and landmines that you encounter online and connected to the world. InTrustIT.com.

0:00:18.100 --> 0:00:20.220
<v Speaker 2>The business curses, they are the best in the business.

0:00:20.260 --> 0:00:23.300
<v Speaker 2>That would be Dave Hatter's company. Employee owned. They got

0:00:23.360 --> 0:00:25.500
<v Speaker 2>great folks working for you. Dave Hatter, thank you so

0:00:25.520 --> 0:00:27.900
<v Speaker 2>much for sponsoring the segment here on the 55K morning show.

0:00:27.920 --> 0:00:29.940
<v Speaker 2>We'd like to call Tech Friday with you, Dave Hatter.

0:00:31.170 --> 0:00:33.290
<v Speaker 1>Always my pleasure, Brian. Happy to be here.

0:00:33.650 --> 0:00:35.130
<v Speaker 2>Not sure if you were listening. I'm not mad if

0:00:35.170 --> 0:00:37.470
<v Speaker 2>you weren't, but the first article you want to talk about,

0:00:37.510 --> 0:00:41.610
<v Speaker 2>the artificial intelligence refrigerator, led me to get a list

0:00:41.650 --> 0:00:43.950
<v Speaker 2>of some of the dumbest Internet of Things devices you

0:00:43.970 --> 0:00:49.010
<v Speaker 2>could ever find, including an Internet-controlled salt shaker. Of course,

0:00:49.890 --> 0:00:53.010
<v Speaker 2>it's hooked up to an app. You can get an

0:00:53.310 --> 0:00:57.390
<v Speaker 2>Icon smart condom, wearable smart device that tracks and measures

0:00:57.550 --> 0:01:01.620
<v Speaker 2>all kinds of metrics of the bedroom activity. It's I

0:01:01.640 --> 0:01:03.620
<v Speaker 2>just couldn't believe this stuff existed. You talk about it

0:01:03.660 --> 0:01:05.990
<v Speaker 2>all the time. So let's pivot back over to the story.

0:01:06.010 --> 0:01:09.610
<v Speaker 2>You wanted to talk about a smart refrigerator. Just open

0:01:09.630 --> 0:01:11.410
<v Speaker 2>the door and look and see what you need, for

0:01:11.450 --> 0:01:12.009
<v Speaker 2>God's sake.

0:01:12.330 --> 0:01:15.310
<v Speaker 1>I'm glad you brought that up, Brian. I couldn't agree

0:01:15.330 --> 0:01:17.450
<v Speaker 1>with you more because more and more we're talking about

0:01:18.020 --> 0:01:22.860
<v Speaker 1>Internet of Things devices, a.k.a. smart devices. People listening can't

0:01:22.900 --> 0:01:25.770
<v Speaker 1>see me doing the air quotes around that. This stuff

0:01:25.950 --> 0:01:28.600
<v Speaker 1>is a privacy and security dumpster fire, as I keep saying,

0:01:28.680 --> 0:01:30.440
<v Speaker 1>and we just have more and more examples. So I'm

0:01:30.480 --> 0:01:32.000
<v Speaker 1>glad you looked that up, and no, I did not

0:01:32.040 --> 0:01:32.420
<v Speaker 1>hear that.

0:01:34.500 --> 0:01:38.539
<v Speaker 2>How about a $ 50 egg tray, Wi-Fi connected to count

0:01:38.620 --> 0:01:39.360
<v Speaker 2>your eggs?

0:01:40.580 --> 0:01:43.260
<v Speaker 1>Well, I want to come back to that. I'm glad

0:01:43.280 --> 0:01:47.450
<v Speaker 1>you brought that up. On my Substack, davehatter.substack.com. This is

0:01:47.750 --> 0:01:53.500
<v Speaker 1>just a blogging site. One of the things I have

0:01:53.540 --> 0:01:57.490
<v Speaker 1>blogged on is why the Internet of Things, so-called smart devices,

0:01:57.570 --> 0:01:59.510
<v Speaker 1>are a privacy and security dumpster fire, and why you

0:01:59.530 --> 0:02:02.830
<v Speaker 1>should get rid of all this garbage. Just some high-level stuff,

0:02:02.950 --> 0:02:05.570
<v Speaker 1>including links to books like Mick of Opponents, If It's Smart,

0:02:05.650 --> 0:02:09.570
<v Speaker 1>It's Vulnerable, where he meant anything, including the election system,

0:02:09.610 --> 0:02:13.830
<v Speaker 1>by the way, is vulnerable. And then Bruce Schneier's book,

0:02:14.290 --> 0:02:16.720
<v Speaker 1>Click Here to Kill Everyone. Now, Bruce Schneier is a

0:02:16.780 --> 0:02:20.790
<v Speaker 1>very well-known cryptography expert. He knows more about this than

0:02:20.930 --> 0:02:22.929
<v Speaker 1>I could ever hope to know. And he wrote a

0:02:22.950 --> 0:02:25.430
<v Speaker 1>book called Click Here to Kill Everyone. So you tell me, Brian.

0:02:25.490 --> 0:02:29.240
<v Speaker 1>But my point is, on that sub stack, every time

0:02:29.290 --> 0:02:31.120
<v Speaker 1>I find a story like this, I add it. So

0:02:31.160 --> 0:02:33.240
<v Speaker 1>you don't have to just see what I'm saying about it.

0:02:33.600 --> 0:02:35.340
<v Speaker 1>You don't have to see what other experts are saying

0:02:35.360 --> 0:02:38.260
<v Speaker 1>about it. I am now creating a compendium of these stories.

0:02:38.400 --> 0:02:40.920
<v Speaker 1>I encourage all your listeners. I'll put it in today's

0:02:41.000 --> 0:02:45.790
<v Speaker 1>show notes. Just go see for yourself. It's one after

0:02:45.850 --> 0:02:49.510
<v Speaker 1>another after another of these things. It's your car. It's everything, right?

0:02:50.120 --> 0:02:52.780
<v Speaker 1>But this really brings us to a finer point, especially

0:02:52.800 --> 0:02:54.240
<v Speaker 1>in light of the story that came out of France.

0:02:55.100 --> 0:02:59.170
<v Speaker 1>And forget about AI at this point. Does your device

0:02:59.210 --> 0:03:02.760
<v Speaker 1>have software in it? And does it need software? Is

0:03:02.800 --> 0:03:06.500
<v Speaker 1>it connected to the internet using that software? And ask yourself, why?

0:03:06.620 --> 0:03:08.160
<v Speaker 1>To your point, why do I need to have an

0:03:08.240 --> 0:03:10.770
<v Speaker 1>egg tray for 50 bucks when I could get probably

0:03:10.810 --> 0:03:12.650
<v Speaker 1>a 50 cent egg tray and I can look in

0:03:12.669 --> 0:03:14.290
<v Speaker 1>the refrigerator and count the eggs myself?

0:03:14.350 --> 0:03:16.070
<v Speaker 2>Not to mention- Just keep them in the damn carton

0:03:16.110 --> 0:03:16.870
<v Speaker 2>you bought them in.

0:03:17.910 --> 0:03:20.410
<v Speaker 1>Even better. Even better, Brian. That's what I do because

0:03:20.610 --> 0:03:23.769
<v Speaker 1>I am cheap, as my wife will tell you. But

0:03:24.530 --> 0:03:27.239
<v Speaker 1>imagine this for a second. Even without the issue of

0:03:27.300 --> 0:03:31.090
<v Speaker 1>the security and usability issue this brings up, Do you

0:03:31.130 --> 0:03:33.250
<v Speaker 1>really think it's going to be helpful to you when

0:03:33.290 --> 0:03:36.250
<v Speaker 1>your insurance company strikes a deal with your smart refrigerator

0:03:36.290 --> 0:03:39.930
<v Speaker 1>company and they surreptitiously buy your data because you signed

0:03:39.970 --> 0:03:42.550
<v Speaker 1>a terms of service that's 80 pages long? It's a

0:03:42.570 --> 0:03:46.260
<v Speaker 1>confusopoly of legal and technical mumbo jumbo that you can't understand.

0:03:46.900 --> 0:03:49.020
<v Speaker 1>And they're buying your data and they suddenly see that

0:03:49.080 --> 0:03:52.700
<v Speaker 1>you eat 15 pounds of bacon a week. You have

0:03:52.700 --> 0:03:57.040
<v Speaker 1>30 jars of mayonnaise. You drink 42 gallons of Diet

0:03:57.100 --> 0:04:00.190
<v Speaker 1>Coke and three gallons of vodka. Do you think that

0:04:00.260 --> 0:04:03.840
<v Speaker 1>is going to be helpful to you in your insurance premiums? So,

0:04:04.160 --> 0:04:07.340
<v Speaker 1>but anyhow, back to this particular story. And this is

0:04:07.420 --> 0:04:11.500
<v Speaker 1>not a new concept. Brian, year after year after year,

0:04:11.660 --> 0:04:13.370
<v Speaker 1>for all the years we've been doing this, you hear

0:04:13.410 --> 0:04:16.810
<v Speaker 1>people like me, including me, saying software updates. You've got

0:04:16.830 --> 0:04:19.050
<v Speaker 1>to install the software updates. If you didn't catch it, Brian,

0:04:19.089 --> 0:04:22.029
<v Speaker 1>this past Patch Tuesday, you know, Microsoft releases their updates

0:04:22.110 --> 0:04:29.820
<v Speaker 1>once a month. They fixed 1,413 bugs. 1,413. That is

0:04:29.839 --> 0:04:33.180
<v Speaker 1>an all-time record after last month's Patch Tuesday record of

0:04:33.240 --> 0:04:36.460
<v Speaker 1>almost 1,000. So you've got these devices that used to

0:04:36.500 --> 0:04:39.710
<v Speaker 1>just work, used to keep your drinks cold, used to

0:04:39.750 --> 0:04:43.010
<v Speaker 1>make ice cubes without any of this software, no internet connections.

0:04:43.350 --> 0:04:45.349
<v Speaker 1>They just work. Well, now you got to worry about

0:04:45.390 --> 0:04:48.940
<v Speaker 1>these patches. And now add to it, well, you hear

0:04:48.980 --> 0:04:52.660
<v Speaker 1>me say, install the patches. The patches break your refrigerator.

0:04:52.760 --> 0:04:55.580
<v Speaker 1>You come home from work, Right after it dropped the

0:04:55.620 --> 0:04:59.190
<v Speaker 1>dime on you, the insurance company, it updates itself, stops working,

0:04:59.390 --> 0:05:00.210
<v Speaker 1>and ruins all your food.

0:05:00.750 --> 0:05:04.349
<v Speaker 2>It reminds me of the 737 MAX update that resulted

0:05:04.390 --> 0:05:06.650
<v Speaker 2>in pilots crashing planes in the ground because they weren't

0:05:06.710 --> 0:05:08.739
<v Speaker 2>advised about the software update, Dave.

0:05:09.460 --> 0:05:11.260
<v Speaker 1>Did you see the story out of France? It's kind

0:05:11.279 --> 0:05:13.700
<v Speaker 1>of related but on a commercial side, right? Because this

0:05:13.740 --> 0:05:18.140
<v Speaker 1>consumer stuff is terrible garbage. But now we're ruining everything

0:05:18.260 --> 0:05:21.370
<v Speaker 1>in industry with this kind of thing as well. Commercial

0:05:21.430 --> 0:05:26.110
<v Speaker 1>refrigeration units in many supermarkets, I think possibly as many

0:05:26.170 --> 0:05:28.909
<v Speaker 1>as 1,000 in France, this headline just came out this week,

0:05:29.370 --> 0:05:31.850
<v Speaker 1>were attacked by hackers because, of course, they have software

0:05:31.890 --> 0:05:34.490
<v Speaker 1>in them now and they're connected to the internet. They

0:05:34.510 --> 0:05:37.430
<v Speaker 1>were attacked by hackers. They were made to overheat. Yep.

0:05:38.589 --> 0:05:40.710
<v Speaker 1>Millions of pounds of food were ruined, and in some

0:05:40.750 --> 0:05:44.190
<v Speaker 1>cases they caught on fire. So even better, you come home,

0:05:44.310 --> 0:05:46.969
<v Speaker 1>your refrigerator has not only ruined your food, no longer works,

0:05:47.130 --> 0:05:49.229
<v Speaker 1>but it's burned your house down because of a bad

0:05:49.750 --> 0:05:52.980
<v Speaker 1>software update or hackers found it online using Shodan and

0:05:53.180 --> 0:05:53.900
<v Speaker 1>burned your house down.

0:05:54.300 --> 0:05:55.520
<v Speaker 2>Food for thought on that, Dave.

0:05:56.220 --> 0:05:58.860
<v Speaker 1>I know this sounds crazy to people, Brian. How can it?

0:05:58.860 --> 0:06:01.160
<v Speaker 1>That's partially why I started building this.

0:06:01.240 --> 0:06:03.160
<v Speaker 2>I know, but how can it sound crazy? You don't

0:06:03.200 --> 0:06:05.040
<v Speaker 2>come on the program to lie, Dave. You just pass

0:06:05.060 --> 0:06:05.920
<v Speaker 2>along the information.

0:06:06.700 --> 0:06:09.060
<v Speaker 1>Go look at the list I put together. It will

0:06:09.100 --> 0:06:12.280
<v Speaker 1>be mind-blowing to you folks. It will be mind-blowing how

0:06:12.360 --> 0:06:14.839
<v Speaker 1>these stories keep cropping up and they get worse and

0:06:14.860 --> 0:06:17.120
<v Speaker 1>worse and worse and worse. It's not just your privacy,

0:06:17.160 --> 0:06:19.599
<v Speaker 1>which is a huge problem in and of itself. It's

0:06:19.700 --> 0:06:22.820
<v Speaker 1>now these things that are connected in the physical world

0:06:23.180 --> 0:06:27.180
<v Speaker 1>can be manipulated and potentially hacked and weaponized. That's where

0:06:27.200 --> 0:06:28.700
<v Speaker 1>we're at. Stop buying this garbage.

0:06:28.779 --> 0:06:35.060
<v Speaker 2>DaveHatter.substack.com, intrustit.com, and of course LinkedIn. In.com is where you

0:06:35.089 --> 0:06:36.770
<v Speaker 2>can find Dave, and he also posts the articles there.

0:06:37.050 --> 0:06:37.330
<v Speaker 1>Pause.

0:06:37.350 --> 0:06:38.950
<v Speaker 2>We'll come back, and we'll talk about how it's, well,

0:06:39.029 --> 0:06:41.410
<v Speaker 2>it's hooked up to the Internet. Problems can happen.

0:06:41.589 --> 0:06:42.270
<v Speaker 1>Talk Station.

0:06:44.130 --> 0:06:48.630
<v Speaker 2>It's 642-55-KCB Talk Station, pivoting away from artificial intelligence, refrigerators,

0:06:48.670 --> 0:06:51.170
<v Speaker 2>and salt shakers. Oh, I forgot to mention Dave Hatter,

0:06:51.230 --> 0:06:55.130
<v Speaker 2>interestit.com's Dave Hatter. The salt shaker, in addition to having

0:06:55.180 --> 0:06:57.480
<v Speaker 2>an app, also is hooked up to Alexa, so it's

0:06:57.520 --> 0:06:59.159
<v Speaker 2>got a microphone and speaker.

0:07:00.279 --> 0:07:01.140
<v Speaker 1>What could go wrong, Brian?

0:07:01.260 --> 0:07:02.659
<v Speaker 2>Nothing. Absolutely nothing.

0:07:03.000 --> 0:07:03.180
<v Speaker 1>All right.

0:07:03.220 --> 0:07:05.740
<v Speaker 2>What happened over in Northern California where we had a

0:07:05.779 --> 0:07:06.900
<v Speaker 2>problem with malware?

0:07:08.080 --> 0:07:11.650
<v Speaker 1>Well, this is all part of the same problem. Software

0:07:11.690 --> 0:07:15.270
<v Speaker 1>and everything now, everything connected to the internet, all these interdependencies.

0:07:15.990 --> 0:07:18.870
<v Speaker 1>And Brian, we've talked about the concept of this many

0:07:18.930 --> 0:07:20.890
<v Speaker 1>times because this is one of the things that really

0:07:20.930 --> 0:07:23.790
<v Speaker 1>keeps me up at night. And you know me pretty well, Brian.

0:07:23.850 --> 0:07:26.330
<v Speaker 1>And people who don't know me that well often don't

0:07:26.370 --> 0:07:30.270
<v Speaker 1>realize that sometimes when I'm being hyperbolic, I'm being facetious

0:07:30.390 --> 0:07:33.420
<v Speaker 1>and other times I'm not. And Maybe I don't always

0:07:33.440 --> 0:07:35.800
<v Speaker 1>do the best job. Maybe I don't always do the

0:07:35.820 --> 0:07:38.520
<v Speaker 1>best job of helping you understand when I'm serious and

0:07:38.540 --> 0:07:41.860
<v Speaker 1>when I'm not. But this topic, as we used to

0:07:41.900 --> 0:07:44.030
<v Speaker 1>say back in the 80s when I was a kid,

0:07:44.450 --> 0:07:46.630
<v Speaker 1>serious is a heart attack, Brian. You know, I bet

0:07:46.650 --> 0:07:47.360
<v Speaker 1>you remember that one.

0:07:47.550 --> 0:07:49.250
<v Speaker 2>Oh, yeah. My dad used to say that all the time.

0:07:50.470 --> 0:07:51.970
<v Speaker 1>So critical infrastructure.

0:07:52.350 --> 0:07:52.510
<v Speaker 2>Right.

0:07:52.910 --> 0:07:55.290
<v Speaker 1>I keep bringing this up. I talk about this all

0:07:55.330 --> 0:07:59.280
<v Speaker 1>the time. We talk about it on your show. FBI

0:07:59.320 --> 0:08:02.860
<v Speaker 1>has defined 16 critical infrastructure sectors. We have seen increasing

0:08:02.920 --> 0:08:07.290
<v Speaker 1>attacks on the critical infrastructure sector as it becomes more automated,

0:08:07.410 --> 0:08:09.810
<v Speaker 1>as it becomes more interconnected, as we rely on it

0:08:09.870 --> 0:08:14.430
<v Speaker 1>more and more. All of this technology, and clearly I'm

0:08:14.450 --> 0:08:16.610
<v Speaker 1>not against technology. I made a whole career out of this.

0:08:17.090 --> 0:08:19.650
<v Speaker 1>What I'm increasingly concerned about the speed with which things

0:08:19.710 --> 0:08:23.800
<v Speaker 1>are being automated, the hard to understand, if not unknown

0:08:23.840 --> 0:08:26.500
<v Speaker 1>dependencies of this thing connected to that thing connected to

0:08:26.540 --> 0:08:29.250
<v Speaker 1>this thing over here creates In fact, I'm giving a

0:08:29.290 --> 0:08:32.130
<v Speaker 1>talk about this today at NKU at their cybersecurity conference.

0:08:32.860 --> 0:08:35.140
<v Speaker 1>But here's yet another example. You know, you and I

0:08:35.179 --> 0:08:39.100
<v Speaker 1>have talked 12 states over 100 water plants hacked. Yep.

0:08:39.380 --> 0:08:42.220
<v Speaker 1>You can't live long without water. Well, here's an example

0:08:42.240 --> 0:08:45.270
<v Speaker 1>of a 911 system that was knocked off a line. OK,

0:08:45.910 --> 0:08:49.190
<v Speaker 1>after a cyber attack. And it's not just the cyber

0:08:49.210 --> 0:08:51.900
<v Speaker 1>attacks that are the problem, Brian. One of the things

0:08:51.940 --> 0:08:54.340
<v Speaker 1>that got me out of the software engineering business and

0:08:54.520 --> 0:08:58.350
<v Speaker 1>focused exclusively on cybersecurity really was an article in The

0:08:58.380 --> 0:09:01.569
<v Speaker 1>Atlantic over 10 years ago called The Coming Software Apocalypse.

0:09:02.170 --> 0:09:06.450
<v Speaker 1>TMIT professors warning long before all, I mean, IoT was

0:09:06.510 --> 0:09:08.510
<v Speaker 1>a thing then. Smart devices were a thing, but not

0:09:08.550 --> 0:09:11.400
<v Speaker 1>like they are now. Warning that as we keep adding

0:09:11.460 --> 0:09:14.760
<v Speaker 1>software into things that probably don't really need software and

0:09:14.780 --> 0:09:17.600
<v Speaker 1>we create dependencies that are hard to understand because your

0:09:17.640 --> 0:09:21.460
<v Speaker 1>software is uses my software library, which calls some API,

0:09:21.500 --> 0:09:24.179
<v Speaker 1>which uses some other thing. You can't even know how

0:09:24.240 --> 0:09:27.170
<v Speaker 1>it works. And we're starting to see this come to

0:09:27.190 --> 0:09:30.470
<v Speaker 1>bear now. whether it's cyber attacks that bring these things

0:09:30.510 --> 0:09:33.860
<v Speaker 1>down or just faulty software. Like, you know, the Samsung

0:09:33.880 --> 0:09:36.440
<v Speaker 1>thing we just talked about wasn't a cyber attack. You

0:09:36.460 --> 0:09:38.920
<v Speaker 1>could argue it's a denial of service attack created by

0:09:38.960 --> 0:09:42.020
<v Speaker 1>the vendor because they denied service to the device by

0:09:42.080 --> 0:09:45.720
<v Speaker 1>bad software. It was a mistake. Brian, do you remember CrowdStrike,

0:09:45.900 --> 0:09:47.980
<v Speaker 1>the CrowdStrike thing a couple of years ago when this

0:09:48.059 --> 0:09:50.830
<v Speaker 1>CrowdStrike antivirus rolled out an update and it bricked like

0:09:50.830 --> 0:09:54.310
<v Speaker 1>10 million Windows computers? Delta was down for a while.

0:09:55.840 --> 0:09:59.900
<v Speaker 1>So it's not even cyber attacks. We're trying to rush

0:09:59.960 --> 0:10:05.280
<v Speaker 1>this stuff without thinking about security and robustness and privacy

0:10:05.380 --> 0:10:08.750
<v Speaker 1>and resilience. And here's an example where, again, this could

0:10:08.790 --> 0:10:11.130
<v Speaker 1>have been a software update that knocked this system offline.

0:10:11.230 --> 0:10:14.950
<v Speaker 1>You're having a heart attack. You call 911. No ambulance

0:10:14.970 --> 0:10:18.600
<v Speaker 1>shows up because the system's down. But in this case,

0:10:18.670 --> 0:10:21.080
<v Speaker 1>it was a cyber attack. Again, I want people to

0:10:21.120 --> 0:10:24.780
<v Speaker 1>get in their minds. It's not just cyber attacks. It's

0:10:25.940 --> 0:10:29.360
<v Speaker 1>who in your audience has not had a problem with software,

0:10:30.020 --> 0:10:34.390
<v Speaker 1>has not installed some software update, and their device stopped working, a.k.a.

0:10:34.470 --> 0:10:40.300
<v Speaker 1>was bricked. Ford just recently recalled 254,000 SUVs. Because a

0:10:40.380 --> 0:10:44.720
<v Speaker 1>software update impacted some of the safety capabilities. Look this up, folks.

0:10:45.640 --> 0:10:48.450
<v Speaker 1>It's on my substack, by the way, Brian, as is

0:10:48.510 --> 0:10:51.429
<v Speaker 1>this story. And I have a different substack where I'm

0:10:51.490 --> 0:10:54.290
<v Speaker 1>just listing all of the local government attacks like this

0:10:54.330 --> 0:10:58.840
<v Speaker 1>that I can find. Because local governments are frequently not

0:10:58.960 --> 0:11:03.620
<v Speaker 1>understanding the risks to their constituents about these things. So, again,

0:11:03.960 --> 0:11:07.960
<v Speaker 1>we're talking about a real-world situation, not some wacky software stuff.

0:11:08.020 --> 0:11:10.520
<v Speaker 1>I lost my photos. I had all my money stolen.

0:11:11.140 --> 0:11:13.750
<v Speaker 1>I'm having a heart attack. My kid got hit by

0:11:13.809 --> 0:11:17.950
<v Speaker 1>a car. My mom's having a stroke. I dial 911

0:11:17.950 --> 0:11:20.870
<v Speaker 1>to get the life-saving services that I expect and deserve

0:11:21.010 --> 0:11:23.950
<v Speaker 1>and paid for. They don't come because the system is down.

0:11:24.830 --> 0:11:27.210
<v Speaker 1>That's where we're at, folks. We are. That's where we're at.

0:11:27.270 --> 0:11:29.650
<v Speaker 2>Well, and you know what? That's even a lesser scenario

0:11:29.690 --> 0:11:32.550
<v Speaker 2>than the electricity being shut off by remote control. Dave?

0:11:34.730 --> 0:11:36.490
<v Speaker 1>I hate to be the doom guy, Brian, but we

0:11:36.510 --> 0:11:39.059
<v Speaker 1>have got to wake people up. We've got to slow

0:11:39.120 --> 0:11:41.500
<v Speaker 1>this stuff down. We've got to make sure that it

0:11:41.559 --> 0:11:46.730
<v Speaker 1>is focused on security and resilience first. Not speed to market,

0:11:46.790 --> 0:11:49.590
<v Speaker 1>not market share, not ease of use, not making money,

0:11:49.929 --> 0:11:53.190
<v Speaker 1>not collecting your data to make even more money. protecting

0:11:53.350 --> 0:11:57.610
<v Speaker 1>our society because it is increasingly at risk because of

0:11:57.630 --> 0:11:58.010
<v Speaker 1>this stuff.

0:11:58.350 --> 0:12:01.030
<v Speaker 2>OpenAI just got sued by eight states because they rushed

0:12:01.120 --> 0:12:04.860
<v Speaker 2>to get chat GPT out the door without maybe taking

0:12:04.920 --> 0:12:07.180
<v Speaker 2>its time and dealing with the errors that apparently they

0:12:07.200 --> 0:12:09.000
<v Speaker 2>were aware of when they rolled it out. Dave, don't

0:12:09.040 --> 0:12:11.020
<v Speaker 2>go away because you're going to talk about one of

0:12:11.059 --> 0:12:16.579
<v Speaker 2>my favorite subjects. The Talk Station. 652-55-KERCY The Talk Station.

0:12:16.620 --> 0:12:20.220
<v Speaker 2>Brian Thomas with intrustit.com's Dave Hatter. Thank you, Intrust IT,

0:12:20.260 --> 0:12:23.970
<v Speaker 2>for sponsoring it. And Dave Hatter, for providing all this very,

0:12:24.030 --> 0:12:26.890
<v Speaker 2>very useful information. And when can I get rid of

0:12:26.929 --> 0:12:29.420
<v Speaker 2>the idea of a connected car? Dave, you're talking about

0:12:29.440 --> 0:12:33.920
<v Speaker 2>software updates. Nothing really irks me more. Well, that's a

0:12:33.980 --> 0:12:34.580
<v Speaker 2>bold statement.

0:12:35.260 --> 0:12:36.300
<v Speaker 1>The idea that.

0:12:36.300 --> 0:12:40.230
<v Speaker 2>Your car comes with the equipment to, let's say, have

0:12:40.470 --> 0:12:43.150
<v Speaker 2>your seats heated, but you've got to pay a monthly

0:12:43.250 --> 0:12:46.320
<v Speaker 2>service to have it activated. I mean, I would not

0:12:46.440 --> 0:12:49.680
<v Speaker 2>consider a car that has that obligation. But then again,

0:12:49.960 --> 0:12:51.300
<v Speaker 2>if I had an option to buy a car that

0:12:51.400 --> 0:12:53.820
<v Speaker 2>isn't hooked up to the Internet at all, that's the

0:12:53.860 --> 0:12:54.720
<v Speaker 2>car I'd want to buy.

0:12:54.740 --> 0:12:58.370
<v Speaker 1>Yeah, I'm thinking I need a 78 Dodge Power Wagon

0:12:58.410 --> 0:12:59.589
<v Speaker 1>like on Simon &amp; Simon.

0:12:59.630 --> 0:13:00.390
<v Speaker 2>Try to find one.

0:13:00.429 --> 0:13:04.310
<v Speaker 1>Yeah. Where A, it doesn't have any software in it,

0:13:04.500 --> 0:13:07.600
<v Speaker 1>and B, you can't EMP it because it doesn't have

0:13:07.660 --> 0:13:08.380
<v Speaker 1>any chips either.

0:13:08.580 --> 0:13:10.940
<v Speaker 2>And those are all the rage these days. The prices

0:13:10.980 --> 0:13:12.740
<v Speaker 2>of those cars have gone through the roof. I mentioned

0:13:12.760 --> 0:13:15.540
<v Speaker 2>a 70s Ford Bronco earlier. I think those are like

0:13:15.980 --> 0:13:17.740
<v Speaker 2>collector car level prices these days.

0:13:18.700 --> 0:13:21.980
<v Speaker 1>So, Brian, yeah, I agree with you wholeheartedly. And again, folks,

0:13:22.700 --> 0:13:25.160
<v Speaker 1>I was a software engineer for 25 years. It's how

0:13:25.220 --> 0:13:27.880
<v Speaker 1>I made a living. This is what I did. So

0:13:28.460 --> 0:13:31.960
<v Speaker 1>I'm not against this stuff. I'm against the way it's

0:13:32.020 --> 0:13:35.319
<v Speaker 1>being done. I'm against the lack of focus on security

0:13:35.360 --> 0:13:38.300
<v Speaker 1>and privacy and the risk that it creates to each

0:13:38.370 --> 0:13:41.970
<v Speaker 1>of us and our entire society. So, yeah, your car

0:13:42.010 --> 0:13:44.790
<v Speaker 1>is basically a rolling computer now. And I've brought this

0:13:44.890 --> 0:13:49.230
<v Speaker 1>up before on my Substack. I've written articles about this.

0:13:49.830 --> 0:13:51.610
<v Speaker 1>Let me give you a headline here before we dive

0:13:51.630 --> 0:13:55.439
<v Speaker 1>into this specific topic. OK, Mozilla, the people that make

0:13:55.460 --> 0:13:58.200
<v Speaker 1>the Firefox web browser. By the way, you should stop

0:13:58.320 --> 0:14:01.569
<v Speaker 1>using everything from Google, including Chrome, and use a privacy

0:14:01.610 --> 0:14:05.429
<v Speaker 1>friendly browser like Firefox or Brave or Safari if you're

0:14:05.570 --> 0:14:08.969
<v Speaker 1>Apple exclusive. OK, these people know what they're talking about.

0:14:09.010 --> 0:14:11.469
<v Speaker 1>They have a website called Privacy Not Included. I bring

0:14:11.510 --> 0:14:14.830
<v Speaker 1>it up occasionally. They just review all of these sorts

0:14:14.870 --> 0:14:18.030
<v Speaker 1>of Internet of Things devices and show you how bad

0:14:18.090 --> 0:14:21.030
<v Speaker 1>they are for you as a consumer. They did an

0:14:21.210 --> 0:14:24.760
<v Speaker 1>expose on cars a few years ago. This is the headline.

0:14:25.040 --> 0:14:28.740
<v Speaker 1>All 25 car brands we researched earned our privacy not

0:14:28.820 --> 0:14:32.990
<v Speaker 1>included warning label, making cars the official worst category of

0:14:33.070 --> 0:14:38.910
<v Speaker 1>products for privacy that we have ever reviewed. Geez. Now, again,

0:14:39.110 --> 0:14:42.350
<v Speaker 1>these are technical people. They make software. They know what

0:14:42.370 --> 0:14:44.130
<v Speaker 1>they're talking about. Now, it was a couple years ago.

0:14:44.630 --> 0:14:47.510
<v Speaker 1>All modern cars are loaded with this garbage. Ford filed

0:14:47.550 --> 0:14:51.160
<v Speaker 1>a patent. that would allow their cars to eavesdrop on

0:14:51.200 --> 0:14:54.060
<v Speaker 1>you and sell you ads to your car. Also a

0:14:54.100 --> 0:14:57.120
<v Speaker 1>patent to recall your car autonomously when you don't pay.

0:14:58.450 --> 0:15:00.770
<v Speaker 1>You may recall GM had a big scandal because they

0:15:00.790 --> 0:15:03.050
<v Speaker 1>were selling your data that they're collecting from all this

0:15:03.090 --> 0:15:06.450
<v Speaker 1>garbage in your car to insurance companies. I try to

0:15:06.490 --> 0:15:09.170
<v Speaker 1>tell people, you know, if I drove to Columbus this

0:15:09.230 --> 0:15:11.570
<v Speaker 1>week to speak at an event, And do you think

0:15:11.750 --> 0:15:14.790
<v Speaker 1>if I accelerated really hard three times and braked really

0:15:14.830 --> 0:15:17.250
<v Speaker 1>hard four times, my insurance company might not like to

0:15:17.310 --> 0:15:19.510
<v Speaker 1>know that and might decide that if that's a pattern,

0:15:20.050 --> 0:15:22.390
<v Speaker 1>that maybe they should raise my rates and I would

0:15:22.410 --> 0:15:24.630
<v Speaker 1>never know why they went up. It's because my car

0:15:24.690 --> 0:15:29.580
<v Speaker 1>is dropping a dime on me. But back to this thing, yeah,

0:15:29.660 --> 0:15:34.880
<v Speaker 1>connected cars. It's not just the surveillance. Right. It's the well,

0:15:34.960 --> 0:15:38.520
<v Speaker 1>everything has software it now. It has the capability to

0:15:39.040 --> 0:15:41.300
<v Speaker 1>sell you subscriptions to use certain functions. Oh, we're going

0:15:41.320 --> 0:15:43.280
<v Speaker 1>to give you the heated steering wheel for three months

0:15:43.560 --> 0:15:45.800
<v Speaker 1>if you want it in month four. You got to

0:15:45.840 --> 0:15:50.120
<v Speaker 1>pay or heated seats or hey, you know, maybe you

0:15:50.140 --> 0:15:54.090
<v Speaker 1>can only set the air conditioner down to 72 unless

0:15:54.110 --> 0:15:59.010
<v Speaker 1>you pay a subscription as you make things smart, quote unquote.

0:15:59.500 --> 0:16:04.260
<v Speaker 1>You add the capability for external actors to control them,

0:16:04.820 --> 0:16:09.070
<v Speaker 1>to surveil you, to hack them and potentially weaponize them.

0:16:09.140 --> 0:16:12.410
<v Speaker 1>You may recall over the years, we've talked about this before,

0:16:12.890 --> 0:16:15.930
<v Speaker 1>over the years, there have been increasing concerns by people

0:16:15.970 --> 0:16:20.450
<v Speaker 1>in the business about vehicle security. All the way up

0:16:20.530 --> 0:16:22.910
<v Speaker 1>from tankers and so forth and airplanes, you mentioned the

0:16:22.960 --> 0:16:27.830
<v Speaker 1>Boeing thing. down to, you know, Mack trucks and cars.

0:16:27.910 --> 0:16:32.530
<v Speaker 1>Because imagine if I'm a hacker, a nation state adversarial hacker,

0:16:32.650 --> 0:16:35.620
<v Speaker 1>and I want to cause chaos. If I could hack,

0:16:35.670 --> 0:16:36.980
<v Speaker 1>and I'm just going to throw out a brand. I

0:16:37.200 --> 0:16:40.000
<v Speaker 1>don't want to slight any particular brand. Let's say Peterbilt trucks.

0:16:40.840 --> 0:16:45.380
<v Speaker 1>If every Peterbilt tractor out there that was hauling something,

0:16:45.820 --> 0:16:50.720
<v Speaker 1>including let's say 80,000 gallons of gasoline, could somehow be

0:16:50.780 --> 0:16:54.000
<v Speaker 1>weaponized so that the brakes stop working, Or you couldn't

0:16:54.020 --> 0:16:57.140
<v Speaker 1>stop it from accelerating. And even better, you could feed

0:16:57.180 --> 0:17:00.990
<v Speaker 1>into it certain coordinates through the GPS. And you could like, hey,

0:17:01.170 --> 0:17:04.690
<v Speaker 1>there's a nice local Duke power substation right over here.

0:17:05.230 --> 0:17:08.970
<v Speaker 1>Imagine what 80,000 gallons of gasoline exploding at the local

0:17:09.010 --> 0:17:10.670
<v Speaker 1>Duke substation would do to the power.

0:17:11.170 --> 0:17:13.530
<v Speaker 2>We could come up with scenarios for hours about how

0:17:13.570 --> 0:17:14.070
<v Speaker 2>bad this.

0:17:13.950 --> 0:17:17.139
<v Speaker 1>Could be, Dave. And I know this is crazy to people.

0:17:17.600 --> 0:17:21.970
<v Speaker 1>Don't take my word for it. Go look this stuff up. right?

0:17:22.170 --> 0:17:25.990
<v Speaker 1>But we just keep adding more and more. You only

0:17:26.030 --> 0:17:28.869
<v Speaker 1>hear people talking about the convenience and the awesomeness of

0:17:28.910 --> 0:17:31.550
<v Speaker 1>all of this. You never hear people talking about things

0:17:31.570 --> 0:17:33.970
<v Speaker 1>like right to repair, you know, and the fact that

0:17:34.230 --> 0:17:36.290
<v Speaker 1>you can't fix your own truck now because it has

0:17:36.369 --> 0:17:38.880
<v Speaker 1>software in it, and they claim intellectual property.

0:17:39.040 --> 0:17:40.880
<v Speaker 2>Since we're out of time, Dave, I'll just remind people,

0:17:40.940 --> 0:17:43.080
<v Speaker 2>that's why we have you here, to remind people of

0:17:43.119 --> 0:17:46.760
<v Speaker 2>the downside risk and to heed Dave's warning. Well-respected in

0:17:46.800 --> 0:17:49.580
<v Speaker 2>the tech community, Dave Hatter is, intrustit.com for