WEBVTT - Hack That Auto

0:00:04.200 --> 0:00:11.640
<v Speaker 1>Get in touch with technology with tex Stuff from dot com.

0:00:12.000 --> 0:00:15.320
<v Speaker 1>Hey there, and welcome to tech Stuff. I'm Jonathan Strickland

0:00:15.360 --> 0:00:20.040
<v Speaker 1>and joining me once again despite his incredibly busy schedule.

0:00:20.160 --> 0:00:23.239
<v Speaker 1>Possibly the busiest man at how stuff works dot Com

0:00:23.560 --> 0:00:27.280
<v Speaker 1>Ben Bowling, Oh gosh, hey, thank you for having me back,

0:00:27.360 --> 0:00:31.000
<v Speaker 1>and uh good to talk to everyone here in tech Stuff.

0:00:31.040 --> 0:00:34.000
<v Speaker 1>I do have to say I am, at best the

0:00:34.120 --> 0:00:37.600
<v Speaker 1>second or third busiest man. Uh. The dubious privilege of

0:00:37.640 --> 0:00:40.600
<v Speaker 1>the most busy probably goes to our super producer Noel

0:00:40.640 --> 0:00:46.040
<v Speaker 1>Brown Knowles Knowles pretty darn busy. Matt Frederick also really busy.

0:00:46.120 --> 0:00:49.280
<v Speaker 1>That's true. There's probably maybe five or six people that

0:00:49.320 --> 0:00:51.960
<v Speaker 1>you could all claim are the most busy person at

0:00:51.960 --> 0:00:54.720
<v Speaker 1>health stuff Works, and they would themselves be too exhausted

0:00:54.760 --> 0:00:57.760
<v Speaker 1>to argue the point. But Ben, of course, one of

0:00:57.800 --> 0:01:01.520
<v Speaker 1>the many shows that you are of is car Stuff.

0:01:01.560 --> 0:01:03.720
<v Speaker 1>And when I asked you if you would be interested

0:01:03.760 --> 0:01:06.600
<v Speaker 1>to come back onto tech stuff, and you didn't have

0:01:06.640 --> 0:01:08.520
<v Speaker 1>the heart to tell me. No, I said what would

0:01:08.560 --> 0:01:10.080
<v Speaker 1>you like to talk about? And you came up with

0:01:10.120 --> 0:01:13.039
<v Speaker 1>a ton of different suggestions, which really just means that

0:01:13.040 --> 0:01:15.880
<v Speaker 1>you're eventually going to cover all of them. But today

0:01:15.920 --> 0:01:18.360
<v Speaker 1>we're specifically looking at one of the ones I thought

0:01:18.360 --> 0:01:22.560
<v Speaker 1>was the most interesting, hacking a car. And the reason

0:01:22.600 --> 0:01:25.160
<v Speaker 1>why I think it's really fitting that we do this

0:01:25.240 --> 0:01:29.600
<v Speaker 1>is recently I did an episode with Shannon Morse and

0:01:29.720 --> 0:01:32.560
<v Speaker 1>she is one of the hosts of Hack five, and

0:01:32.600 --> 0:01:36.520
<v Speaker 1>she talks a lot about hacking and coding, including hacking

0:01:36.640 --> 0:01:39.319
<v Speaker 1>electronics and and she said, one of the things you

0:01:39.360 --> 0:01:42.120
<v Speaker 1>really wanted to get more into was the idea of

0:01:42.120 --> 0:01:46.480
<v Speaker 1>hacking vehicles and uh. And so I thought, well, this

0:01:46.520 --> 0:01:48.880
<v Speaker 1>is the perfect opportunity for us to expand on this

0:01:49.040 --> 0:01:52.800
<v Speaker 1>because we introduced it with Shannon's interview, and now we

0:01:52.840 --> 0:01:55.800
<v Speaker 1>can really dive into it and look into it. Now.

0:01:55.800 --> 0:01:59.560
<v Speaker 1>The fact that we're talking about this means that we

0:01:59.640 --> 0:02:05.440
<v Speaker 1>have to you confronts some kind of mythical versions of

0:02:05.480 --> 0:02:11.320
<v Speaker 1>the car hacking lifestyle, because we we've all seen depictions

0:02:11.360 --> 0:02:15.200
<v Speaker 1>of this in various like spy movies or television series.

0:02:15.480 --> 0:02:18.840
<v Speaker 1>So Ben, uh, I know that we've got these great

0:02:18.919 --> 0:02:22.440
<v Speaker 1>notes written down. I want to hear you actually read

0:02:22.520 --> 0:02:27.480
<v Speaker 1>out the opening paragraph, all right, in your most dramatic

0:02:27.560 --> 0:02:31.040
<v Speaker 1>kind of approach. Okay, the old inner world, Yes, okay,

0:02:31.120 --> 0:02:34.840
<v Speaker 1>all right. Now, to be fair, Jonathan I when I

0:02:34.880 --> 0:02:36.880
<v Speaker 1>was writing that, it hit me halfway through that I

0:02:36.960 --> 0:02:40.800
<v Speaker 1>wondered who would which of us would this would fall to? Okay,

0:02:40.880 --> 0:02:45.640
<v Speaker 1>so let's set the scene. Imagine that you're in an

0:02:45.720 --> 0:02:49.320
<v Speaker 1>action film driving on a curving road along the side

0:02:49.320 --> 0:02:53.000
<v Speaker 1>of a cliff, and suddenly the breaks don't work, the

0:02:53.040 --> 0:02:56.360
<v Speaker 1>accelerator jams, and as you careem over the side of

0:02:56.400 --> 0:02:59.320
<v Speaker 1>the road, a voice comes on over your radio saying

0:03:00.080 --> 0:03:04.919
<v Speaker 1>you've made a powerful enemy, old friend. The familiar voice

0:03:04.960 --> 0:03:08.400
<v Speaker 1>over your Bluetooth connection is no doubt making a pun.

0:03:08.520 --> 0:03:11.320
<v Speaker 1>Just as your vehicle, now turned into a jet trap,

0:03:11.680 --> 0:03:15.160
<v Speaker 1>hurdles into the abyss. This being a film, the car

0:03:15.200 --> 0:03:19.679
<v Speaker 1>instantly explodes. I have a nice trip. That's not quite right,

0:03:19.680 --> 0:03:23.240
<v Speaker 1>but you know that's I'm the master of the almost

0:03:23.280 --> 0:03:27.760
<v Speaker 1>but not quite appropriate pun. Um. So yeah, this is

0:03:27.840 --> 0:03:30.480
<v Speaker 1>this is something that I have actually seen in movies where,

0:03:30.800 --> 0:03:33.120
<v Speaker 1>you know, the old version of this would just be

0:03:33.240 --> 0:03:37.160
<v Speaker 1>someone's cut the brake line right. But now cars are

0:03:37.240 --> 0:03:40.600
<v Speaker 1>way more complicated than they used to be, and so

0:03:41.240 --> 0:03:43.680
<v Speaker 1>the question is could this actually happen? Could someone take

0:03:43.720 --> 0:03:48.440
<v Speaker 1>control of your car this way? And it's a little complicated,

0:03:48.760 --> 0:03:53.440
<v Speaker 1>and the answer kind of comes out to maybe, Yeah,

0:03:53.480 --> 0:03:57.880
<v Speaker 1>what do you mean by hacking? Yeah, yeah, So you've

0:03:57.880 --> 0:04:02.200
<v Speaker 1>got a great point in the notes. Cars are increasingly computerized.

0:04:02.200 --> 0:04:05.920
<v Speaker 1>There are more and more electronic systems within cars today.

0:04:06.280 --> 0:04:10.120
<v Speaker 1>So they used to be purely mechanical, right. You had

0:04:10.160 --> 0:04:13.440
<v Speaker 1>an engine that you know, a transmission that would transmit

0:04:13.560 --> 0:04:17.279
<v Speaker 1>the the reciprocal power of the engine into rotational force.

0:04:17.320 --> 0:04:21.560
<v Speaker 1>But the tires, you had breakes, you had steering. It

0:04:21.600 --> 0:04:24.560
<v Speaker 1>wasn't even power steering back in the day. These were

0:04:24.600 --> 0:04:28.960
<v Speaker 1>all mechanical systems right down to the windows. Yeah, so

0:04:29.000 --> 0:04:32.560
<v Speaker 1>you didn't have any sort of electronics. But that's not

0:04:32.640 --> 0:04:36.240
<v Speaker 1>the case anymore. Yeah, those are Now a car is

0:04:36.560 --> 0:04:41.680
<v Speaker 1>more like a series of interconnected digital networks and and

0:04:41.720 --> 0:04:44.200
<v Speaker 1>they could have dozens of computers talking to each other,

0:04:44.600 --> 0:04:48.520
<v Speaker 1>or we call these embedded systems often. And here's the thing, Jonathan,

0:04:48.720 --> 0:04:53.400
<v Speaker 1>their proprietary. So that means that these systems are not

0:04:53.560 --> 0:04:56.320
<v Speaker 1>just plug and play things you could stick into any car,

0:04:56.440 --> 0:04:59.680
<v Speaker 1>a GM car and you know, a Toyota would have

0:04:59.800 --> 0:05:04.560
<v Speaker 1>a different approach. Um, they're also not that smart. Yeah,

0:05:04.600 --> 0:05:06.760
<v Speaker 1>as it turns out, the proprietary thing is both a

0:05:06.800 --> 0:05:09.119
<v Speaker 1>good thing and a bad thing. Now often I say

0:05:09.320 --> 0:05:11.680
<v Speaker 1>I don't like the proprietary approach because I want to

0:05:11.680 --> 0:05:14.560
<v Speaker 1>have the choice as a consumer to be able to

0:05:14.560 --> 0:05:17.720
<v Speaker 1>put together a system. However, I like, I don't want

0:05:17.720 --> 0:05:20.039
<v Speaker 1>to be I don't want to be um, you know,

0:05:20.160 --> 0:05:25.720
<v Speaker 1>beholden to one company's approach, which is why I love

0:05:25.720 --> 0:05:28.600
<v Speaker 1>Apple's design. Don't get me wrong, but I'm not an

0:05:28.600 --> 0:05:31.680
<v Speaker 1>Apple guy because Apple products tend to only work with

0:05:31.760 --> 0:05:35.880
<v Speaker 1>other Apple products, or they they in their best implementation,

0:05:35.960 --> 0:05:38.440
<v Speaker 1>they work with Apple products. And if you try and

0:05:38.480 --> 0:05:41.200
<v Speaker 1>mix and match stuff, things start to fall apart pretty quickly,

0:05:41.560 --> 0:05:44.719
<v Speaker 1>and I like to have more of an open approach. However,

0:05:44.800 --> 0:05:47.839
<v Speaker 1>that being said, the experience I might have with that

0:05:47.880 --> 0:05:50.800
<v Speaker 1>open approach may never get to as good a one

0:05:50.960 --> 0:05:52.599
<v Speaker 1>as I would have if I just broke down and

0:05:52.600 --> 0:05:56.680
<v Speaker 1>bought all the Apple stuff. But the other side of

0:05:56.680 --> 0:05:58.760
<v Speaker 1>that is that with the proprietary approach, and we'll go

0:05:58.800 --> 0:06:01.599
<v Speaker 1>into this more later in the pie cast, uh, it

0:06:01.680 --> 0:06:04.479
<v Speaker 1>means that if you're trying to exploit the system, you

0:06:04.560 --> 0:06:07.760
<v Speaker 1>can't take a one one approach, right. One size does

0:06:07.800 --> 0:06:10.920
<v Speaker 1>not fit all, not a cookie cutter type thing, absolutely, uh,

0:06:11.080 --> 0:06:13.680
<v Speaker 1>and it's not. I guess what we're seeing is that

0:06:13.760 --> 0:06:18.880
<v Speaker 1>it's not as easy to you know hack uh multiple

0:06:19.000 --> 0:06:21.839
<v Speaker 1>cars or control of multiple cars. That will see a

0:06:21.880 --> 0:06:24.720
<v Speaker 1>couple exceptions that rule as it is to you know,

0:06:25.320 --> 0:06:28.480
<v Speaker 1>bot net a bunch of computers right right. You can't.

0:06:28.880 --> 0:06:32.039
<v Speaker 1>You can't build a virus that's going to affect the

0:06:32.240 --> 0:06:34.679
<v Speaker 1>entire fleet of cars out there. But you could write

0:06:34.680 --> 0:06:38.080
<v Speaker 1>a virus that exploits a particular vulnerability and an operating system,

0:06:38.400 --> 0:06:41.279
<v Speaker 1>and then any computer using that unpatched version of the

0:06:41.320 --> 0:06:44.839
<v Speaker 1>operating system would become vulnerable to that attack. So it

0:06:44.960 --> 0:06:47.960
<v Speaker 1>is a little different. It's not the same as uh,

0:06:48.360 --> 0:06:50.840
<v Speaker 1>hacking a computer. And keep in mind, hacking a computer

0:06:51.000 --> 0:06:53.240
<v Speaker 1>is not the same as what you'll see in a movie,

0:06:53.560 --> 0:06:56.000
<v Speaker 1>isn't it. It's not like it's not like that nineties

0:06:56.040 --> 0:06:59.080
<v Speaker 1>film Hackers. We can't just reroute the encryption or or

0:06:59.160 --> 0:07:01.960
<v Speaker 1>the or all all the different versions of hacking where

0:07:02.000 --> 0:07:04.760
<v Speaker 1>they show it as a character like suddenly you're an

0:07:04.760 --> 0:07:08.080
<v Speaker 1>avatar navigating through a maze and you actually encounter like

0:07:08.120 --> 0:07:11.440
<v Speaker 1>floating skull and crossbones and oh no, that's the that's

0:07:11.480 --> 0:07:14.320
<v Speaker 1>the firewall. I need to turn around, And that's not

0:07:14.400 --> 0:07:17.520
<v Speaker 1>what hacking is like. It made so many people's first

0:07:17.520 --> 0:07:21.560
<v Speaker 1>computer experience underwhelming. I've got oh, I've got something. This

0:07:21.560 --> 0:07:23.440
<v Speaker 1>a little bit of a sidebar. Do you know that

0:07:23.440 --> 0:07:26.960
<v Speaker 1>show The Strain? Yes, okay, have you watched it? I haven't.

0:07:27.040 --> 0:07:29.080
<v Speaker 1>It's on my list of things to watch, but I

0:07:29.120 --> 0:07:30.760
<v Speaker 1>haven't watched it yet. All Right, this is the one

0:07:30.760 --> 0:07:33.640
<v Speaker 1>with the virus that goes through the eye, right yeah, yeah, yeah,

0:07:33.720 --> 0:07:38.480
<v Speaker 1>it's a it's sort of a paradipe. Yeah, adaptation to

0:07:38.560 --> 0:07:41.520
<v Speaker 1>parasites science. But this is not really a spoiler because

0:07:41.520 --> 0:07:44.320
<v Speaker 1>it's a side note here one of and I mean

0:07:44.480 --> 0:07:46.559
<v Speaker 1>I say this with love because I've watched the show.

0:07:46.840 --> 0:07:49.480
<v Speaker 1>One of the dumbest things that happens and that show

0:07:49.920 --> 0:07:53.480
<v Speaker 1>is that there's a you know, there's a hacker lady character,

0:07:53.680 --> 0:07:57.000
<v Speaker 1>and she's she's crazy in this This billionaire finds her

0:07:57.120 --> 0:07:59.120
<v Speaker 1>and he wants to pay her an exorbitant amount of

0:07:59.160 --> 0:08:02.760
<v Speaker 1>money to get this slow down the internet. It's like

0:08:03.720 --> 0:08:07.960
<v Speaker 1>she's he says, we need you to slow down the internet,

0:08:08.080 --> 0:08:11.920
<v Speaker 1>and she just goes how slow, Like she has the

0:08:12.000 --> 0:08:14.320
<v Speaker 1>dial to the Internet on her a computer, like, well,

0:08:14.400 --> 0:08:16.840
<v Speaker 1>let me just crank this down to three and now

0:08:17.000 --> 0:08:20.000
<v Speaker 1>now everyone's working on a three speed as opposed to eleven.

0:08:20.080 --> 0:08:22.200
<v Speaker 1>It's exactly that and that doesn't even work in a car,

0:08:22.600 --> 0:08:26.000
<v Speaker 1>just for some perspective for people who want to know

0:08:26.160 --> 0:08:30.080
<v Speaker 1>more examples, You've got a pretty good, pretty comprehensive list

0:08:30.120 --> 0:08:33.520
<v Speaker 1>here of the various different things likely run by a

0:08:33.640 --> 0:08:36.520
<v Speaker 1>computer in the average person's car today. Yeah, you've got

0:08:36.520 --> 0:08:38.720
<v Speaker 1>a lot of different systems that are now electronic and

0:08:38.760 --> 0:08:41.840
<v Speaker 1>no longer mechanical. So here's just some that could be

0:08:41.920 --> 0:08:46.719
<v Speaker 1>connected to a microprocessor. Uh, the engine ignition, fuel injection,

0:08:47.280 --> 0:08:52.119
<v Speaker 1>missions controls, that's a big one, breaking steering, transmission controls,

0:08:52.200 --> 0:08:56.839
<v Speaker 1>collision avoidance systems, they definitely have microprocessors. Heating and air

0:08:56.880 --> 0:09:03.360
<v Speaker 1>conditioning systems, navigation systems, communication systems, entertainment systems, safety and

0:09:03.480 --> 0:09:06.480
<v Speaker 1>security systems. So that would include things like a safety

0:09:06.480 --> 0:09:09.240
<v Speaker 1>system might be anything from again, collision avoidance, that kind

0:09:09.240 --> 0:09:11.439
<v Speaker 1>of thing too. And security systems would be things like

0:09:11.520 --> 0:09:15.040
<v Speaker 1>a car alarm or the safety system might be the

0:09:15.120 --> 0:09:18.200
<v Speaker 1>way a dealership is able to track down a vehicle.

0:09:18.280 --> 0:09:21.520
<v Speaker 1>Let's say that you have reported as stolen vehicle. Some dealerships,

0:09:21.559 --> 0:09:26.600
<v Speaker 1>some car companies include systems that allow wherever you bought

0:09:26.600 --> 0:09:28.920
<v Speaker 1>the car from to be able to find where that

0:09:29.040 --> 0:09:32.400
<v Speaker 1>particular receiver is. Well, that receiver has to be able

0:09:32.400 --> 0:09:35.680
<v Speaker 1>to connect and communicate through a system somehow, So that's

0:09:35.880 --> 0:09:38.040
<v Speaker 1>you know, any time you talk about a system that

0:09:38.120 --> 0:09:41.959
<v Speaker 1>communicates to the outside world, that's a potential invasion vector.

0:09:43.360 --> 0:09:46.560
<v Speaker 1>That's where someone can get at your your car. Because

0:09:46.600 --> 0:09:48.720
<v Speaker 1>a lot of car, like a lot of cars, we

0:09:48.760 --> 0:09:50.720
<v Speaker 1>just look at them as closed systems, and a lot

0:09:50.720 --> 0:09:52.920
<v Speaker 1>of them are. A lot of them are totally closed off,

0:09:53.200 --> 0:09:57.400
<v Speaker 1>which means that your your invasion h vectors are limited.

0:09:57.640 --> 0:09:59.320
<v Speaker 1>And we'll talk more about that in a bit, but

0:09:59.360 --> 0:10:02.600
<v Speaker 1>at any rate, your typical car today has probably around

0:10:02.679 --> 0:10:05.840
<v Speaker 1>one hundred micro processors, and it maybe more, and within

0:10:05.880 --> 0:10:07.840
<v Speaker 1>the next few years that's going to double. We're gonna

0:10:07.840 --> 0:10:10.560
<v Speaker 1>see twice. In fact, I am I imagine a lot

0:10:10.600 --> 0:10:13.439
<v Speaker 1>of the cars that are coming out this year, especially

0:10:13.480 --> 0:10:16.520
<v Speaker 1>the high end luxury cars that tend to feature these systems,

0:10:16.600 --> 0:10:18.920
<v Speaker 1>before we see it rolled out to the general fleet,

0:10:19.640 --> 0:10:23.880
<v Speaker 1>they probably already are around two hundred microprocessors. Uh. In fact,

0:10:23.960 --> 0:10:26.400
<v Speaker 1>this this figure of a hundred microprocessors was in an

0:10:26.480 --> 0:10:28.480
<v Speaker 1>article from two thousand eleven, So it may even be

0:10:28.559 --> 0:10:31.200
<v Speaker 1>that your average car has two hundred by now, um

0:10:31.320 --> 0:10:35.559
<v Speaker 1>and and five miles of wiring to connect all those

0:10:35.600 --> 0:10:37.680
<v Speaker 1>systems are in the car. Yeah, that's one of my

0:10:37.760 --> 0:10:41.120
<v Speaker 1>favorite statistics that you're pulled up and and before we

0:10:41.160 --> 0:10:44.839
<v Speaker 1>go aiming further, now we we already i think did

0:10:44.840 --> 0:10:47.839
<v Speaker 1>an okay job of saying that, uh, what you've see

0:10:47.840 --> 0:10:50.280
<v Speaker 1>in hollywood's on what you've see in real life. But

0:10:50.480 --> 0:10:54.600
<v Speaker 1>we should also say that hacking in the way that

0:10:54.640 --> 0:10:56.760
<v Speaker 1>we're using it, which is a little bit more colloquial,

0:10:57.040 --> 0:11:00.360
<v Speaker 1>hacking is not necessarily something that a fee would do

0:11:00.400 --> 0:11:03.959
<v Speaker 1>to your car. Right. It's not necessarily an invasive technique

0:11:03.960 --> 0:11:07.480
<v Speaker 1>to take over a system. Right. Hacking just means that

0:11:07.559 --> 0:11:12.240
<v Speaker 1>you are using techniques to get a specific result, using

0:11:12.240 --> 0:11:15.120
<v Speaker 1>a system that wasn't necessarily intended to get that result.

0:11:15.440 --> 0:11:18.840
<v Speaker 1>So hackers can be of all shapes and sizes. They

0:11:18.840 --> 0:11:20.880
<v Speaker 1>can have all different types of interest. It doesn't have

0:11:21.000 --> 0:11:23.480
<v Speaker 1>to be a computer. You know, we've seen life hacks,

0:11:23.480 --> 0:11:26.800
<v Speaker 1>this idea of you want to achieve a specific outcome,

0:11:26.920 --> 0:11:29.520
<v Speaker 1>here's a cool way to do that. They're not always

0:11:29.520 --> 0:11:32.600
<v Speaker 1>the most elegant approach. It's not always the cleanest or

0:11:32.679 --> 0:11:35.920
<v Speaker 1>the simplest, but sometimes it's it's one that just works.

0:11:35.960 --> 0:11:37.800
<v Speaker 1>That's the goal of the hacker is to find a

0:11:37.840 --> 0:11:41.359
<v Speaker 1>way of making that outcome happen. So early computer programmers

0:11:41.360 --> 0:11:44.200
<v Speaker 1>were called hackers because they were hacking together code to

0:11:44.320 --> 0:11:48.040
<v Speaker 1>make something happen. And sure they might have used, you know,

0:11:48.160 --> 0:11:50.400
<v Speaker 1>twice as many lines of code then we're what was

0:11:50.559 --> 0:11:52.800
<v Speaker 1>strictly necessary, but they were just trying to get it

0:11:52.840 --> 0:11:56.720
<v Speaker 1>done in the time. Well, hackers with cars might be

0:11:56.760 --> 0:11:59.720
<v Speaker 1>hacking their own vehicles. It might not be in order

0:11:59.760 --> 0:12:03.040
<v Speaker 1>to try and sabotage a vehicle, but rather to change

0:12:03.120 --> 0:12:07.000
<v Speaker 1>the parameters that it can work within. So you might

0:12:07.120 --> 0:12:11.840
<v Speaker 1>want to, I don't know, make remove any limiting factors

0:12:12.320 --> 0:12:15.079
<v Speaker 1>and yeah, governors, things like that to to make your

0:12:15.080 --> 0:12:20.200
<v Speaker 1>car um work with greater horsepower or more torque or

0:12:20.840 --> 0:12:24.559
<v Speaker 1>moving a faster top speed. And there are a lot

0:12:24.600 --> 0:12:26.360
<v Speaker 1>of systems that are in place to limit that kind

0:12:26.360 --> 0:12:29.679
<v Speaker 1>of thing so that a car works within safety parameters, right,

0:12:29.840 --> 0:12:32.600
<v Speaker 1>because once you get beyond that, you start to really

0:12:32.679 --> 0:12:36.520
<v Speaker 1>test the strength of the vehicle and maybe that it

0:12:36.600 --> 0:12:40.040
<v Speaker 1>can't hold up to greater speeds over a certain amount.

0:12:40.080 --> 0:12:42.840
<v Speaker 1>And usually once you'll get as a car company that

0:12:42.920 --> 0:12:45.360
<v Speaker 1>will dial that back to within a safe limit and

0:12:45.400 --> 0:12:47.800
<v Speaker 1>say all right, well here's the maximum and it's well

0:12:47.920 --> 0:12:52.360
<v Speaker 1>below that that real top limit, which same sort of

0:12:52.360 --> 0:12:57.320
<v Speaker 1>thing we see with overclocking with microprocessors. So there are

0:12:57.360 --> 0:12:59.920
<v Speaker 1>some car hackers who will go in and they'll reef

0:13:00.040 --> 0:13:04.120
<v Speaker 1>flash the engine engine control unit or electronic control unit

0:13:04.160 --> 0:13:06.520
<v Speaker 1>that's e c U, and they'll go in and they'll

0:13:06.520 --> 0:13:09.640
<v Speaker 1>reflash it, which means that they will essentially start with

0:13:09.679 --> 0:13:13.160
<v Speaker 1>a clean slate and and um change a few of

0:13:13.200 --> 0:13:17.199
<v Speaker 1>the parameters can be really dangerous. By the way, Yeah,

0:13:17.280 --> 0:13:21.439
<v Speaker 1>we're not we are officially not recommending that you do this,

0:13:21.559 --> 0:13:24.800
<v Speaker 1>although it is interesting. Um and in some ways, I

0:13:24.800 --> 0:13:28.520
<v Speaker 1>think there's a very positive note. Statistically speaking, the person

0:13:28.720 --> 0:13:31.880
<v Speaker 1>most likely to hack your car is you. Yeah, that's

0:13:31.920 --> 0:13:35.880
<v Speaker 1>the best news. But it can be really dangerous or

0:13:35.960 --> 0:13:39.560
<v Speaker 1>at the very least, it can damage your vehicle to

0:13:39.600 --> 0:13:42.320
<v Speaker 1>the point where you can't drive it anymore. Or you

0:13:42.400 --> 0:13:45.040
<v Speaker 1>might do something where you're you're tweaking something in the

0:13:45.040 --> 0:13:48.560
<v Speaker 1>e CU, thinking that you're going to squeeze another fifteen

0:13:48.640 --> 0:13:51.000
<v Speaker 1>miles per hour out of the top speed, but turns

0:13:51.000 --> 0:13:55.120
<v Speaker 1>out instead what you've done is have it honking forever

0:13:55.720 --> 0:13:58.320
<v Speaker 1>and you can't stop it. Uh. And you know this

0:13:58.400 --> 0:14:02.800
<v Speaker 1>sort of stuff obvious avoids, warranties. You know there are

0:14:02.800 --> 0:14:05.440
<v Speaker 1>a lot of issues that if if things go wrong,

0:14:06.160 --> 0:14:09.719
<v Speaker 1>you could be stuck with the bill period. There might

0:14:09.720 --> 0:14:11.920
<v Speaker 1>not be any help for you. You might not be

0:14:12.000 --> 0:14:14.599
<v Speaker 1>able to get it covered by insurance or warranties, that

0:14:14.679 --> 0:14:17.720
<v Speaker 1>kind of thing, and you'll have to walk somewhere to pay. Yeah. Yeah,

0:14:17.760 --> 0:14:21.440
<v Speaker 1>So I've seen pictures of stuff like um uh, like

0:14:21.680 --> 0:14:25.320
<v Speaker 1>the the pistons that you would find within an engine,

0:14:25.400 --> 0:14:30.160
<v Speaker 1>just they're unrecognizable because they had been put through such

0:14:30.280 --> 0:14:32.920
<v Speaker 1>speed and force that it beat them out of the

0:14:33.560 --> 0:14:36.000
<v Speaker 1>shape that they were supposed to be in. So bad

0:14:36.040 --> 0:14:38.000
<v Speaker 1>things can happen if you don't know what you're doing,

0:14:38.120 --> 0:14:40.400
<v Speaker 1>and very few people really know what they're doing, and

0:14:40.440 --> 0:14:41.920
<v Speaker 1>in order to get into work you often have to

0:14:41.920 --> 0:14:45.240
<v Speaker 1>do stuff like tweak the fuel injection system, which you know,

0:14:45.280 --> 0:14:47.520
<v Speaker 1>if you don't know your physics and chemistry, you're not

0:14:47.560 --> 0:14:50.120
<v Speaker 1>going to get that mixed right and you could just

0:14:50.320 --> 0:14:53.520
<v Speaker 1>end up making your vehicle undrivable. And there are people,

0:14:53.560 --> 0:14:56.760
<v Speaker 1>of course, especially in the world of racing, who professionally

0:14:57.320 --> 0:15:00.680
<v Speaker 1>tune cars and to a degree hack them. Sure, but

0:15:00.920 --> 0:15:04.200
<v Speaker 1>keep in mind these are cars that are already built

0:15:04.200 --> 0:15:07.080
<v Speaker 1>for racing. They have a much lower lifespan and they're

0:15:07.120 --> 0:15:10.000
<v Speaker 1>only built to do one thing. Yeah, and you know,

0:15:10.080 --> 0:15:13.200
<v Speaker 1>the real issue we're having here is something that's kind

0:15:13.200 --> 0:15:15.560
<v Speaker 1>of you know, we didn't really mention this in the notes,

0:15:15.640 --> 0:15:18.440
<v Speaker 1>but something that we see throughout the industry, which is

0:15:18.480 --> 0:15:21.520
<v Speaker 1>that cars are getting so complicated with all these different

0:15:21.520 --> 0:15:25.560
<v Speaker 1>electronic systems that even people who are experienced mechanics can

0:15:25.720 --> 0:15:29.840
<v Speaker 1>encounter issues because you've got all these different proprietary systems,

0:15:30.200 --> 0:15:34.240
<v Speaker 1>you've got all these different electronic subsystems within the car,

0:15:34.920 --> 0:15:38.680
<v Speaker 1>and uh, you can't necessarily be an expert on everything

0:15:38.800 --> 0:15:43.120
<v Speaker 1>all the time. So yeah, it's it's tough for everybody

0:15:43.160 --> 0:15:46.160
<v Speaker 1>out there, like it's tough for professional mechanics now too. Yeah,

0:15:46.200 --> 0:15:47.800
<v Speaker 1>that's a really good point. I'm glad you made it

0:15:47.840 --> 0:15:50.800
<v Speaker 1>because this maybe is a little bit of a tangent

0:15:50.840 --> 0:15:53.280
<v Speaker 1>for us. But it is very important to note that,

0:15:53.400 --> 0:15:56.960
<v Speaker 1>just as you said, mechanics, especially mechanics who came up

0:15:57.080 --> 0:15:59.360
<v Speaker 1>under what I guess we would call the old school,

0:15:59.720 --> 0:16:04.880
<v Speaker 1>would ways now are increasingly finding that a higher number

0:16:04.920 --> 0:16:09.600
<v Speaker 1>of repairs require shipping to the manufacturer, which is not

0:16:09.640 --> 0:16:11.480
<v Speaker 1>what you want to hear when your car is broken down. Yeah,

0:16:11.480 --> 0:16:15.120
<v Speaker 1>if you're looking at any vehicle post nineteen. It's got

0:16:15.160 --> 0:16:17.600
<v Speaker 1>a lot of electronic systems in it, that's true, and

0:16:17.640 --> 0:16:20.360
<v Speaker 1>some of those are mandated, right. Yeah. In fact, that

0:16:20.440 --> 0:16:23.400
<v Speaker 1>was one of the reasons why the cars are the

0:16:23.400 --> 0:16:27.240
<v Speaker 1>way they are is because you had states like California

0:16:27.360 --> 0:16:29.640
<v Speaker 1>that had to put in emissions controls. I mean, we've

0:16:29.680 --> 0:16:32.280
<v Speaker 1>all seen the pictures of Los Angeles and the haze,

0:16:32.320 --> 0:16:35.640
<v Speaker 1>the pollution that hangs above the city, and so there

0:16:35.640 --> 0:16:37.760
<v Speaker 1>were there was a lot of incentive to try and

0:16:37.800 --> 0:16:39.440
<v Speaker 1>clean up the air as much as possible. Part of

0:16:39.480 --> 0:16:43.640
<v Speaker 1>that was controlling the emissions made from vehicles. So emission

0:16:43.640 --> 0:16:47.160
<v Speaker 1>control systems and emission detection systems became an important part

0:16:47.200 --> 0:16:50.560
<v Speaker 1>of vehicles within that state, and once people started to

0:16:50.600 --> 0:16:54.120
<v Speaker 1>develop onboard diagnostics systems to make sure that a car

0:16:54.200 --> 0:16:57.840
<v Speaker 1>was working within the right legal limits of emissions, that

0:16:58.160 --> 0:16:59.920
<v Speaker 1>rolled out to the rest of the United States and

0:17:00.000 --> 0:17:04.119
<v Speaker 1>became a requirement for all vehicles. And so a lot

0:17:04.200 --> 0:17:07.800
<v Speaker 1>of these were originally electronic systems that were designed to

0:17:07.880 --> 0:17:12.040
<v Speaker 1>make a particular model of car safer than previous models,

0:17:12.600 --> 0:17:16.640
<v Speaker 1>but because of their proved efficacy, they are now required

0:17:16.880 --> 0:17:19.399
<v Speaker 1>in all vehicles, not just you know, the ones that

0:17:19.480 --> 0:17:22.879
<v Speaker 1>they viewed it. So, uh, Scott and I talked about

0:17:22.920 --> 0:17:28.160
<v Speaker 1>how that is also driving the average price of cars up. Yeah. Yeah,

0:17:28.160 --> 0:17:30.679
<v Speaker 1>but they those those cars are getting more and more sophisticated,

0:17:30.760 --> 0:17:33.160
<v Speaker 1>they also get more and more expensive. But it also

0:17:33.200 --> 0:17:35.600
<v Speaker 1>means that, again, we have more and more systems that

0:17:35.880 --> 0:17:41.199
<v Speaker 1>could potentially be exploited. And by potentially we mean that

0:17:41.320 --> 0:17:44.800
<v Speaker 1>your car could be potentially exploited. By exploited, we mean

0:17:44.880 --> 0:17:49.280
<v Speaker 1>that there is proven research, peer reviewed. These guys went

0:17:49.320 --> 0:17:51.920
<v Speaker 1>to def Con. They're not just they're not just you know,

0:17:52.040 --> 0:17:55.080
<v Speaker 1>like you and mean Jonathan hanging out in a garage

0:17:55.080 --> 0:17:57.560
<v Speaker 1>and saying let's see what we can do. Yeah, they're

0:17:57.560 --> 0:18:02.639
<v Speaker 1>not They're not feorizing, right, They have actually done some

0:18:02.760 --> 0:18:06.760
<v Speaker 1>hacking to see how cars can be vulnerable to different

0:18:06.760 --> 0:18:11.200
<v Speaker 1>types of attacks. And you've got a pair of hackers

0:18:11.280 --> 0:18:13.640
<v Speaker 1>that that I think you want to talk about, right,

0:18:13.680 --> 0:18:17.440
<v Speaker 1>Oh yeah, yeah yeah. These would be Miller and Valisc

0:18:17.520 --> 0:18:19.719
<v Speaker 1>There two of the biggest names in the world of

0:18:19.760 --> 0:18:23.119
<v Speaker 1>car hacking research. Charlie Miller Chris Valisac. I want to

0:18:23.160 --> 0:18:26.080
<v Speaker 1>set this up for a quotation that maybe you could read,

0:18:26.359 --> 0:18:29.359
<v Speaker 1>um Miller is a or was at one time a

0:18:29.400 --> 0:18:33.720
<v Speaker 1>security engineer. Twitter valisc director of Security intelligence at a

0:18:33.800 --> 0:18:41.280
<v Speaker 1>Seattle consultancy called IOActive or IOActive, but they they received

0:18:41.320 --> 0:18:45.400
<v Speaker 1>an eighty thousand dollar grant from DARPA to research security

0:18:45.480 --> 0:18:49.040
<v Speaker 1>vulnerabilities of cars. And I think in this context it's

0:18:49.080 --> 0:18:51.120
<v Speaker 1>helpful to think of them as white hat hackers. Yeah,

0:18:51.160 --> 0:18:55.080
<v Speaker 1>they were specifically hired to say, can you can you

0:18:55.200 --> 0:18:59.440
<v Speaker 1>breach this cars systems and exploit it? Because we need

0:18:59.480 --> 0:19:01.800
<v Speaker 1>to know if that's a possibility, and we need to

0:19:01.800 --> 0:19:05.320
<v Speaker 1>know where the vulnerabilities are. That's definitely a white hat approach. Yes,

0:19:05.440 --> 0:19:08.480
<v Speaker 1>So we've got We've got a quotation from a summary

0:19:08.480 --> 0:19:12.840
<v Speaker 1>of their um groundbreaking two thousand eleven paper that if

0:19:13.480 --> 0:19:16.280
<v Speaker 1>absolutely here we go, I made you do the first one.

0:19:17.320 --> 0:19:20.080
<v Speaker 1>Previous research has shown that it is possible for an

0:19:20.119 --> 0:19:24.240
<v Speaker 1>attacker to get remote code execution on the electronic control

0:19:24.359 --> 0:19:28.960
<v Speaker 1>units ECU in automotive vehicles via various interfaces such as

0:19:28.960 --> 0:19:32.920
<v Speaker 1>the Bluetooth interface and the telematics unit. This paper aims

0:19:32.960 --> 0:19:35.480
<v Speaker 1>to expand on the ideas of what such an attacker

0:19:35.560 --> 0:19:38.760
<v Speaker 1>could do to influence the behavior of the vehicle after

0:19:38.960 --> 0:19:42.240
<v Speaker 1>that type of attack. So here's what they did. I

0:19:42.280 --> 0:19:45.000
<v Speaker 1>know that's in some dry language, but they're talking about

0:19:45.000 --> 0:19:49.719
<v Speaker 1>some frankly frightening stuff. They essentially they built the software

0:19:49.800 --> 0:19:54.680
<v Speaker 1>tools to uh enable a Mac laptop, going back to

0:19:54.760 --> 0:19:58.880
<v Speaker 1>Apple uh and and also back to Independence Day. Yeah, yes,

0:19:59.040 --> 0:20:01.240
<v Speaker 1>you're going to explore way to technology. You need to

0:20:01.320 --> 0:20:04.240
<v Speaker 1>use Apple computer in order to insert the code, right, Yeah,

0:20:04.359 --> 0:20:07.400
<v Speaker 1>just reroute the encryptions. That's a little callback for everybody

0:20:07.400 --> 0:20:11.000
<v Speaker 1>who listen to our previous series. Uh. Yeah. They plugged

0:20:11.040 --> 0:20:15.399
<v Speaker 1>into the diagnostic port of the car, which again, um,

0:20:15.680 --> 0:20:18.600
<v Speaker 1>there's an overwhelming chance, unless you're driving a classic car,

0:20:18.720 --> 0:20:21.199
<v Speaker 1>that you have one of these. Yeah. And and this

0:20:21.320 --> 0:20:23.280
<v Speaker 1>was one of those things that was mandated by law

0:20:23.440 --> 0:20:27.080
<v Speaker 1>because it allows a very quick assessment of how a

0:20:27.160 --> 0:20:31.160
<v Speaker 1>vehicle is performing. Yeah, and they they found because they

0:20:31.160 --> 0:20:34.480
<v Speaker 1>are white hat, they presented their software and their findings.

0:20:34.480 --> 0:20:37.160
<v Speaker 1>They want public and transparent with the two thousand thirteen

0:20:37.280 --> 0:20:40.600
<v Speaker 1>def con, and they wanted other researchers in on this

0:20:40.640 --> 0:20:43.560
<v Speaker 1>game to help find and fix the security flaws before

0:20:44.240 --> 0:20:50.639
<v Speaker 1>hackers or you know, incredibly sophisticated car thieves got to them. Usually,

0:20:50.760 --> 0:20:53.439
<v Speaker 1>like when we talk about malicious hackers, we often use

0:20:53.520 --> 0:20:57.080
<v Speaker 1>the term crackers, as in people who cracked the security

0:20:57.359 --> 0:21:00.480
<v Speaker 1>in order to exploit it. Ah, that's all right, you're

0:21:00.480 --> 0:21:02.240
<v Speaker 1>putting me on the game here. You know, it's just

0:21:02.359 --> 0:21:05.400
<v Speaker 1>one of those one of those terms I rarely bust out.

0:21:05.440 --> 0:21:08.159
<v Speaker 1>But that is in fact one because because hacker does

0:21:08.200 --> 0:21:11.720
<v Speaker 1>not necessarily mean malicious exactly, but it often has portrayed

0:21:11.760 --> 0:21:13.600
<v Speaker 1>such in the media. It's a it's a because it's

0:21:13.600 --> 0:21:15.720
<v Speaker 1>a shorthand way of saying, this person who wants to

0:21:15.720 --> 0:21:24.040
<v Speaker 1>get access to your stuff, this is crucial, this kind

0:21:24.080 --> 0:21:27.720
<v Speaker 1>of information. It's crucial because more and more cars have

0:21:28.000 --> 0:21:32.879
<v Speaker 1>onboard WiFi networks, each of which is to a degree proprietary. Know,

0:21:33.200 --> 0:21:37.720
<v Speaker 1>General Motors has on Star, Toyota's got Safety connect etcetera. Um.

0:21:37.760 --> 0:21:41.040
<v Speaker 1>But of course they are not the only researchers in

0:21:41.080 --> 0:21:42.920
<v Speaker 1>the game, and their methods, which we'll talk about in

0:21:42.960 --> 0:21:46.320
<v Speaker 1>a little bit, are not the only options because if

0:21:46.359 --> 0:21:50.440
<v Speaker 1>you recall earlier, ladies and gentlemen, we talked about an

0:21:50.480 --> 0:21:54.800
<v Speaker 1>exception to the rule of multi car hacking. Yeah, so

0:21:55.800 --> 0:21:58.680
<v Speaker 1>car dealerships. You know, I mentioned the idea of having

0:21:58.760 --> 0:22:01.120
<v Speaker 1>those systems in place you to be able to track

0:22:01.200 --> 0:22:04.400
<v Speaker 1>down a vehicle in case it's been stolen, and this

0:22:04.520 --> 0:22:07.160
<v Speaker 1>is becoming a standard feature in a lot of automobiles.

0:22:07.200 --> 0:22:11.560
<v Speaker 1>These days. In two thousand and ten, Omar Or Ramos Lopez,

0:22:11.640 --> 0:22:15.520
<v Speaker 1>who was a former employee of an Austin card dealership,

0:22:16.160 --> 0:22:20.480
<v Speaker 1>used the vehicle tracking system to get revenge. This is

0:22:20.480 --> 0:22:26.000
<v Speaker 1>where we see a well intentioned system, which is, you know,

0:22:26.080 --> 0:22:29.359
<v Speaker 1>designed to do one thing very well, can sometimes be

0:22:29.520 --> 0:22:34.200
<v Speaker 1>put to misuse by someone who has ulterior motives. Reminds

0:22:34.200 --> 0:22:35.680
<v Speaker 1>me of a lot of discussions I've had about the

0:22:35.760 --> 0:22:39.800
<v Speaker 1>n s A. Your your your intentions may have been pure,

0:22:39.960 --> 0:22:42.880
<v Speaker 1>but you've built a tool that humans use, and humans

0:22:42.920 --> 0:22:48.920
<v Speaker 1>have some pretty base desires occasionally. So the system allowed

0:22:49.040 --> 0:22:52.320
<v Speaker 1>the dealer to send wireless reminders about the linquent payments

0:22:52.400 --> 0:22:56.760
<v Speaker 1>to customers and also allowed this particular ex employee to

0:22:56.880 --> 0:23:02.080
<v Speaker 1>remotely hack the vehicles of nearly one people, which, uh

0:23:02.160 --> 0:23:04.439
<v Speaker 1>the result of the hack was that their car horns

0:23:04.440 --> 0:23:08.720
<v Speaker 1>started honking uncontrollably and disabled their the ignissions of their cars.

0:23:09.520 --> 0:23:12.040
<v Speaker 1>So not only was their car honking and honking and honking,

0:23:12.080 --> 0:23:15.920
<v Speaker 1>they could not you know, turn on the car. Wow.

0:23:15.960 --> 0:23:19.440
<v Speaker 1>And that's that's weird because ordinarily those functions which are

0:23:19.560 --> 0:23:24.480
<v Speaker 1>in that existing hardware are I imagine for people who

0:23:24.520 --> 0:23:27.280
<v Speaker 1>are not paying their car payment or their leasing or something,

0:23:27.400 --> 0:23:29.600
<v Speaker 1>or they have their car stolen, and that way, the

0:23:29.640 --> 0:23:33.000
<v Speaker 1>car suddenly becomes inoperable and it's making a nuisance of itself,

0:23:33.000 --> 0:23:36.320
<v Speaker 1>two things that you want if you have, say, police

0:23:36.760 --> 0:23:39.800
<v Speaker 1>out there looking for your stolen vehicle. Yeah, that's a

0:23:39.800 --> 0:23:43.679
<v Speaker 1>really good point. But Omar managed to hack the system.

0:23:43.680 --> 0:23:46.520
<v Speaker 1>Of course, he did later get arrested ladies and gentlemen,

0:23:46.560 --> 0:23:49.520
<v Speaker 1>which is how he knows his name. Yeah, and clearly

0:23:49.680 --> 0:23:53.520
<v Speaker 1>it was a an ultimately unsuccessful attempt because he didn't

0:23:53.520 --> 0:23:56.400
<v Speaker 1>get away clean. It was not a successful exploit. Now,

0:23:56.400 --> 0:23:59.080
<v Speaker 1>in many of the cases that you'll here mentioned about

0:23:59.119 --> 0:24:02.359
<v Speaker 1>car hacking in the news, there's this very important caveat

0:24:02.359 --> 0:24:05.080
<v Speaker 1>the hackers needed some sort of physical access to the

0:24:05.160 --> 0:24:08.560
<v Speaker 1>vehicle through its o b D the onboard diagnostic port.

0:24:08.800 --> 0:24:12.200
<v Speaker 1>And you know that that makes sense. So Valsake and

0:24:12.240 --> 0:24:15.639
<v Speaker 1>Miller plugging in the thing directly to a car or

0:24:16.240 --> 0:24:20.320
<v Speaker 1>Omar using pre existing hardware on the car, so they

0:24:20.320 --> 0:24:23.000
<v Speaker 1>have that access, and they have to have that to

0:24:23.040 --> 0:24:30.119
<v Speaker 1>get there right well mostly okay, So generally speaking, that

0:24:30.280 --> 0:24:32.439
<v Speaker 1>is the surest way to to be able to get

0:24:32.480 --> 0:24:35.200
<v Speaker 1>access to a car subsystems is being able to plug

0:24:35.280 --> 0:24:37.480
<v Speaker 1>physically into that car, which means they already have to

0:24:37.520 --> 0:24:40.040
<v Speaker 1>have physical access to the inside of your car, and

0:24:40.440 --> 0:24:43.440
<v Speaker 1>not to not to do a spoiler. But there's a

0:24:43.480 --> 0:24:45.399
<v Speaker 1>point I think that you make later in the notes

0:24:45.680 --> 0:24:48.479
<v Speaker 1>that it behooves us to bring up. Now, if you're

0:24:48.480 --> 0:24:51.040
<v Speaker 1>gonna go through that much trouble, there's probably other stuff

0:24:51.040 --> 0:24:53.680
<v Speaker 1>you can do to the person you're aiming at that

0:24:53.680 --> 0:24:55.440
<v Speaker 1>that you know, you can save a lot of time

0:24:55.440 --> 0:24:58.440
<v Speaker 1>and effort and not go to the trouble of getting

0:24:58.440 --> 0:25:01.280
<v Speaker 1>access to their vehicle, plugging in secretly without them knowing

0:25:01.359 --> 0:25:05.040
<v Speaker 1>about it, yes, and being redundant there, then inserting whatever

0:25:05.119 --> 0:25:08.400
<v Speaker 1>malicious code you have and and changing all of their

0:25:08.400 --> 0:25:12.440
<v Speaker 1>systems around and then leaving. That's a lot of that's

0:25:12.480 --> 0:25:14.879
<v Speaker 1>a lot of trouble, whereas you could do something like,

0:25:15.280 --> 0:25:19.320
<v Speaker 1>I don't know, disabled their their brake system, like physically

0:25:19.359 --> 0:25:23.280
<v Speaker 1>disabled their brake system. Yeah, so uh yeah, there's certainly

0:25:23.480 --> 0:25:26.560
<v Speaker 1>the possibility and the plausibility are two different things. But

0:25:26.600 --> 0:25:31.240
<v Speaker 1>then the idea of getting at a car without physically

0:25:31.280 --> 0:25:35.440
<v Speaker 1>plugging in is something that people are exploring because, as

0:25:35.440 --> 0:25:38.000
<v Speaker 1>you mentioned, a lot of these have these these various

0:25:38.040 --> 0:25:41.119
<v Speaker 1>communication systems that connect to the outside world. That's a

0:25:41.160 --> 0:25:44.360
<v Speaker 1>possible point of intrusion. Now, it all depends on whether

0:25:44.440 --> 0:25:46.960
<v Speaker 1>or not that system is connected to any other systems

0:25:46.960 --> 0:25:49.439
<v Speaker 1>in the car. Now, if you're talking about safety system,

0:25:49.440 --> 0:25:52.160
<v Speaker 1>it probably is at least on a diagnostic level, because

0:25:52.200 --> 0:25:54.320
<v Speaker 1>it has to be able to send an alert to

0:25:54.920 --> 0:25:59.000
<v Speaker 1>whatever agency is in charge of responding to those Right, So,

0:25:59.040 --> 0:26:01.119
<v Speaker 1>if you have a vehicle has a safety system in

0:26:01.160 --> 0:26:04.600
<v Speaker 1>it that can detect something wrong with your vehicle, send

0:26:04.640 --> 0:26:07.919
<v Speaker 1>that message off to a security firm whatever it may be,

0:26:08.040 --> 0:26:10.080
<v Speaker 1>like on Star is a great example. And then on

0:26:10.160 --> 0:26:15.240
<v Speaker 1>Star response, Well, that that that connection, that wireless communication

0:26:15.400 --> 0:26:17.840
<v Speaker 1>is a possible point of intrusion, and since it can

0:26:17.920 --> 0:26:21.800
<v Speaker 1>at least diagnose problems and systems, it may give people

0:26:22.119 --> 0:26:26.080
<v Speaker 1>the opportunity to mess with those systems. But this is

0:26:26.119 --> 0:26:28.800
<v Speaker 1>a big there's a lot of big ifs. These are

0:26:28.880 --> 0:26:31.000
<v Speaker 1>a lot of big gifts. But the research is there,

0:26:31.080 --> 0:26:34.159
<v Speaker 1>you know. Yeah, So you have the research from the

0:26:34.240 --> 0:26:37.600
<v Speaker 1>University of California and University of Washington hacking the controller

0:26:37.680 --> 0:26:42.359
<v Speaker 1>area network or CAN of an unnamed late model car,

0:26:43.440 --> 0:26:46.640
<v Speaker 1>and they were able to put in malicious commands through

0:26:46.680 --> 0:26:50.080
<v Speaker 1>the cars satellite radio. So I assume they made the

0:26:50.119 --> 0:26:54.240
<v Speaker 1>person listen to Robin Thick or something, right, I guess

0:26:54.240 --> 0:26:57.280
<v Speaker 1>not it's two thousand eleven blurredlines wasn't around yet, but no,

0:26:57.720 --> 0:27:03.239
<v Speaker 1>it was just him just that that's something that no

0:27:03.280 --> 0:27:07.760
<v Speaker 1>one should have to endure except possibly Alan Thick. But yeah,

0:27:08.000 --> 0:27:11.520
<v Speaker 1>So the idea was that they could sneak malicious commands

0:27:11.520 --> 0:27:13.840
<v Speaker 1>and actually it's a satellite radio, WiFi or a CD

0:27:14.040 --> 0:27:16.919
<v Speaker 1>containing the virus, which is interesting. I never would have

0:27:16.960 --> 0:27:21.560
<v Speaker 1>thought that a sound system presumably that's what you're putting

0:27:21.560 --> 0:27:24.480
<v Speaker 1>the CD into, or at least an entertainment system, that

0:27:24.480 --> 0:27:27.400
<v Speaker 1>that would have any kind of access to other important

0:27:27.400 --> 0:27:30.040
<v Speaker 1>systems within the car. But it may very well be

0:27:30.200 --> 0:27:33.960
<v Speaker 1>that it's connected to that same network, and then once

0:27:34.000 --> 0:27:35.879
<v Speaker 1>you have access to the network, you can start to

0:27:35.880 --> 0:27:39.080
<v Speaker 1>try and get access to some of the more critical subsystems,

0:27:39.400 --> 0:27:43.000
<v Speaker 1>things like power steering, which would be you know, catastrophic

0:27:43.040 --> 0:27:46.600
<v Speaker 1>obviously potentially. So yeah. One of the one of the

0:27:46.640 --> 0:27:49.000
<v Speaker 1>professors involved in some of these tests, a guy named

0:27:49.040 --> 0:27:53.760
<v Speaker 1>Stefan Savage Uh, said that these wireless hacks still remain possible.

0:27:53.840 --> 0:27:57.160
<v Speaker 1>Specifically said, the vulnerabilities that we found were the kind

0:27:57.200 --> 0:27:59.760
<v Speaker 1>that existed on PCs in the early to mid nineteen

0:27:59.800 --> 0:28:05.240
<v Speaker 1>hundreds when computers were first getting on the Internet. And uh,

0:28:05.600 --> 0:28:10.600
<v Speaker 1>here's I think the strangest example that I've read so far,

0:28:11.359 --> 0:28:15.040
<v Speaker 1>and maybe maybe readers and maybe you have a different one. Uh,

0:28:15.320 --> 0:28:18.960
<v Speaker 1>what if you could take a car's tire pressure monitoring

0:28:19.320 --> 0:28:23.159
<v Speaker 1>system and use that as a way to monitor the

0:28:23.280 --> 0:28:27.200
<v Speaker 1>movements of a car? To me, that sounds like a

0:28:27.359 --> 0:28:31.520
<v Speaker 1>sci fi writer was running out of ideas and season uh,

0:28:31.560 --> 0:28:37.120
<v Speaker 1>you know six of an anthology show, right, yeah, yeah,

0:28:37.280 --> 0:28:40.000
<v Speaker 1>and they said, let's make this next season six. But

0:28:41.240 --> 0:28:46.920
<v Speaker 1>the researchers from Rutgers University and University South Carolina demonstrated

0:28:47.640 --> 0:28:52.080
<v Speaker 1>in the possibility of this that's pretty incredible and it's

0:28:52.280 --> 0:28:55.160
<v Speaker 1>and they use the wireless seeing signals sent out by

0:28:55.160 --> 0:28:59.200
<v Speaker 1>the pressure monitoring system to to I guess, uh trace

0:28:59.320 --> 0:29:03.480
<v Speaker 1>ping's on. Yeah. Well, let's talk about some of the

0:29:03.520 --> 0:29:06.800
<v Speaker 1>other things that you could do potentially if you were

0:29:06.840 --> 0:29:11.040
<v Speaker 1>able to access a car's computer systems, keeping in mind

0:29:11.040 --> 0:29:14.640
<v Speaker 1>that most of these again are probably due to uh,

0:29:14.760 --> 0:29:18.600
<v Speaker 1>physically connecting with the vehicle and inserting yeah, as opposed

0:29:18.640 --> 0:29:20.760
<v Speaker 1>to you know, it's not like someone whipped out a

0:29:21.160 --> 0:29:24.520
<v Speaker 1>giant remote control and suddenly suddenly they make your car

0:29:24.640 --> 0:29:28.600
<v Speaker 1>feer left. But they could. We've mentioned honking the horn. Uh,

0:29:28.680 --> 0:29:33.000
<v Speaker 1>that's certainly possible. Uh. There was one about the Toyota

0:29:33.000 --> 0:29:35.680
<v Speaker 1>Prius and being able to slam its brakes when the

0:29:36.040 --> 0:29:39.960
<v Speaker 1>car is already traveling at high speed, thus uh, potentially

0:29:40.040 --> 0:29:42.600
<v Speaker 1>leading to a situation where the car gets out of control.

0:29:42.840 --> 0:29:44.560
<v Speaker 1>At the very least, it's going to lead to a

0:29:44.600 --> 0:29:46.520
<v Speaker 1>situation where the car is going to become a hazard

0:29:46.560 --> 0:29:48.760
<v Speaker 1>to anyone who's traveling at that same rate of speed

0:29:48.800 --> 0:29:52.760
<v Speaker 1>behind them. Uh. Then there's the killing the power steering.

0:29:52.840 --> 0:29:55.240
<v Speaker 1>Anyone who's ever driven a vehicle without power steering or

0:29:55.240 --> 0:29:58.880
<v Speaker 1>where the power steering has suddenly become uh inactive, knows

0:29:58.920 --> 0:30:01.480
<v Speaker 1>that that is no Joe. I mean that you really

0:30:01.520 --> 0:30:04.560
<v Speaker 1>don't know how much that power steering helps you until

0:30:04.600 --> 0:30:06.840
<v Speaker 1>you try and drive a vehicle that does not have it.

0:30:07.440 --> 0:30:11.200
<v Speaker 1>Um spoofing the GPS, So this would be a way

0:30:11.280 --> 0:30:14.280
<v Speaker 1>of making a car appear someplace where it's not actually

0:30:14.440 --> 0:30:19.280
<v Speaker 1>used a GPS spoofer for a while. Yeah, Um, I'm

0:30:19.320 --> 0:30:21.680
<v Speaker 1>not proud of it. It was for a really dumb

0:30:21.720 --> 0:30:23.800
<v Speaker 1>reason too. You want to know what it was. Okay,

0:30:23.840 --> 0:30:28.040
<v Speaker 1>So when I say dumb reason, I'm not saying anything like, um,

0:30:28.160 --> 0:30:33.400
<v Speaker 1>like illicit, or or or like salacious. I was using

0:30:33.400 --> 0:30:36.760
<v Speaker 1>a GPS spoofer because I had downloaded an app that

0:30:36.920 --> 0:30:41.040
<v Speaker 1>was a promotional app for a popular science fiction film,

0:30:41.120 --> 0:30:43.840
<v Speaker 1>and part of it would give you achievements for checking

0:30:43.920 --> 0:30:47.320
<v Speaker 1>in at certain physical locations. And some of those physical

0:30:47.360 --> 0:30:50.720
<v Speaker 1>locations because of the particular film I'm talking about, we're

0:30:50.720 --> 0:30:54.000
<v Speaker 1>located in San Francisco. I am not in San Francisco,

0:30:54.640 --> 0:30:57.920
<v Speaker 1>but I wanted those achievements, and so by spoofing my

0:30:57.960 --> 0:31:00.760
<v Speaker 1>GPS I could make it appear as if I were

0:31:00.800 --> 0:31:04.120
<v Speaker 1>in San Francisco at the specific locations, check into those

0:31:04.160 --> 0:31:09.120
<v Speaker 1>locations and get the achievements. It was Star Trek Star Trek, Yeah,

0:31:09.120 --> 0:31:11.680
<v Speaker 1>it was the j J Abrams Star Trek reboot. It

0:31:11.760 --> 0:31:15.920
<v Speaker 1>was actually Star Trek Into Darkness. To be specific. I

0:31:15.920 --> 0:31:18.600
<v Speaker 1>think I finally achieved the rank of captain. My wife

0:31:18.680 --> 0:31:22.360
<v Speaker 1>is an admiral, so that'll tell you. Isn't that against

0:31:22.360 --> 0:31:27.520
<v Speaker 1>Star Trek code. Look, look, if Captain Kirk can cheat

0:31:27.600 --> 0:31:30.560
<v Speaker 1>during the Kobe y Ashi Maru, then I can cheat

0:31:31.280 --> 0:31:34.240
<v Speaker 1>in the check in sport. But anyway, spoofing GPS is

0:31:34.360 --> 0:31:37.120
<v Speaker 1>that's a serious issue because let's say that the GPS

0:31:37.200 --> 0:31:40.520
<v Speaker 1>is tied to again the car monitoring system. If if

0:31:40.600 --> 0:31:43.560
<v Speaker 1>the car appears to be someplace that's not then any

0:31:43.600 --> 0:31:46.760
<v Speaker 1>sort of response physical response sent from say on Star

0:31:46.840 --> 0:31:50.000
<v Speaker 1>again is going to go to the wrong location. So

0:31:50.200 --> 0:31:54.160
<v Speaker 1>that's a real thing. Then there's a falsifying speedometers and odometers.

0:31:54.640 --> 0:31:56.720
<v Speaker 1>I mean it's falsifying an odometer that you can see

0:31:56.720 --> 0:32:02.640
<v Speaker 1>lots of ress. Um. There's violently making the vehicle just

0:32:02.920 --> 0:32:09.800
<v Speaker 1>jerk around not good um. And also they demonstrated that

0:32:09.880 --> 0:32:12.840
<v Speaker 1>they can exploit both of Toyota and Affords self parking

0:32:12.880 --> 0:32:16.800
<v Speaker 1>functions to hijack a vehicle steering, essentially turning it into

0:32:17.080 --> 0:32:20.320
<v Speaker 1>a primitive kind of remote controlled vehicle. And you you

0:32:20.360 --> 0:32:22.840
<v Speaker 1>can sort of see where that would come into play,

0:32:22.880 --> 0:32:27.360
<v Speaker 1>because obviously if you have a parallel parking automated system,

0:32:27.400 --> 0:32:29.400
<v Speaker 1>it has to be able to control the steering and

0:32:29.440 --> 0:32:31.360
<v Speaker 1>breaking of the vehicle in order for that to work.

0:32:31.480 --> 0:32:34.160
<v Speaker 1>So you just give it a new set of instructions. Yeah. Now,

0:32:34.280 --> 0:32:36.440
<v Speaker 1>again this is all stuff that you know, you would

0:32:36.480 --> 0:32:38.640
<v Speaker 1>have to have physical access to the vehicle first before

0:32:38.720 --> 0:32:41.640
<v Speaker 1>you could have introduced these problems. So if you're really

0:32:41.640 --> 0:32:44.440
<v Speaker 1>careful with the way your you know, your vehicle is

0:32:44.520 --> 0:32:46.760
<v Speaker 1>like your your vehicle secure, then you don't need to

0:32:46.760 --> 0:32:49.400
<v Speaker 1>worry about this so much. But yeah, that's that's a

0:32:49.440 --> 0:32:53.840
<v Speaker 1>good point. And before this becomes too uh too scary

0:32:53.880 --> 0:32:57.120
<v Speaker 1>for anybody, let's also keep in mind that when Miller

0:32:57.160 --> 0:33:01.360
<v Speaker 1>and val Sec were demonstrating these things, especially to a

0:33:01.360 --> 0:33:05.520
<v Speaker 1>couple of journalists, one of the guys was literally sitting

0:33:05.560 --> 0:33:10.920
<v Speaker 1>in the car with his laptop plugged in running the code. So, uh,

0:33:11.120 --> 0:33:13.360
<v Speaker 1>I guess if you see someone you don't know in

0:33:13.400 --> 0:33:16.120
<v Speaker 1>the backseat of your co there might be some other

0:33:16.200 --> 0:33:18.400
<v Speaker 1>questions you come up with before you actually get the

0:33:18.400 --> 0:33:21.640
<v Speaker 1>car in motion, right, Yeah, so it's not it's the

0:33:22.240 --> 0:33:26.240
<v Speaker 1>odds of you hopping into your two thousand ten preus

0:33:26.320 --> 0:33:29.800
<v Speaker 1>or escape and then finding that the car is completely

0:33:29.840 --> 0:33:34.000
<v Speaker 1>not under your control are very, very very low. Yeah.

0:33:34.120 --> 0:33:37.640
<v Speaker 1>The the point that these hackers were making was that

0:33:37.680 --> 0:33:41.600
<v Speaker 1>the vulnerabilities existed, and that the vulnerabilities could be addressed

0:33:41.880 --> 0:33:44.400
<v Speaker 1>and sealed up so that it would no longer be

0:33:44.440 --> 0:33:47.320
<v Speaker 1>a point of entry for a hacker. So it was

0:33:47.880 --> 0:33:51.040
<v Speaker 1>you know, they didn't need for the demonstration to be practical,

0:33:51.080 --> 0:33:54.080
<v Speaker 1>They just needed to show that, look, with enough work,

0:33:54.160 --> 0:33:58.000
<v Speaker 1>you can do this, and presumably if you're really determined

0:33:58.360 --> 0:34:01.760
<v Speaker 1>you could create, say a module that plugs into the

0:34:01.840 --> 0:34:06.360
<v Speaker 1>onboard diagnostic system and has a wireless communication with a laptop,

0:34:06.600 --> 0:34:08.160
<v Speaker 1>and then I don't have to be in the back

0:34:08.200 --> 0:34:12.200
<v Speaker 1>seat anymore because I can just send those the communications

0:34:12.239 --> 0:34:15.759
<v Speaker 1>straight through. But not that anyone's developed that, but rather

0:34:15.880 --> 0:34:18.920
<v Speaker 1>that we need to address the vulnerabilities that would make

0:34:18.960 --> 0:34:22.839
<v Speaker 1>such a thing possible. Yeah, exactly, And again just underlining

0:34:23.000 --> 0:34:26.800
<v Speaker 1>that if something is controlled by a computer in your car,

0:34:27.320 --> 0:34:31.920
<v Speaker 1>then another computer can be come involved and and anything

0:34:31.960 --> 0:34:34.840
<v Speaker 1>from your power windows to your breaking that function could

0:34:34.880 --> 0:34:38.920
<v Speaker 1>be hacked. We talked a little bit already about the

0:34:38.920 --> 0:34:41.920
<v Speaker 1>the evolution of the e c U, right. Yeah. The

0:34:41.960 --> 0:34:45.400
<v Speaker 1>whole point about these are these were systems made to

0:34:45.480 --> 0:34:50.360
<v Speaker 1>make either cars safer or to have a smaller environmental impact,

0:34:50.800 --> 0:34:53.160
<v Speaker 1>and that these were things that because they were because

0:34:53.200 --> 0:34:57.000
<v Speaker 1>of their benefits, they ended up being required, you know,

0:34:57.280 --> 0:35:00.080
<v Speaker 1>and you've got some you've got some great notes here

0:35:00.120 --> 0:35:04.760
<v Speaker 1>about the can bus. Ultimately, what what Millar and valis

0:35:04.840 --> 0:35:09.319
<v Speaker 1>act we're doing, is they're analyzing the can bus and

0:35:09.400 --> 0:35:12.719
<v Speaker 1>they're they're using that kind of like their skeleton key

0:35:12.800 --> 0:35:15.400
<v Speaker 1>or their highway. Now you can think of the can

0:35:15.560 --> 0:35:19.439
<v Speaker 1>bus that's sort of its own little maniature network. Uh

0:35:19.520 --> 0:35:22.080
<v Speaker 1>So think of it like, you know, think of the

0:35:22.480 --> 0:35:26.120
<v Speaker 1>Internet in microcosm, except it's all within the context of

0:35:26.160 --> 0:35:29.560
<v Speaker 1>a car. And the can is what pretty much allows

0:35:29.800 --> 0:35:35.440
<v Speaker 1>various uh subsystems to be interconnected, and it can interconnect

0:35:35.480 --> 0:35:39.120
<v Speaker 1>up to forty different systems for the different devices anyway,

0:35:39.520 --> 0:35:43.000
<v Speaker 1>and information travels at about one megabit per second, which is,

0:35:43.200 --> 0:35:47.520
<v Speaker 1>you know, compared to broadband speeds. Well in the United States,

0:35:47.520 --> 0:35:49.839
<v Speaker 1>broadband is defined as four megabits per second, so it's

0:35:49.840 --> 0:35:53.719
<v Speaker 1>really not that far behind, but it's it's uh more

0:35:53.840 --> 0:35:57.120
<v Speaker 1>than sufficient for the kind of data that the vehicle

0:35:57.200 --> 0:35:59.640
<v Speaker 1>tends to work in because it's not you know, it's

0:35:59.640 --> 0:36:02.800
<v Speaker 1>not con scarned with everything. It's concerned with very specific

0:36:02.880 --> 0:36:07.360
<v Speaker 1>systems like fuel injection or spedometer or that sort of stuff.

0:36:07.680 --> 0:36:11.080
<v Speaker 1>So it's definitely sufficient for that kind of thing. But

0:36:11.200 --> 0:36:13.840
<v Speaker 1>that is again, you know, anytime you have a system

0:36:13.880 --> 0:36:17.440
<v Speaker 1>where data is traveling around, then there's the potential of

0:36:17.520 --> 0:36:19.840
<v Speaker 1>exploiting it if you can get that point of entry.

0:36:20.040 --> 0:36:23.400
<v Speaker 1>So when they were defcon they explained this sort of stuff.

0:36:23.440 --> 0:36:26.600
<v Speaker 1>They also said that, uh, part of their process was

0:36:26.680 --> 0:36:30.799
<v Speaker 1>to get these proprietary messages. One of the most base

0:36:30.880 --> 0:36:33.360
<v Speaker 1>ways to think of it is speaking the language of

0:36:33.360 --> 0:36:37.120
<v Speaker 1>the car, right, and so by learning some of those links,

0:36:37.400 --> 0:36:41.520
<v Speaker 1>those phrases uh, in this tortured analogy I painted myself

0:36:41.560 --> 0:36:44.600
<v Speaker 1>into UH, they can replay these on a device that's

0:36:44.640 --> 0:36:48.520
<v Speaker 1>hooked up to the diagnostic connector ports, and then they

0:36:48.600 --> 0:36:52.000
<v Speaker 1>can uh influence the breaking in the steering. And then

0:36:52.320 --> 0:36:55.920
<v Speaker 1>as you said, they can also modify the existing firmware

0:36:56.280 --> 0:37:00.880
<v Speaker 1>so that they can still have this signal interplay without

0:37:00.960 --> 0:37:04.000
<v Speaker 1>having a guy in the back. Um. But to me,

0:37:04.239 --> 0:37:08.680
<v Speaker 1>it's interesting that this is not more of a big

0:37:08.719 --> 0:37:12.560
<v Speaker 1>deal externally with companies. You know, this seems like the

0:37:12.719 --> 0:37:15.239
<v Speaker 1>kind of thing that could easily become alarmist, and I'm

0:37:15.520 --> 0:37:20.480
<v Speaker 1>surprised that there hasn't already been more examination of it.

0:37:21.040 --> 0:37:22.560
<v Speaker 1>I think part of it is that we're still in

0:37:22.600 --> 0:37:25.840
<v Speaker 1>the early days right right now. It's in the hacker culture,

0:37:25.960 --> 0:37:30.279
<v Speaker 1>it's something that's being discussed, and in car culture, where

0:37:30.280 --> 0:37:32.680
<v Speaker 1>you have people who mod and tune their own cards.

0:37:32.760 --> 0:37:35.600
<v Speaker 1>It's being discussed, but usually from the perspective of how

0:37:35.640 --> 0:37:37.239
<v Speaker 1>can I make my car do something it was not

0:37:37.320 --> 0:37:39.480
<v Speaker 1>meant to do? Yeah, without how can I over clock

0:37:39.520 --> 0:37:43.319
<v Speaker 1>without falling apart right right from the hacker culture, it's

0:37:43.360 --> 0:37:47.279
<v Speaker 1>more about what are the potential vulnerabilities and either how

0:37:47.320 --> 0:37:49.359
<v Speaker 1>can I exploit them or how can I prevent them

0:37:49.360 --> 0:37:53.160
<v Speaker 1>from being exploited companies, I mean, bringing attention to it

0:37:53.200 --> 0:37:55.200
<v Speaker 1>is probably not something that most companies want to do.

0:37:55.239 --> 0:37:57.439
<v Speaker 1>They want to sell cars, but a lot of them

0:37:57.680 --> 0:38:01.320
<v Speaker 1>are definitely responding by saying, this is something we really

0:38:02.239 --> 0:38:04.160
<v Speaker 1>are concerned about. We want to make sure that our

0:38:04.280 --> 0:38:07.279
<v Speaker 1>our cars as as safe as possible. We take it

0:38:07.360 --> 0:38:11.319
<v Speaker 1>very seriously. We want to make sure that it's not

0:38:11.840 --> 0:38:16.719
<v Speaker 1>a trivial task to tap into one of these cars. So, yeah, exactly,

0:38:16.800 --> 0:38:20.960
<v Speaker 1>And the statements of various companies, of course, for its

0:38:21.040 --> 0:38:23.480
<v Speaker 1>is to take it very seriously. In other car companies

0:38:23.760 --> 0:38:26.759
<v Speaker 1>are saying that there is a differentiation that needs to

0:38:26.800 --> 0:38:31.680
<v Speaker 1>be made between hacking a car with physical access versus

0:38:31.960 --> 0:38:36.920
<v Speaker 1>remote hacking, and uh, for many car companies, the focus

0:38:37.000 --> 0:38:41.600
<v Speaker 1>is on preventing that kind of exploitation remotely. Well, yeah,

0:38:41.600 --> 0:38:44.200
<v Speaker 1>because that's the one that is more likely to like,

0:38:44.320 --> 0:38:47.040
<v Speaker 1>if it's a possible, that's the more likely vector because

0:38:47.080 --> 0:38:49.600
<v Speaker 1>it's the one that requires less work on the part

0:38:49.600 --> 0:38:51.560
<v Speaker 1>of the person who's trying to get access to the car.

0:38:52.040 --> 0:38:54.839
<v Speaker 1>You know, if if I find out the only way

0:38:54.880 --> 0:38:57.920
<v Speaker 1>that I'm going to be able to sabotage my enemies

0:38:58.000 --> 0:39:00.520
<v Speaker 1>vehicle is if I get physical access to the inside

0:39:00.560 --> 0:39:02.080
<v Speaker 1>of the vehicle, and then I have to be there

0:39:02.120 --> 0:39:04.800
<v Speaker 1>for a couple of hours while I reflashed the engine

0:39:04.800 --> 0:39:08.799
<v Speaker 1>control unit. That's not really that attractive to me. I mean,

0:39:08.840 --> 0:39:13.600
<v Speaker 1>do you have any enemies that, like I was gonna say,

0:39:13.600 --> 0:39:16.800
<v Speaker 1>I would wing man on that wing, but that would

0:39:16.800 --> 0:39:19.319
<v Speaker 1>take all afternoon. See Ben, what I'm telling you now

0:39:19.440 --> 0:39:22.319
<v Speaker 1>is that I didn't use this approach because I'm much

0:39:22.360 --> 0:39:25.560
<v Speaker 1>more efficient. But at any rate, uh the Yeah, if

0:39:25.600 --> 0:39:28.080
<v Speaker 1>you could get access remotely, then clearly that would be

0:39:28.120 --> 0:39:31.600
<v Speaker 1>a big draw for potential hackers. Now, they also point

0:39:31.600 --> 0:39:35.040
<v Speaker 1>out that it's usually a one on one kind of

0:39:35.080 --> 0:39:37.520
<v Speaker 1>thing that the approaches we've seen so far, with the

0:39:37.560 --> 0:39:42.920
<v Speaker 1>exception of exploiting the dealership system, which you know, again,

0:39:42.960 --> 0:39:45.120
<v Speaker 1>then you have to get access to the dealership system,

0:39:45.120 --> 0:39:48.359
<v Speaker 1>which is which is even more difficult at least presumably

0:39:48.560 --> 0:39:52.000
<v Speaker 1>than an individual vehicle. But because these are one on

0:39:52.000 --> 0:39:55.160
<v Speaker 1>one attacks, you would have to be targeted specifically. Now,

0:39:55.160 --> 0:39:57.960
<v Speaker 1>if you own a really high end luxury vehicle. That

0:39:58.080 --> 0:40:02.840
<v Speaker 1>might happen, right but the likelihood of having a vehicle

0:40:02.920 --> 0:40:06.560
<v Speaker 1>stolen if it's a high end luxury vehicle is already increased.

0:40:07.400 --> 0:40:10.400
<v Speaker 1>Right there. There are multiple there are multiple avenues that

0:40:10.440 --> 0:40:12.360
<v Speaker 1>people will go through in order to get hold of

0:40:12.400 --> 0:40:16.200
<v Speaker 1>that vehicle. Some of them might involve electronic hijacking, some

0:40:16.280 --> 0:40:18.719
<v Speaker 1>of them might involve just getting physical access to the

0:40:18.760 --> 0:40:21.000
<v Speaker 1>car and hot wiring the thing. I mean, it's you know,

0:40:21.120 --> 0:40:23.239
<v Speaker 1>that's that's a risk to take with a high end

0:40:23.320 --> 0:40:26.840
<v Speaker 1>luxury vehicle, and you usually will take uh, you know,

0:40:27.440 --> 0:40:30.759
<v Speaker 1>you'll take steps to prevent that from happening, hopefully, you know,

0:40:30.880 --> 0:40:34.359
<v Speaker 1>like possibly hiring a very large person to stand right

0:40:34.360 --> 0:40:37.040
<v Speaker 1>next to the vehicle and uh and discourage people from

0:40:37.040 --> 0:40:40.760
<v Speaker 1>getting too close. But um, yeah, because we're not getting

0:40:40.800 --> 0:40:45.640
<v Speaker 1>this kind of car communication where the cars are constantly

0:40:46.560 --> 0:40:53.000
<v Speaker 1>part of the larger Internet, then it's it's fairly it's

0:40:53.040 --> 0:40:57.000
<v Speaker 1>fairly safe right now from the remote attacks. As cars

0:40:57.040 --> 0:41:00.560
<v Speaker 1>get more and more Internet capable and Internet connected, then

0:41:00.600 --> 0:41:02.040
<v Speaker 1>you have to sit there and say, all right, well,

0:41:02.040 --> 0:41:05.319
<v Speaker 1>how is the car interacting with the Internet. Can that

0:41:05.400 --> 0:41:08.400
<v Speaker 1>be identified from an external source? If it could be identified,

0:41:08.440 --> 0:41:12.239
<v Speaker 1>can it also be exploited. And that's those are the

0:41:12.320 --> 0:41:14.720
<v Speaker 1>questions that are really going to be important to answer.

0:41:15.080 --> 0:41:17.600
<v Speaker 1>And I suspect we're going to see more and more

0:41:17.719 --> 0:41:19.839
<v Speaker 1>cars get this sort of Internet connection. I mean, we're

0:41:19.880 --> 0:41:23.319
<v Speaker 1>already seeing it with entertainment systems again, right, so you

0:41:23.520 --> 0:41:27.719
<v Speaker 1>have cars that have entertainment systems that do connect either

0:41:27.800 --> 0:41:31.040
<v Speaker 1>to the Internet via satellite or through the cellular network.

0:41:31.200 --> 0:41:34.960
<v Speaker 1>You know, however it may be, um, that's again a

0:41:35.080 --> 0:41:39.800
<v Speaker 1>potential point of entry, assuming that the subsystem is designed

0:41:39.800 --> 0:41:42.680
<v Speaker 1>to communicate with other systems. One way to prevent this

0:41:42.800 --> 0:41:44.960
<v Speaker 1>is to say, all right, well, which systems need to

0:41:45.000 --> 0:41:47.640
<v Speaker 1>talk to each other and which ones totally don't need

0:41:47.680 --> 0:41:50.720
<v Speaker 1>to talk to anything, And let's make sure that those

0:41:50.840 --> 0:41:53.680
<v Speaker 1>are boxed away so that if someone gets access to them,

0:41:53.719 --> 0:41:55.880
<v Speaker 1>the worst you're gonna get is they're making me listen

0:41:55.960 --> 0:42:00.919
<v Speaker 1>to I don't know, modern country. That would drive me crazy. Yeah,

0:42:01.480 --> 0:42:04.399
<v Speaker 1>you know, we could do an entirely different show on

0:42:04.800 --> 0:42:09.120
<v Speaker 1>modern country versus classic country. Yeah, okay, like Hank Williams Sr.

0:42:09.320 --> 0:42:14.880
<v Speaker 1>Brilliant man. But you know, okay, you're right, I'm not

0:42:14.880 --> 0:42:18.040
<v Speaker 1>gonna go down. I have I have some questions for

0:42:18.080 --> 0:42:22.440
<v Speaker 1>you as our resident tech expert UM and to ask

0:42:22.520 --> 0:42:24.239
<v Speaker 1>to set up one of these questions. First, I have

0:42:24.320 --> 0:42:27.120
<v Speaker 1>a have a short little anecdote here. In two thousand

0:42:27.239 --> 0:42:30.520
<v Speaker 1>thirteen is reported by the Guardian, there was a scientist

0:42:30.719 --> 0:42:34.839
<v Speaker 1>named Flavio Garcia, which name, which is a wonderful name.

0:42:35.160 --> 0:42:37.719
<v Speaker 1>I I had first assumed he was a name scientist.

0:42:37.880 --> 0:42:42.480
<v Speaker 1>But he had an academic paper that he had written

0:42:42.640 --> 0:42:46.680
<v Speaker 1>with several colleagues revealing the secret codes used to start

0:42:46.880 --> 0:42:50.960
<v Speaker 1>luxury cars out He's Bentley's and so on. And the

0:42:51.080 --> 0:42:54.239
<v Speaker 1>judge in the case, uh, there was there was a

0:42:54.280 --> 0:42:58.759
<v Speaker 1>suppression case right right, Uh to suppress the paper rights

0:42:58.800 --> 0:43:02.160
<v Speaker 1>some car companies wanted to us, and the judge ultimately

0:43:02.239 --> 0:43:06.480
<v Speaker 1>ruled that it should be suppressed. I think specifically this

0:43:06.600 --> 0:43:11.200
<v Speaker 1>was the parent company of Volkswagen, and the idea here

0:43:11.520 --> 0:43:16.120
<v Speaker 1>was um. The the idea was that the scientists, by

0:43:16.160 --> 0:43:20.600
<v Speaker 1>publishing this paper were endangering you know, hundreds of thousands

0:43:20.640 --> 0:43:24.799
<v Speaker 1>of car owners minimum and and even even if you

0:43:24.840 --> 0:43:27.880
<v Speaker 1>don't consider it a danger immediately, let's say that it

0:43:27.920 --> 0:43:32.160
<v Speaker 1>inspires the companies to do a recall, or that all

0:43:32.200 --> 0:43:36.080
<v Speaker 1>those customers go out to have this system changed. That's

0:43:36.120 --> 0:43:40.720
<v Speaker 1>a real monetary impact. Either to the owners or the

0:43:40.800 --> 0:43:45.040
<v Speaker 1>car companies or both to both most likely and uh

0:43:45.080 --> 0:43:48.520
<v Speaker 1>what they found in the course of the investigation was

0:43:48.560 --> 0:43:53.759
<v Speaker 1>that Garcia's team was deriving these codes but by cracking

0:43:53.840 --> 0:43:58.919
<v Speaker 1>the algorithms there. They used complex mathematical models to check

0:43:59.000 --> 0:44:02.399
<v Speaker 1>the software behind in the code. But here's the thing, man,

0:44:02.680 --> 0:44:05.879
<v Speaker 1>the code, they the process they were using in their

0:44:05.920 --> 0:44:08.880
<v Speaker 1>conclusion and stuff like that, we're in some pieces they

0:44:08.880 --> 0:44:13.799
<v Speaker 1>were available and since two thousand nine. So what my

0:44:13.920 --> 0:44:16.640
<v Speaker 1>question is with this, with this dilemma, and I think

0:44:16.640 --> 0:44:20.040
<v Speaker 1>it is, um, where where would you fall? Like professionally,

0:44:20.080 --> 0:44:24.120
<v Speaker 1>what's the idea here? Is this a case? Where is

0:44:24.160 --> 0:44:28.399
<v Speaker 1>this a case where security trump's transparency or I think so?

0:44:28.600 --> 0:44:32.080
<v Speaker 1>I think my my general philosophy and these matters, and

0:44:32.120 --> 0:44:34.600
<v Speaker 1>this goes to all sorts of all types of white

0:44:34.600 --> 0:44:40.680
<v Speaker 1>hat hacking. My general philosophy is that it is the

0:44:40.760 --> 0:44:46.080
<v Speaker 1>responsible thing to do is to alert whatever governing body,

0:44:46.160 --> 0:44:51.680
<v Speaker 1>whether that's a country, a company, uh, some some specific programmers, whatever,

0:44:51.760 --> 0:44:55.839
<v Speaker 1>whoever is responsible for the hacked system, to let them

0:44:55.840 --> 0:44:58.520
<v Speaker 1>know what the vulnerability is and to say, here is

0:44:58.560 --> 0:45:02.600
<v Speaker 1>how I exploited thatulnerability. You need to address this. I

0:45:02.680 --> 0:45:06.239
<v Speaker 1>think that's the responsible thing to do. It's also fair too,

0:45:06.600 --> 0:45:09.920
<v Speaker 1>I think to say that there is a vulnerability, that

0:45:10.000 --> 0:45:12.720
<v Speaker 1>you found a vulnerability, not to say what the vulnerability

0:45:12.760 --> 0:45:16.160
<v Speaker 1>is necessarily or how you exploited it, but that one

0:45:16.239 --> 0:45:19.120
<v Speaker 1>does exist because then it creates the incentive on the

0:45:19.200 --> 0:45:22.800
<v Speaker 1>part of the the person in charge to actually address

0:45:22.880 --> 0:45:25.280
<v Speaker 1>the problem and fix it. I see, So go straight

0:45:25.280 --> 0:45:28.919
<v Speaker 1>to the source, not to USA Today or something. Yeah,

0:45:28.920 --> 0:45:31.239
<v Speaker 1>I mean, go to the source first, and then give

0:45:31.280 --> 0:45:33.480
<v Speaker 1>the source enough time to sit there and at least

0:45:33.520 --> 0:45:37.000
<v Speaker 1>evaluate what you have said, and then go to the

0:45:37.080 --> 0:45:39.959
<v Speaker 1>press and say, all right, here's the deal. There's there's

0:45:40.000 --> 0:45:43.920
<v Speaker 1>this problem and if it's not addressed, then this is

0:45:43.960 --> 0:45:46.960
<v Speaker 1>what could happen. This is the potential outcome. Uh. And

0:45:47.040 --> 0:45:49.239
<v Speaker 1>that was you know, like the heart bleed bug is

0:45:49.239 --> 0:45:50.839
<v Speaker 1>a great example. You know, this is one of those

0:45:50.840 --> 0:45:53.359
<v Speaker 1>things where when you discover it, you kind of, I think,

0:45:53.360 --> 0:45:58.560
<v Speaker 1>have the responsibility to let people know, hey, there's this problem. Here,

0:45:58.640 --> 0:46:02.320
<v Speaker 1>here's how how exploited it, here's what needs to happen,

0:46:02.760 --> 0:46:07.040
<v Speaker 1>and then reveal it to everybody because the potential impact

0:46:07.320 --> 0:46:12.280
<v Speaker 1>is so great. But you don't actually unveil how step

0:46:12.320 --> 0:46:16.520
<v Speaker 1>by step to exploit the vulnerability that is irresponsible as well,

0:46:16.920 --> 0:46:19.480
<v Speaker 1>and that goes from white hat hacking to black hack

0:46:19.280 --> 0:46:22.120
<v Speaker 1>hacking in my mind. So I've seen this over and

0:46:22.160 --> 0:46:25.480
<v Speaker 1>over again in the in the computer world, where an

0:46:25.480 --> 0:46:28.800
<v Speaker 1>operating system comes out and someone or an operate system

0:46:28.840 --> 0:46:32.439
<v Speaker 1>that's been out forever, someone discovers that there's a vulnerability,

0:46:32.600 --> 0:46:36.000
<v Speaker 1>and generally speaking, what they do is they alert the

0:46:36.040 --> 0:46:42.040
<v Speaker 1>operating system, uh, you know, developer, and then after a

0:46:42.160 --> 0:46:44.080
<v Speaker 1>set amount of time, will say, all right, we found

0:46:44.120 --> 0:46:47.040
<v Speaker 1>a vulnerability. Here's what the vulnerability does. I'm not going

0:46:47.120 --> 0:46:49.080
<v Speaker 1>to tell you how to do it, but here's what

0:46:49.120 --> 0:46:52.279
<v Speaker 1>happens if someone exploits it and this company needs to

0:46:52.280 --> 0:46:55.279
<v Speaker 1>fix it, and that again puts that social pressure on

0:46:55.280 --> 0:46:57.360
<v Speaker 1>the company. Yeah, I see what you're seeing, and I

0:46:57.360 --> 0:47:00.280
<v Speaker 1>think that's I think that's a decent compromise. But between

0:47:00.320 --> 0:47:03.799
<v Speaker 1>the two principles and it sounds pretty ethical. And now

0:47:03.920 --> 0:47:06.239
<v Speaker 1>we go to Now we go to the question that

0:47:06.320 --> 0:47:11.560
<v Speaker 1>might be on everybody's mind. Uh so, wait, guys, Jonathan Ben,

0:47:11.880 --> 0:47:16.560
<v Speaker 1>will my car be hacked? Probably not, that's true. There's

0:47:16.600 --> 0:47:19.839
<v Speaker 1>no silver bullet hack. As we've said, and with the

0:47:19.840 --> 0:47:22.600
<v Speaker 1>exception of that dealer fleet. Um, you know, as you

0:47:22.680 --> 0:47:25.640
<v Speaker 1>as you point out Uh, someone would have to the

0:47:26.280 --> 0:47:29.560
<v Speaker 1>whomever would do this to you would have to have

0:47:30.120 --> 0:47:32.239
<v Speaker 1>a lot of time on their hands, a heck of

0:47:32.280 --> 0:47:34.719
<v Speaker 1>a lot of book smarts, right, and a lot of motivation,

0:47:35.000 --> 0:47:37.200
<v Speaker 1>a lot of They would have to have it out

0:47:37.239 --> 0:47:41.560
<v Speaker 1>for you specific must have done something really awful to

0:47:41.680 --> 0:47:45.439
<v Speaker 1>that person, kill their father and gave up fencing. Let's

0:47:45.480 --> 0:47:47.879
<v Speaker 1>let's just look at the the plots for taking one

0:47:47.920 --> 0:47:51.800
<v Speaker 1>through three. You've done something on those plots against Liam Neeson,

0:47:51.840 --> 0:47:54.160
<v Speaker 1>and he has the reason to hack your car now, right.

0:47:54.200 --> 0:47:57.600
<v Speaker 1>The truth of it is, it's just incredibly inconvenient to

0:47:57.680 --> 0:48:00.360
<v Speaker 1>do so. And if we look at I love that

0:48:00.400 --> 0:48:03.359
<v Speaker 1>you said, taken. But because if you look at all

0:48:03.440 --> 0:48:06.360
<v Speaker 1>the stuff we've said now, for something like this to

0:48:06.400 --> 0:48:11.480
<v Speaker 1>have to happen, honestly, those would be like action movie

0:48:11.520 --> 0:48:15.120
<v Speaker 1>problems that most people, uh hopefully don't have. Yeah, it's

0:48:15.160 --> 0:48:16.880
<v Speaker 1>the same sort of thing like if you if you

0:48:16.920 --> 0:48:19.160
<v Speaker 1>are flying back on Christmas and you have to go

0:48:19.200 --> 0:48:22.879
<v Speaker 1>to Naca Tomi Plaza, you're probably not gonna relive die hard.

0:48:24.200 --> 0:48:26.279
<v Speaker 1>You know, it's just it's it's an action movie thing,

0:48:26.320 --> 0:48:29.680
<v Speaker 1>not a real life thing. But uh, you know, it's

0:48:29.680 --> 0:48:32.520
<v Speaker 1>certainly one of the things that awareness is good because

0:48:32.560 --> 0:48:36.080
<v Speaker 1>we're getting into a more uh you know, the trend

0:48:36.120 --> 0:48:39.880
<v Speaker 1>of of computers and electronic systems getting getting more advanced

0:48:39.880 --> 0:48:42.560
<v Speaker 1>in cars is not going to reverse, it's going to continue,

0:48:42.560 --> 0:48:45.000
<v Speaker 1>it's gonna evolve, and we're getting closer and closer to

0:48:45.040 --> 0:48:47.839
<v Speaker 1>autonomous cars. Clearly, when you get to a system where

0:48:47.840 --> 0:48:51.399
<v Speaker 1>the car itself is taken over, then at least the

0:48:51.480 --> 0:48:55.040
<v Speaker 1>idea of the possibility of hacking becomes more realistic to people.

0:48:55.280 --> 0:48:58.080
<v Speaker 1>Keep in mind, the systems we talked about, they can

0:48:58.080 --> 0:49:02.080
<v Speaker 1>affect a manually controlled car. We're not suggesting that if

0:49:02.080 --> 0:49:04.040
<v Speaker 1>you have your hands on the wheel you can prevent

0:49:04.120 --> 0:49:06.880
<v Speaker 1>this from happening. But I think once you get to

0:49:06.880 --> 0:49:08.879
<v Speaker 1>the point where you no longer have to have your

0:49:08.880 --> 0:49:10.680
<v Speaker 1>hands on the wheel that you're on one of those

0:49:10.719 --> 0:49:12.880
<v Speaker 1>Google cars that can that doesn't even have a wheel,

0:49:13.560 --> 0:49:19.040
<v Speaker 1>the mindset is that, oh, computer is controlling this. Someone

0:49:19.080 --> 0:49:21.080
<v Speaker 1>could get control of the computer. It just seems like

0:49:21.120 --> 0:49:24.920
<v Speaker 1>it's more possible in that model, even though even though

0:49:24.920 --> 0:49:27.960
<v Speaker 1>it may not necessarily be more possible, But as we

0:49:28.000 --> 0:49:30.880
<v Speaker 1>get these cars that communicate more and more with the

0:49:30.920 --> 0:49:33.400
<v Speaker 1>outside world, then clearly that's something for us to keep

0:49:33.440 --> 0:49:36.560
<v Speaker 1>in mind. And uh. It also drives home a point

0:49:36.600 --> 0:49:40.080
<v Speaker 1>that Scott Benjamin and I made in our Autonomous Cars episode.

0:49:40.320 --> 0:49:43.719
<v Speaker 1>We talked about how early implementations all imagine that the

0:49:43.760 --> 0:49:46.160
<v Speaker 1>autonomous car was going to be part of a larger

0:49:46.200 --> 0:49:49.680
<v Speaker 1>autonomous system. Right, You're gonna have the the super Highway

0:49:49.719 --> 0:49:52.120
<v Speaker 1>of the future, and that was going to be the infrastructure,

0:49:52.360 --> 0:49:54.880
<v Speaker 1>and the cars were going to be largely passive and

0:49:54.920 --> 0:49:58.840
<v Speaker 1>receive direction from the outside world. Well, in that world,

0:49:58.880 --> 0:50:02.279
<v Speaker 1>you could definitely imagine a system that takes advantage of

0:50:02.320 --> 0:50:05.759
<v Speaker 1>that and sends conflicting commands to the cars that are

0:50:05.760 --> 0:50:10.200
<v Speaker 1>going down the road. But as we've seen this technology mature,

0:50:10.800 --> 0:50:13.520
<v Speaker 1>it turns out that it's all being self contained in

0:50:13.560 --> 0:50:17.360
<v Speaker 1>the vehicle. It's not dependent upon the environment outside the vehicle,

0:50:17.840 --> 0:50:20.239
<v Speaker 1>which means it's harder to get at that system so

0:50:20.280 --> 0:50:23.759
<v Speaker 1>that we benefit from that. So, um, I think that

0:50:24.080 --> 0:50:27.120
<v Speaker 1>because we didn't go in this world where all the

0:50:27.160 --> 0:50:30.120
<v Speaker 1>cars have to talk to each other, and we discovered no,

0:50:30.239 --> 0:50:31.759
<v Speaker 1>they don't really need to talk to each other. If

0:50:31.760 --> 0:50:35.160
<v Speaker 1>they have the sensors to detect each other, that's enough.

0:50:35.200 --> 0:50:38.080
<v Speaker 1>They don't actually have to have two way communication. Well,

0:50:38.120 --> 0:50:40.600
<v Speaker 1>then you start cutting down on those vectors we were

0:50:40.600 --> 0:50:44.160
<v Speaker 1>talking about. So just the way the technology is matured,

0:50:44.200 --> 0:50:47.320
<v Speaker 1>which I don't think has anything necessarily to do with security,

0:50:47.760 --> 0:50:51.040
<v Speaker 1>benefits us in a security way. I see what you're saying.

0:50:51.400 --> 0:50:56.439
<v Speaker 1>And to be completely candid, we know that we are

0:50:56.719 --> 0:51:03.520
<v Speaker 1>on the course of a very very swift evolution, not revolution,

0:51:03.880 --> 0:51:09.000
<v Speaker 1>because the progress made in automotive science, in uh just

0:51:09.080 --> 0:51:15.840
<v Speaker 1>electronic communication means that the cars children born today drive

0:51:15.880 --> 0:51:19.279
<v Speaker 1>are going to be radically different. They might not be driving. Yeah,

0:51:19.360 --> 0:51:22.239
<v Speaker 1>they That's That's where I'm getting at, man, they may

0:51:22.360 --> 0:51:25.359
<v Speaker 1>just not be driving. Henrik Kristensen over at Georgia Tech

0:51:25.640 --> 0:51:27.720
<v Speaker 1>made the prediction on one of my episodes of forward

0:51:27.760 --> 0:51:31.120
<v Speaker 1>thinking that children born today will never have to drive

0:51:31.160 --> 0:51:35.080
<v Speaker 1>a car because the cars of their generation will all

0:51:35.160 --> 0:51:37.960
<v Speaker 1>be like, at least a car that you you could

0:51:38.000 --> 0:51:41.480
<v Speaker 1>buy a car once they reached the driving age that

0:51:41.600 --> 0:51:44.960
<v Speaker 1>does all the driving for you and uh and it's

0:51:45.280 --> 0:51:47.000
<v Speaker 1>that's one of those things that's going to require a

0:51:47.000 --> 0:51:49.840
<v Speaker 1>lot of changes, not just in technology but in policies.

0:51:50.440 --> 0:51:52.520
<v Speaker 1>Um And there are a lot of important questions that

0:51:52.560 --> 0:51:55.200
<v Speaker 1>you have to answer personally. I think that most technologies

0:51:55.239 --> 0:51:57.359
<v Speaker 1>are going to be able to behave more responsibly than

0:51:57.400 --> 0:52:00.799
<v Speaker 1>people do. But that's because you know, I have a

0:52:00.800 --> 0:52:03.640
<v Speaker 1>lot of faith in the reaction time of a computer

0:52:03.880 --> 0:52:07.160
<v Speaker 1>compared to the reaction time of a human being. I've

0:52:07.200 --> 0:52:10.759
<v Speaker 1>seen I mean, look, I've played those games and those

0:52:10.800 --> 0:52:15.560
<v Speaker 1>computer bots that they cheat. Man, they are cheap. They

0:52:15.680 --> 0:52:19.200
<v Speaker 1>juggle you. It's terrible. But anyway, um, yeah, I mean

0:52:19.239 --> 0:52:21.839
<v Speaker 1>this this is one of those things that I'm glad

0:52:21.880 --> 0:52:24.240
<v Speaker 1>you brought it up. I'm glad that this was a

0:52:24.280 --> 0:52:29.040
<v Speaker 1>discussion we could have because, uh, it's it's certainly an

0:52:29.080 --> 0:52:31.560
<v Speaker 1>area that people are getting more and more interested in,

0:52:32.000 --> 0:52:35.680
<v Speaker 1>and there's so little information that the average person has

0:52:35.719 --> 0:52:38.960
<v Speaker 1>access to, and and we've seen so much in the

0:52:39.000 --> 0:52:42.560
<v Speaker 1>hacking world as far as computers go, that it could

0:52:42.719 --> 0:52:47.160
<v Speaker 1>very quickly escalate into a fear, uncertainty, and doubt. Uh

0:52:47.200 --> 0:52:51.640
<v Speaker 1>you know, chaos, right, Because you look and see the

0:52:51.760 --> 0:52:54.800
<v Speaker 1>kinds of exploits people have made with like credit card systems,

0:52:54.920 --> 0:52:57.440
<v Speaker 1>you think, well, what if we apply that same sort

0:52:57.480 --> 0:53:00.919
<v Speaker 1>of exploit system with a car that the results could

0:53:00.960 --> 0:53:05.080
<v Speaker 1>be devastating. Yeah, there was already a huge stink that

0:53:05.239 --> 0:53:09.839
<v Speaker 1>was raised when we in the United States there's this

0:53:09.920 --> 0:53:13.799
<v Speaker 1>mandate that's going to require every car to have the

0:53:13.840 --> 0:53:16.080
<v Speaker 1>equivalent of a black box like you would see on

0:53:16.080 --> 0:53:18.960
<v Speaker 1>a plane, right, just captures all the data. And there

0:53:19.040 --> 0:53:21.200
<v Speaker 1>was this huge stink raised about it when it hit

0:53:21.239 --> 0:53:24.359
<v Speaker 1>the news. Uh, so much of a huge stink that

0:53:24.440 --> 0:53:27.160
<v Speaker 1>people forgot to do their research and find out that

0:53:27.680 --> 0:53:31.040
<v Speaker 1>the vast majority of US cars have had those very

0:53:31.120 --> 0:53:34.799
<v Speaker 1>number of years. So it's I think you're right, uh,

0:53:35.280 --> 0:53:38.120
<v Speaker 1>if you're in the uncertainty, because we have such a

0:53:38.160 --> 0:53:41.719
<v Speaker 1>dichotomy and when we contemplate the future, it's dystopic or

0:53:41.760 --> 0:53:47.960
<v Speaker 1>it's utopian, you know, utopic, Yeah, yeah, exactly. We we

0:53:48.320 --> 0:53:51.759
<v Speaker 1>tend to see things in the the extreme ends of

0:53:51.800 --> 0:53:54.520
<v Speaker 1>the spectrum, and the truth is we're going to live

0:53:54.560 --> 0:53:57.239
<v Speaker 1>somewhere in the middle and if if we're lucky, it's

0:53:57.239 --> 0:54:00.960
<v Speaker 1>gonna be leaning heavier on the utopia side than the dystopia.

0:54:01.000 --> 0:54:05.600
<v Speaker 1>And if we're not observant and responsive, it'll definitely be

0:54:05.680 --> 0:54:09.680
<v Speaker 1>on the second one to dystopia rather than utopia. But um, yeah,

0:54:09.719 --> 0:54:13.400
<v Speaker 1>I think I think it's good to to just you know,

0:54:13.640 --> 0:54:16.399
<v Speaker 1>keep in mind that there are electronic systems in your car.

0:54:16.840 --> 0:54:21.600
<v Speaker 1>Electronic systems can fail just like any other system. Uh,

0:54:21.640 --> 0:54:26.160
<v Speaker 1>they can be sabotaged with the right amount of um

0:54:26.320 --> 0:54:30.120
<v Speaker 1>of vim and vigor and elbow grease. But it's probably

0:54:30.520 --> 0:54:34.719
<v Speaker 1>it's more likely than not it's never gonna happen to you, like,

0:54:34.840 --> 0:54:38.600
<v Speaker 1>far more likely than not um, at least in the

0:54:38.600 --> 0:54:43.120
<v Speaker 1>current iteration of the wave vehicles work. Uh, You're much

0:54:43.160 --> 0:54:48.000
<v Speaker 1>more likely to encounter something that would be a problem,

0:54:48.080 --> 0:54:50.560
<v Speaker 1>like a driver cutting you off in traffic, which happens

0:54:50.560 --> 0:54:53.880
<v Speaker 1>all the time and could lead to really disastrous results,

0:54:54.080 --> 0:54:57.759
<v Speaker 1>then you ever would be with someone hacking your car. Uh.

0:54:58.000 --> 0:55:00.799
<v Speaker 1>So I'm glad we could talk of out it. Uh.

0:55:00.840 --> 0:55:05.040
<v Speaker 1>It's really an interesting topic. Ben People can find your

0:55:05.080 --> 0:55:08.760
<v Speaker 1>work all over the darn place. With how stuff works.

0:55:08.840 --> 0:55:11.680
<v Speaker 1>You are a host of car stuff. Along with Scott Benjamin,

0:55:12.080 --> 0:55:13.960
<v Speaker 1>you are a host of stuff they don't want you

0:55:14.000 --> 0:55:16.080
<v Speaker 1>to know. Along with Matt Frederick, you are one of

0:55:16.120 --> 0:55:20.840
<v Speaker 1>the many hosts of brain stuff. I am also occasionally

0:55:20.840 --> 0:55:24.920
<v Speaker 1>on brain stuff. Are you doing what the stuff? We're

0:55:25.000 --> 0:55:28.200
<v Speaker 1>both on what the stuff? Uh? I don't even know

0:55:28.280 --> 0:55:30.799
<v Speaker 1>what shows I host anymore, so I have to ask

0:55:30.840 --> 0:55:34.160
<v Speaker 1>you which ones you do? Have I missed any you

0:55:34.280 --> 0:55:37.840
<v Speaker 1>will know? We're I think those are most of the

0:55:38.480 --> 0:55:42.440
<v Speaker 1>food science Oh, food stuff stuff your food stuff? Okay, now,

0:55:42.600 --> 0:55:46.480
<v Speaker 1>folks on got another another final little tangent. If you

0:55:46.600 --> 0:55:49.840
<v Speaker 1>have not watched the How Stuff Works Food Stuff episodes,

0:55:50.400 --> 0:55:52.799
<v Speaker 1>you have got to do that, and you need to

0:55:52.840 --> 0:55:57.520
<v Speaker 1>do them in order because there's the narratives from one

0:55:57.560 --> 0:56:01.200
<v Speaker 1>episode to the next, so it does actually progress. And

0:56:01.280 --> 0:56:04.319
<v Speaker 1>you will also see occasionally other people from How Stuff

0:56:04.320 --> 0:56:07.800
<v Speaker 1>Works pop up. Joe McCormick, who is one of the

0:56:08.400 --> 0:56:11.799
<v Speaker 1>hosts of Forward Thinking podcast and also one of the

0:56:11.800 --> 0:56:14.600
<v Speaker 1>writers for Forward Thinking. He pops up in a recent

0:56:14.680 --> 0:56:20.520
<v Speaker 1>episode and they are informative and they really exercise the

0:56:20.560 --> 0:56:23.880
<v Speaker 1>comedic chops of Mr Ben Boland and Ms Kristen Conger,

0:56:24.160 --> 0:56:27.480
<v Speaker 1>both of whom are brilliant improvisers. So you've got to

0:56:27.520 --> 0:56:29.800
<v Speaker 1>treat yourself and go check out the Food Stuff So

0:56:29.960 --> 0:56:35.279
<v Speaker 1>it's they're fantastic. Wow, that's high. That's high. It's I'm

0:56:35.320 --> 0:56:37.120
<v Speaker 1>buttering you up so that you put me on the show.

0:56:38.280 --> 0:56:40.960
<v Speaker 1>I want to be on an episode, but I'll have

0:56:41.000 --> 0:56:43.480
<v Speaker 1>to come up with whatever the topic will be. But anyway, guys,

0:56:44.360 --> 0:56:46.719
<v Speaker 1>check out those shows. Remember you can get in touch

0:56:46.719 --> 0:56:49.040
<v Speaker 1>with tech stuff. Let's know, any suggestions you might have

0:56:49.080 --> 0:56:52.160
<v Speaker 1>for future episodes. Maybe there's another guest that you want

0:56:52.160 --> 0:56:54.319
<v Speaker 1>to have back. Maybe maybe you're thinking, Hey, we gotta

0:56:54.360 --> 0:56:56.400
<v Speaker 1>have Ben back on the show as soon as possible.

0:56:56.680 --> 0:56:58.839
<v Speaker 1>Let me know. Send me an email. My address is

0:56:58.880 --> 0:57:01.600
<v Speaker 1>tech Stuff at how stuff works dot com, or you

0:57:01.640 --> 0:57:04.960
<v Speaker 1>can drop me a line on Facebook, Twitter, or Tumblr.

0:57:04.960 --> 0:57:07.840
<v Speaker 1>The handle it all three is tech stuff H s W.

0:57:08.440 --> 0:57:10.719
<v Speaker 1>And I'll talk to you again, really soon