WEBVTT - Lock and Key

0:00:00.160 --> 0:00:07.160
<v Speaker 1>Brought to you by Toyota. Let's go places. Welcome to

0:00:07.360 --> 0:00:15.240
<v Speaker 1>Forward Thinking, Pater and welcome to Forward Thinking, the podcast

0:00:15.320 --> 0:00:17.279
<v Speaker 1>that looks at the future and says they take you

0:00:17.360 --> 0:00:21.000
<v Speaker 1>away and throw away the key. I'm Jonathan Strickland, I'm

0:00:21.079 --> 0:00:23.840
<v Speaker 1>Lauren bo and I'm Joe McCormick, and i want to

0:00:23.840 --> 0:00:26.439
<v Speaker 1>ask you guys a question. I'll go to the prom

0:00:26.440 --> 0:00:31.080
<v Speaker 1>with you. You guys are so sweet. It wasn't the prom,

0:00:31.120 --> 0:00:34.440
<v Speaker 1>it was the enchantment under the seat. That's thank goodness,

0:00:34.479 --> 0:00:37.240
<v Speaker 1>because it's two thousand and fifteen. You know what year

0:00:37.320 --> 0:00:40.239
<v Speaker 1>that is. To the future too. Anyway, what's your what's

0:00:40.240 --> 0:00:42.880
<v Speaker 1>your actual question? No, no, no, I may have made

0:00:42.880 --> 0:00:45.280
<v Speaker 1>this comparison before, but I've got to make it again.

0:00:46.159 --> 0:00:51.400
<v Speaker 1>Do you remember all the Internet paranoia in the nineties, Yeah, yeah,

0:00:51.520 --> 0:00:54.840
<v Speaker 1>And so thinking back on it now, it's often very

0:00:54.960 --> 0:00:58.560
<v Speaker 1>funny because we were all thinking back then, oh no,

0:00:58.720 --> 0:01:02.160
<v Speaker 1>what if evil techno criminals used the net to do

0:01:02.240 --> 0:01:06.000
<v Speaker 1>horrible things? And and it's funny how some of the

0:01:06.040 --> 0:01:09.160
<v Speaker 1>fears we had back then turned out to be hilariously

0:01:09.319 --> 0:01:12.640
<v Speaker 1>wrong and overblown, you know, like Sandra Bullock gets caught

0:01:12.640 --> 0:01:16.119
<v Speaker 1>in the net. Yeah, it turns out. She was perfectly fine.

0:01:16.160 --> 0:01:18.280
<v Speaker 1>She never got she got caught in a net, but

0:01:18.319 --> 0:01:21.920
<v Speaker 1>it wasn't the net. But then, uh, some of it

0:01:22.040 --> 0:01:25.800
<v Speaker 1>represented threats that we actually do have to deal with

0:01:25.880 --> 0:01:30.600
<v Speaker 1>now that we're in this this internet, ubiquitous future. Identity, theft,

0:01:30.720 --> 0:01:34.040
<v Speaker 1>privacy compromises. I mean, these were things people were worried

0:01:34.080 --> 0:01:36.479
<v Speaker 1>about back in the nineties and that they turned out

0:01:36.520 --> 0:01:40.399
<v Speaker 1>to become reality. Sure, yeah, not everything depicted in those

0:01:40.400 --> 0:01:43.160
<v Speaker 1>films was completely off base, although it was almost always

0:01:43.720 --> 0:01:47.039
<v Speaker 1>you know, because it has imagined in a hilarious way,

0:01:47.280 --> 0:01:53.240
<v Speaker 1>overly dramatized. And that certainly that the user operating systems

0:01:53.280 --> 0:01:58.680
<v Speaker 1>were like nothing that we've ever seen. I know this UM,

0:01:58.720 --> 0:02:00.920
<v Speaker 1>and I think we're sort of living in a similar

0:02:01.040 --> 0:02:05.840
<v Speaker 1>era for three D printing. Sure we don't know yet

0:02:05.920 --> 0:02:09.320
<v Speaker 1>what we're worrying about too much and what we're not

0:02:09.400 --> 0:02:13.079
<v Speaker 1>worrying about enough. Sure, well, especially for people who have

0:02:13.160 --> 0:02:16.200
<v Speaker 1>had very limited experience with three D printers. They've heard

0:02:16.200 --> 0:02:19.480
<v Speaker 1>about them but never had direct experience. Joe, as someone

0:02:19.520 --> 0:02:23.079
<v Speaker 1>who has had direct experience with three D printers, would

0:02:23.120 --> 0:02:25.480
<v Speaker 1>you say that the three D printer we have here

0:02:25.480 --> 0:02:28.880
<v Speaker 1>in the office would be capable of printing anything that

0:02:28.960 --> 0:02:32.240
<v Speaker 1>someone should be worried about remotely. Are you worried about

0:02:32.280 --> 0:02:35.359
<v Speaker 1>tangled masses of plastic hair? Yeah? See, here's the thing.

0:02:36.280 --> 0:02:38.120
<v Speaker 1>It sounds like the plot of a Japanese horror movie

0:02:38.160 --> 0:02:43.640
<v Speaker 1>actually if it's in front of the person's face. Uh So,

0:02:44.360 --> 0:02:46.600
<v Speaker 1>we have printed stuff out with a three D printer

0:02:46.760 --> 0:02:49.360
<v Speaker 1>here at the office. It's just it takes a lot

0:02:49.480 --> 0:02:52.400
<v Speaker 1>of of paying attention, Like you can't just hit the

0:02:52.400 --> 0:02:56.079
<v Speaker 1>print and walk away because the materials themselves in our case,

0:02:56.120 --> 0:02:58.440
<v Speaker 1>I think we're using p L A plastic, but the

0:02:58.480 --> 0:03:02.440
<v Speaker 1>materials themselves are uh you know there. They need a

0:03:02.480 --> 0:03:05.480
<v Speaker 1>certain temperature to operate at, and beyond that you're either

0:03:05.560 --> 0:03:09.200
<v Speaker 1>not going to get the meltedness you need for extrusion,

0:03:09.520 --> 0:03:11.320
<v Speaker 1>or it's going to be too warm and then the

0:03:11.800 --> 0:03:15.680
<v Speaker 1>stability of the build will be compromised. Or the build

0:03:15.760 --> 0:03:20.280
<v Speaker 1>plate isn't leveled, or you haven't aligned everything correctly in

0:03:20.320 --> 0:03:23.480
<v Speaker 1>your your pre planning phase, trying to print at a

0:03:23.560 --> 0:03:26.600
<v Speaker 1>level below where the plate is or something, or your

0:03:26.680 --> 0:03:29.840
<v Speaker 1>design has a key element missing some kind of structural

0:03:29.919 --> 0:03:32.079
<v Speaker 1>bit to it that just isn't quite there right. I

0:03:32.360 --> 0:03:36.240
<v Speaker 1>recently had a mask three D printed for a costume

0:03:36.520 --> 0:03:39.680
<v Speaker 1>and in that case, the mask was divided into three pieces,

0:03:39.720 --> 0:03:42.240
<v Speaker 1>because if we had tried to print it as one

0:03:42.320 --> 0:03:45.000
<v Speaker 1>full piece, it would have been very It would have

0:03:45.040 --> 0:03:47.520
<v Speaker 1>been a miracle if it had come through with the

0:03:47.640 --> 0:03:52.000
<v Speaker 1>structural integrity intact and not folded in on itself. The

0:03:52.040 --> 0:03:55.000
<v Speaker 1>point being that three D printing, at least on the

0:03:55.000 --> 0:03:58.080
<v Speaker 1>consumer level, has come a long way, but it's it's

0:03:58.120 --> 0:04:02.120
<v Speaker 1>still fairly primitive, and it's it's not like you can

0:04:02.200 --> 0:04:05.720
<v Speaker 1>hit print and you get a gorgeous coffee mug at

0:04:05.720 --> 0:04:07.640
<v Speaker 1>the end of it. You're gonna get something that's made

0:04:07.640 --> 0:04:10.680
<v Speaker 1>out of plastic. Depending upon the sophistication of your printer,

0:04:10.760 --> 0:04:15.880
<v Speaker 1>it may be fairly there may be some fairly obvious edges,

0:04:16.480 --> 0:04:19.440
<v Speaker 1>especially like just between the layers of the plastic that's

0:04:19.440 --> 0:04:23.520
<v Speaker 1>been like a plastic plastic pixelation. Yeah, yeah, it's it's

0:04:23.520 --> 0:04:26.320
<v Speaker 1>not like a smooth surface like you would get from

0:04:26.360 --> 0:04:30.120
<v Speaker 1>something that was molded plastic. Well, I mean, certainly, to

0:04:30.160 --> 0:04:32.160
<v Speaker 1>a certain degree, you're right, But also I mean, if

0:04:32.160 --> 0:04:33.880
<v Speaker 1>you're willing to shell out a lot of money, there

0:04:33.920 --> 0:04:36.880
<v Speaker 1>are some really good printers out there. These show absolutely

0:04:36.880 --> 0:04:39.960
<v Speaker 1>and in labs and research labs, there are extremely good

0:04:39.960 --> 0:04:44.680
<v Speaker 1>printers that can print with with metals and with glass even. Yeah,

0:04:44.720 --> 0:04:47.080
<v Speaker 1>it's it's a little bit beyond even the pro summer

0:04:47.160 --> 0:04:50.320
<v Speaker 1>level obviously, But the point being that, uh, some of

0:04:50.360 --> 0:04:54.600
<v Speaker 1>the fears around three D printers might be a little premature, right,

0:04:54.960 --> 0:04:57.039
<v Speaker 1>But but there are all kinds of fears people have

0:04:57.240 --> 0:05:00.440
<v Speaker 1>because I mean, obviously it's not exactly analogous the Internet,

0:05:00.480 --> 0:05:03.880
<v Speaker 1>because the Internet was a more ubiquitous kind of information technology.

0:05:03.920 --> 0:05:06.960
<v Speaker 1>You know what, anything that people could do to you

0:05:07.160 --> 0:05:11.120
<v Speaker 1>socially in general life that didn't involve physical contact they

0:05:11.160 --> 0:05:14.840
<v Speaker 1>could do over the Internet. Sure, but there's there's there

0:05:14.880 --> 0:05:17.919
<v Speaker 1>are fears that some of which are are vaguely valid

0:05:18.120 --> 0:05:21.520
<v Speaker 1>in the like like especially for the future about three

0:05:21.600 --> 0:05:24.200
<v Speaker 1>D printers. Uh, you know it's not all the like

0:05:24.240 --> 0:05:27.200
<v Speaker 1>Oh no, cats and dogs three D printing together. Uh,

0:05:27.839 --> 0:05:31.400
<v Speaker 1>copyright infringement. I suppose that the fair fear sort of

0:05:31.400 --> 0:05:34.160
<v Speaker 1>the I mean, it's almost difficult to even call it copyright.

0:05:34.160 --> 0:05:37.920
<v Speaker 1>It is certainly intellectual property. The idea of of let's

0:05:37.920 --> 0:05:40.200
<v Speaker 1>say that you own a furniture store. Someone comes in,

0:05:40.320 --> 0:05:43.839
<v Speaker 1>takes pictures of a table that you have designed, and

0:05:43.880 --> 0:05:47.040
<v Speaker 1>then goes and uses additive manufacturing a three D printing

0:05:47.080 --> 0:05:51.919
<v Speaker 1>process to essentially replicate that table. There's they're stealing your work.

0:05:52.400 --> 0:05:54.640
<v Speaker 1>You could at least you could argue that this is

0:05:54.680 --> 0:05:58.600
<v Speaker 1>my plastic table now. Yeah, or or especially with art

0:05:58.760 --> 0:06:01.160
<v Speaker 1>or something like if you really wanted a sculpture and

0:06:01.200 --> 0:06:04.039
<v Speaker 1>you had an extremely good three D printer, then you

0:06:04.080 --> 0:06:06.760
<v Speaker 1>know that sucks for the artist. Yeah. I thought it

0:06:06.839 --> 0:06:09.920
<v Speaker 1>was funny back when everybody freaked out that somebody three

0:06:10.000 --> 0:06:14.760
<v Speaker 1>D printed a gun, because I was like, you can

0:06:14.800 --> 0:06:18.040
<v Speaker 1>buy guns a lot more easily than you could three

0:06:18.080 --> 0:06:21.320
<v Speaker 1>D print one. Well, let's say you've got a criminal record,

0:06:21.360 --> 0:06:25.000
<v Speaker 1>but you also have a large bank account. You buy

0:06:25.000 --> 0:06:26.719
<v Speaker 1>a three D printer and you can print as many

0:06:26.720 --> 0:06:29.040
<v Speaker 1>guns as you would, But you can go into any

0:06:29.480 --> 0:06:33.840
<v Speaker 1>you know, legitimate establishment and have difficulty buying guns. Not

0:06:33.880 --> 0:06:36.120
<v Speaker 1>great if you have a criminal background. You probably also,

0:06:36.240 --> 0:06:38.479
<v Speaker 1>i mean, assuming it's a large amount of money, you

0:06:38.560 --> 0:06:41.200
<v Speaker 1>probably can illegally obtain a gun with you know, a

0:06:41.240 --> 0:06:44.160
<v Speaker 1>good ten dollars anyway, Right, But it's still one of

0:06:44.200 --> 0:06:46.000
<v Speaker 1>those things that you know, you think, oh, well, this

0:06:46.040 --> 0:06:49.920
<v Speaker 1>could suddenly put a not only could it put guns

0:06:49.920 --> 0:06:52.960
<v Speaker 1>in the hands of people, and that's kind of scary,

0:06:53.040 --> 0:06:56.920
<v Speaker 1>you know, without any sort of regulations right. But also

0:06:57.040 --> 0:07:00.240
<v Speaker 1>on the other side of it, beyond that scary thought

0:07:00.360 --> 0:07:04.520
<v Speaker 1>is if the person is not careful with the materials

0:07:04.560 --> 0:07:06.880
<v Speaker 1>they're using to build their gun, you could end up

0:07:06.880 --> 0:07:09.840
<v Speaker 1>with something that maims the person who built it. Even

0:07:09.880 --> 0:07:11.640
<v Speaker 1>if they are just like, Hey, look at this cool

0:07:11.680 --> 0:07:13.760
<v Speaker 1>thing I built. I'm going to take it out to

0:07:13.840 --> 0:07:15.840
<v Speaker 1>the shooting range and I'm going to shoot it there.

0:07:15.840 --> 0:07:18.360
<v Speaker 1>I'm not playing on shooting anyone else. You're talking about

0:07:18.440 --> 0:07:20.480
<v Speaker 1>using something that's you know, if you're not using the

0:07:20.560 --> 0:07:24.360
<v Speaker 1>right plastic, the forces of a of a bullet being

0:07:24.400 --> 0:07:27.680
<v Speaker 1>fired could be enough to shatter that and severely hurt

0:07:27.720 --> 0:07:30.120
<v Speaker 1>the person who's actually using the gun. Oh. Absolutely, the

0:07:30.160 --> 0:07:33.240
<v Speaker 1>type of plastic that Cody Wilson used in that demonstration,

0:07:33.360 --> 0:07:36.560
<v Speaker 1>we were far beyond the grade of the usual p

0:07:36.720 --> 0:07:40.520
<v Speaker 1>l A that's found in most commercial level three D printers. Yeah,

0:07:40.560 --> 0:07:44.600
<v Speaker 1>his gun was called the Liberator. Jonathan and I did

0:07:44.600 --> 0:07:49.320
<v Speaker 1>an entire episode in which we mostly contained our snark

0:07:49.840 --> 0:07:56.240
<v Speaker 1>about defense distributed Tody Wilson um back in it was

0:07:56.240 --> 0:07:58.520
<v Speaker 1>called printing a gun that was over on tech stuff.

0:07:58.560 --> 0:08:01.520
<v Speaker 1>So if you somehow missed that story, you've been living

0:08:01.560 --> 0:08:03.280
<v Speaker 1>under a rock for a couple of years and or

0:08:03.320 --> 0:08:05.240
<v Speaker 1>you'd like to go back and hear some details about it.

0:08:05.800 --> 0:08:08.320
<v Speaker 1>Go ahead and check that out. It is on the interwebs. Yeah,

0:08:08.360 --> 0:08:13.160
<v Speaker 1>but like all of your security information, speaking of security, okay, Yes,

0:08:13.240 --> 0:08:18.960
<v Speaker 1>that that seguates us into into a story about Yeah,

0:08:19.280 --> 0:08:22.280
<v Speaker 1>it ends up getting us to a story about how

0:08:22.400 --> 0:08:27.040
<v Speaker 1>three D printing could cause a threat to one element

0:08:27.120 --> 0:08:30.240
<v Speaker 1>of security. In fact, has that. It's not could, it's

0:08:30.280 --> 0:08:33.719
<v Speaker 1>it's happened. It's it's out there. It's going on right now.

0:08:33.840 --> 0:08:36.960
<v Speaker 1>We're all do it's your keys, it's your key, specific

0:08:37.040 --> 0:08:43.679
<v Speaker 1>your luggage. It could be any key, but specifically, we're

0:08:43.679 --> 0:08:47.080
<v Speaker 1>gonna start talking about the t s A approved locks

0:08:47.120 --> 0:08:49.520
<v Speaker 1>that you would use on your luggage. Yeah, so I'm

0:08:49.520 --> 0:08:55.640
<v Speaker 1>gonna tell a little story. On November, the Washington Post

0:08:55.800 --> 0:08:59.560
<v Speaker 1>ran a story by Ashley Halsey the third titled the

0:08:59.600 --> 0:09:02.679
<v Speaker 1>Secret Life of Baggage? Where does your luggage go at

0:09:02.679 --> 0:09:06.240
<v Speaker 1>the airport? It sounds like it sounds like one of

0:09:06.240 --> 0:09:09.720
<v Speaker 1>the movies they would watch on Best of the Worst Media.

0:09:09.840 --> 0:09:12.720
<v Speaker 1>It's so magical, like your luggage has a little magic

0:09:12.760 --> 0:09:14.800
<v Speaker 1>gnome kingdom and you know, you know, I would have

0:09:14.840 --> 0:09:17.240
<v Speaker 1>that plinky music that do do do do do do

0:09:17.240 --> 0:09:19.520
<v Speaker 1>do do do do as you watch it go through anyway,

0:09:19.640 --> 0:09:22.320
<v Speaker 1>Sorry you were saying no no. So it was an

0:09:22.400 --> 0:09:27.520
<v Speaker 1>article looking into US Transportation Security Administration. So that's the

0:09:27.520 --> 0:09:31.400
<v Speaker 1>t s A. You're probably familiar with it screening practices

0:09:31.480 --> 0:09:33.960
<v Speaker 1>for checked bags, and it was telling the story of

0:09:33.960 --> 0:09:37.040
<v Speaker 1>what happens to your stuff after you check it, and

0:09:37.080 --> 0:09:39.280
<v Speaker 1>I thought it was a pretty interesting article. Actually, it

0:09:39.280 --> 0:09:42.080
<v Speaker 1>talked about the machinery and the procedures used to screen

0:09:42.200 --> 0:09:46.560
<v Speaker 1>traveling containers. And the key part of the story that's

0:09:46.559 --> 0:09:51.840
<v Speaker 1>relevant to this topic is that the author talks about

0:09:51.920 --> 0:09:54.480
<v Speaker 1>how the t s A has a set of master

0:09:54.640 --> 0:09:58.800
<v Speaker 1>keys that can open all t s A approved locks

0:09:58.800 --> 0:10:03.959
<v Speaker 1>on luggage, which makes sense if your job is to

0:10:03.760 --> 0:10:06.920
<v Speaker 1>to be certain that stuff going through the airport, going

0:10:06.960 --> 0:10:10.599
<v Speaker 1>onto airplanes doesn't contain dangerous materials. Right. The t s

0:10:10.640 --> 0:10:13.320
<v Speaker 1>A started saying, well, we need to screen this luggage

0:10:13.360 --> 0:10:17.280
<v Speaker 1>for important security purposes, but if people are putting locks

0:10:17.280 --> 0:10:19.360
<v Speaker 1>on their luggage, then we might have to cut their

0:10:19.400 --> 0:10:21.680
<v Speaker 1>locks off, which is, you know, a waste of that

0:10:21.720 --> 0:10:25.079
<v Speaker 1>person's resources. So please buy these t s A approved

0:10:25.080 --> 0:10:27.000
<v Speaker 1>locks that the t s A has master keys for,

0:10:27.400 --> 0:10:30.920
<v Speaker 1>and then we can rifle through your personal belongings without

0:10:31.000 --> 0:10:34.480
<v Speaker 1>destroying any of them on purpose, and you'll never know

0:10:34.800 --> 0:10:40.000
<v Speaker 1>because the lock will be back on them again. Yeah,

0:10:40.040 --> 0:10:42.400
<v Speaker 1>But anyway, so people are people. If you want to

0:10:42.440 --> 0:10:45.000
<v Speaker 1>lock your luggage to keep people out of it, but

0:10:45.320 --> 0:10:47.880
<v Speaker 1>you don't use the t s A approved lock, and

0:10:47.920 --> 0:10:50.440
<v Speaker 1>the t s A agent wants to check what's inside

0:10:50.480 --> 0:10:53.640
<v Speaker 1>your bag, they'll just use bolt cutters, which I guess

0:10:53.720 --> 0:10:56.480
<v Speaker 1>is is at least a little better than you know,

0:10:57.160 --> 0:11:00.240
<v Speaker 1>damaging your bag directly to get at what's inside of it, right,

0:11:00.320 --> 0:11:03.600
<v Speaker 1>knife in the side of the bag just barely better

0:11:03.640 --> 0:11:08.560
<v Speaker 1>than that. So the problem is that somebody published a

0:11:08.679 --> 0:11:12.560
<v Speaker 1>version of this story that contained a very problematic picture.

0:11:12.920 --> 0:11:15.320
<v Speaker 1>And I word it that way because I honestly can't

0:11:15.360 --> 0:11:18.400
<v Speaker 1>tell if the image that I'm going to talk about

0:11:18.400 --> 0:11:20.880
<v Speaker 1>originally ran with the story when it was published on

0:11:20.880 --> 0:11:23.840
<v Speaker 1>the Washington Post page, or if it only appeared in

0:11:23.880 --> 0:11:26.800
<v Speaker 1>a reprinting of the story on a site called Harold

0:11:26.840 --> 0:11:30.720
<v Speaker 1>dot net, which some sources refer to. Uh. The Washington

0:11:30.760 --> 0:11:33.240
<v Speaker 1>Post version of the story does not have the offending

0:11:33.280 --> 0:11:36.160
<v Speaker 1>image anymore, if it ever did, got you, but that

0:11:36.240 --> 0:11:40.720
<v Speaker 1>offending image would be a picture of a hand holding

0:11:40.960 --> 0:11:44.600
<v Speaker 1>a series of the master keys for the various types

0:11:44.640 --> 0:11:47.000
<v Speaker 1>of T s A locks. Yeah, it's a close up

0:11:47.080 --> 0:11:49.839
<v Speaker 1>image of all of the master keys that can get

0:11:49.880 --> 0:11:52.880
<v Speaker 1>into all your bags. So in other words, if you

0:11:52.960 --> 0:11:55.200
<v Speaker 1>take a look at this, you can see the shapes

0:11:55.640 --> 0:11:59.840
<v Speaker 1>of each of those keys. Whoops, which you know all right.

0:12:00.080 --> 0:12:03.120
<v Speaker 1>Back in the day, it would have taken quite a

0:12:03.160 --> 0:12:06.760
<v Speaker 1>lot of work to create a key to you know,

0:12:06.960 --> 0:12:09.200
<v Speaker 1>use like a piece of metal and then grind it

0:12:09.240 --> 0:12:13.000
<v Speaker 1>down just right based upon the way it looks in

0:12:13.040 --> 0:12:15.240
<v Speaker 1>a picture. But that could have been done and we'll

0:12:15.240 --> 0:12:19.800
<v Speaker 1>talk about that later. Yeah, well, certainly before computer run

0:12:20.360 --> 0:12:25.000
<v Speaker 1>key creating machines. Words are apparently not in my head

0:12:25.040 --> 0:12:28.960
<v Speaker 1>today it's terrific, and also before algorithms that can end

0:12:29.080 --> 0:12:31.920
<v Speaker 1>up looking at a pattern and making a really close

0:12:32.040 --> 0:12:35.960
<v Speaker 1>estimation of what that pattern represents. Right, Because the resolution

0:12:36.000 --> 0:12:38.679
<v Speaker 1>on these images is not so high that you could

0:12:38.760 --> 0:12:42.199
<v Speaker 1>just zoom. You couldn't zoom and enhance over and over.

0:12:42.280 --> 0:12:43.760
<v Speaker 1>So you've got a good picture, you need you need

0:12:43.800 --> 0:12:46.120
<v Speaker 1>a computer that has some good guesswork with it too.

0:12:46.520 --> 0:12:50.360
<v Speaker 1>But now we're in the era, the combined era of

0:12:50.679 --> 0:12:58.520
<v Speaker 1>sophisticated object recognition image software and additive manufacturing that is

0:12:58.600 --> 0:13:02.839
<v Speaker 1>three D printing. Joe, Please tell me, please tell me

0:13:03.360 --> 0:13:06.000
<v Speaker 1>that is impossible for someone to take the images that

0:13:06.559 --> 0:13:09.120
<v Speaker 1>are here in front of us and turned that into

0:13:09.200 --> 0:13:13.240
<v Speaker 1>an actual physical thing, thus manufacturing their own master keys

0:13:13.360 --> 0:13:15.880
<v Speaker 1>for T. S A. Locks. Well, I don't know about

0:13:15.960 --> 0:13:18.880
<v Speaker 1>this image, but it's definitely possible to do from a photo,

0:13:19.080 --> 0:13:21.760
<v Speaker 1>and it has been done, and people have tried the

0:13:21.800 --> 0:13:23.520
<v Speaker 1>keys and they work. So I'm going to tell the

0:13:23.559 --> 0:13:28.520
<v Speaker 1>story of that now. Apparently somebody tried to delete this

0:13:28.600 --> 0:13:32.280
<v Speaker 1>photo after they had published it, But silly person, Nothing

0:13:32.320 --> 0:13:35.280
<v Speaker 1>gets deleted off the Internet. What's the rule about the Internet?

0:13:35.400 --> 0:13:39.160
<v Speaker 1>The Internet is forever Archive dot org, We salute you,

0:13:39.679 --> 0:13:45.079
<v Speaker 1>and so on. Auguste Remember that original article was last year,

0:13:45.720 --> 0:13:47.760
<v Speaker 1>so it was out for a while. I don't know

0:13:47.840 --> 0:13:51.320
<v Speaker 1>when the image got deleted, So I don't know exactly

0:13:51.360 --> 0:13:54.000
<v Speaker 1>who was the first person to point out this problem,

0:13:54.000 --> 0:13:59.280
<v Speaker 1>but several sources linked to an August one tweet by

0:13:59.440 --> 0:14:03.840
<v Speaker 1>a guy who calls himself an independent journalist named Luke Rudkowski,

0:14:04.600 --> 0:14:06.760
<v Speaker 1>and it shared the image of the master keys and

0:14:06.800 --> 0:14:10.360
<v Speaker 1>said does at Washington Post and brilliant T s A. No,

0:14:10.480 --> 0:14:13.360
<v Speaker 1>they just compromise their locking system by putting this out.

0:14:15.280 --> 0:14:19.600
<v Speaker 1>So ouch, yeah, some hackers got to work. So I'm

0:14:19.640 --> 0:14:21.760
<v Speaker 1>going to try to explain what happened as far as

0:14:22.040 --> 0:14:24.360
<v Speaker 1>as best I can understand it, because there was a

0:14:24.400 --> 0:14:27.840
<v Speaker 1>kind of complicated series of events. But in early September,

0:14:27.960 --> 0:14:31.800
<v Speaker 1>a group of lock pickers and security hobbyists published to

0:14:32.000 --> 0:14:35.760
<v Speaker 1>get hub, a collection of CAD files based on the

0:14:35.800 --> 0:14:37.920
<v Speaker 1>images of the t s A master keys that have

0:14:38.000 --> 0:14:40.520
<v Speaker 1>become available on the internet. And it looks like it

0:14:40.600 --> 0:14:44.440
<v Speaker 1>probably wasn't just the Washington Post image. And I'll say

0:14:44.440 --> 0:14:46.720
<v Speaker 1>more about that in a minute. But yeah, let's break down.

0:14:46.760 --> 0:14:48.880
<v Speaker 1>Let's let's unpack a couple of terms for those of

0:14:48.880 --> 0:14:50.800
<v Speaker 1>you who might not be familiar with get hub and

0:14:50.840 --> 0:14:54.960
<v Speaker 1>cat images. Sure. So, get hub is essentially a repository.

0:14:55.000 --> 0:14:58.640
<v Speaker 1>It's a place where you put open source code. Typically,

0:14:58.880 --> 0:15:01.640
<v Speaker 1>so let's say that you create a program and you

0:15:01.640 --> 0:15:03.920
<v Speaker 1>want to make it open source so other people can

0:15:03.960 --> 0:15:08.160
<v Speaker 1>take your code, tweak it, change it, upload their own versions,

0:15:08.240 --> 0:15:11.160
<v Speaker 1>you know, do transformative work with it. Get hub is

0:15:11.200 --> 0:15:14.320
<v Speaker 1>sort of the centralized place that you would go and

0:15:14.600 --> 0:15:16.920
<v Speaker 1>store that so other people could get at the code

0:15:16.920 --> 0:15:18.600
<v Speaker 1>you had created. Right, So, if you want to make

0:15:18.640 --> 0:15:21.560
<v Speaker 1>something like a Google deep dream available to the public.

0:15:21.640 --> 0:15:23.520
<v Speaker 1>You can put it up on geth hubs, so people

0:15:23.560 --> 0:15:26.040
<v Speaker 1>can make their own apps to do things with it, right, Yeah,

0:15:27.040 --> 0:15:29.760
<v Speaker 1>but then also their CAD files. The CAD just stands

0:15:29.800 --> 0:15:32.880
<v Speaker 1>for computer aided design. So if you want to put

0:15:32.920 --> 0:15:35.720
<v Speaker 1>together a digital shape to make on your three D

0:15:35.800 --> 0:15:38.840
<v Speaker 1>printer in three dimensions, you'll probably make it in a

0:15:38.880 --> 0:15:40.800
<v Speaker 1>CAD program you can. You can think of a CAD

0:15:40.840 --> 0:15:43.720
<v Speaker 1>program as a kind of MS paint for three D objects. Yeah.

0:15:43.760 --> 0:15:46.160
<v Speaker 1>I remember I had a friend who did a lot

0:15:46.160 --> 0:15:50.400
<v Speaker 1>of work with CAD programs back in high school. But

0:15:50.480 --> 0:15:54.000
<v Speaker 1>that was specifically in design classes where you're trying to

0:15:54.080 --> 0:15:58.360
<v Speaker 1>create a a three dimensional object, a plan for a

0:15:58.360 --> 0:16:00.920
<v Speaker 1>three dimensional object. It's also used a lot in architecture

0:16:01.000 --> 0:16:03.080
<v Speaker 1>firms that kind of thing, right. So CAD is bigger

0:16:03.120 --> 0:16:05.280
<v Speaker 1>than just three D print, but it's a way to

0:16:05.320 --> 0:16:07.600
<v Speaker 1>get the file you want to you want to print

0:16:07.640 --> 0:16:12.320
<v Speaker 1>in a three D printer. So apparently after these files

0:16:12.320 --> 0:16:14.920
<v Speaker 1>went up on geth hub, it was literally only a

0:16:14.920 --> 0:16:18.480
<v Speaker 1>few hours before somebody downloaded them and printed one of

0:16:18.520 --> 0:16:22.680
<v Speaker 1>these things and it worked. There are now images online

0:16:22.680 --> 0:16:25.880
<v Speaker 1>of people using these three D printed keys based on

0:16:25.920 --> 0:16:28.960
<v Speaker 1>these images to pop open their t s A approved

0:16:29.200 --> 0:16:32.960
<v Speaker 1>luggage locks. Yeah, and you know, to be fair, some

0:16:33.040 --> 0:16:35.160
<v Speaker 1>of the t s A locks feel like they could

0:16:35.280 --> 0:16:38.080
<v Speaker 1>open if you sneezed on them. But maybe that's just

0:16:38.240 --> 0:16:42.320
<v Speaker 1>my experience with t s A luggage locks. I've never

0:16:42.400 --> 0:16:46.200
<v Speaker 1>used one I travel. I traveled just enough where I've

0:16:46.280 --> 0:16:50.440
<v Speaker 1>used them a few times. Uh And and I often

0:16:50.520 --> 0:16:53.720
<v Speaker 1>question why I go through the trouble, but I still

0:16:53.800 --> 0:16:57.400
<v Speaker 1>do it. Yeah. Well, some users report being able to

0:16:57.400 --> 0:17:01.480
<v Speaker 1>open the locks with unmodified prints of keys using plain

0:17:01.520 --> 0:17:03.560
<v Speaker 1>old p l A. So these are plastic keys. You

0:17:03.560 --> 0:17:05.639
<v Speaker 1>don't need a print him in metal or anything. And

0:17:05.720 --> 0:17:09.680
<v Speaker 1>p l A is not not the sturdiest plastic. I've

0:17:09.680 --> 0:17:12.000
<v Speaker 1>got some little p l A trinkets on my desk

0:17:12.119 --> 0:17:14.399
<v Speaker 1>that I made in our in our printer in the office.

0:17:14.760 --> 0:17:17.679
<v Speaker 1>I read about one user in this Wired article that

0:17:17.760 --> 0:17:20.800
<v Speaker 1>I'm currently referring to who had to modify the scale

0:17:20.840 --> 0:17:23.960
<v Speaker 1>of the key, but otherwise it worked. And this Wired

0:17:24.040 --> 0:17:27.480
<v Speaker 1>article talked to a lockpicker and University of Pennsylvania compside

0:17:27.480 --> 0:17:30.679
<v Speaker 1>professor named Matt Blaze about it, and he made some

0:17:30.760 --> 0:17:34.159
<v Speaker 1>interesting points I thought. First of all, he pointed out that, uh,

0:17:34.280 --> 0:17:36.520
<v Speaker 1>not that it really changes the thrust of the story,

0:17:36.600 --> 0:17:38.800
<v Speaker 1>but just for the record, he thinks the image in

0:17:38.880 --> 0:17:42.479
<v Speaker 1>question leaked somewhere before the Washington Post story, so they

0:17:42.560 --> 0:17:47.880
<v Speaker 1>might not don't line up with your pitchforks only there.

0:17:48.119 --> 0:17:51.560
<v Speaker 1>Yeah uh. He also says that a good lockpicker, you know,

0:17:51.600 --> 0:17:53.720
<v Speaker 1>could probably pick the locks in less time and was

0:17:54.000 --> 0:17:56.440
<v Speaker 1>with less trouble than it would take to print the keys,

0:17:56.480 --> 0:17:59.560
<v Speaker 1>since he says, and I quote, I find it's actually

0:17:59.640 --> 0:18:01.919
<v Speaker 1>quicker to pick the t s A locks than to

0:18:02.040 --> 0:18:05.119
<v Speaker 1>look for my key sometimes. Yeah. Now, these are not

0:18:05.280 --> 0:18:07.919
<v Speaker 1>terribly sophisticated locks. They're not meant to be. They're just

0:18:07.920 --> 0:18:10.359
<v Speaker 1>meant to be a deterrent. And the other point he

0:18:10.440 --> 0:18:12.720
<v Speaker 1>makes is that the parties in questions should have known

0:18:12.800 --> 0:18:15.760
<v Speaker 1>better than allowing people to photograph the keys, because photo

0:18:15.760 --> 0:18:19.200
<v Speaker 1>security and physical keys is a known issue, and we'll

0:18:19.240 --> 0:18:21.640
<v Speaker 1>get to more about that in a minute. But there

0:18:21.680 --> 0:18:24.960
<v Speaker 1>have been more developments since then. According to a timeline

0:18:25.000 --> 0:18:27.800
<v Speaker 1>that I read, which was created by a lockpicker involved

0:18:27.840 --> 0:18:31.199
<v Speaker 1>with the T s A Key story, which I found

0:18:31.280 --> 0:18:36.119
<v Speaker 1>linked in another article for The Intercept by Jenna McLaughlin, boy,

0:18:36.000 --> 0:18:39.600
<v Speaker 1>the trail of of sights here is is impressive. Well,

0:18:39.640 --> 0:18:43.159
<v Speaker 1>I'm just trying to lead you through my thoughts. But anyway,

0:18:43.320 --> 0:18:47.200
<v Speaker 1>the printed keys were actually based on additional imagery dug

0:18:47.280 --> 0:18:50.240
<v Speaker 1>up by the hackers, So it wasn't just the Washington

0:18:50.359 --> 0:18:53.440
<v Speaker 1>Post image that leaked, but it was sort of inspired

0:18:53.480 --> 0:18:56.400
<v Speaker 1>by the Washington Post league that hackers said, I wonder

0:18:56.440 --> 0:18:58.720
<v Speaker 1>if we can find any more images of these keys,

0:18:59.080 --> 0:19:01.320
<v Speaker 1>and they went out and looked for him, and they did.

0:19:01.480 --> 0:19:05.160
<v Speaker 1>They found, whether by legitimate or illegitimate means. I'm not sure,

0:19:05.680 --> 0:19:09.360
<v Speaker 1>photos contained in a document called Guide to Travel Century

0:19:09.400 --> 0:19:13.399
<v Speaker 1>pass Keys, which was created by a group called Travel Century,

0:19:13.480 --> 0:19:16.280
<v Speaker 1>which they have a kind of complicated relationship with the

0:19:16.320 --> 0:19:18.880
<v Speaker 1>t s A and the lockmakers. They are not lock

0:19:19.000 --> 0:19:22.000
<v Speaker 1>manufacturers and they are not the t s A. But

0:19:22.240 --> 0:19:26.480
<v Speaker 1>I understand that there's some sort of liaison organization. I

0:19:26.560 --> 0:19:30.560
<v Speaker 1>got a third party kind of that. Yeah, like they

0:19:31.440 --> 0:19:35.840
<v Speaker 1>according to this article, they generate and enforced security guidelines

0:19:35.880 --> 0:19:41.640
<v Speaker 1>for T s A approved locks, whatever that means. Huh okay.

0:19:41.840 --> 0:19:46.720
<v Speaker 1>So so in the face of this mishap, the t

0:19:46.880 --> 0:19:50.080
<v Speaker 1>s A responded, Yeah, and this is one of the

0:19:50.119 --> 0:19:53.040
<v Speaker 1>most troubling parts that that piece in the intercept I

0:19:53.080 --> 0:19:56.359
<v Speaker 1>talked about got a t s A official to talk

0:19:56.440 --> 0:19:59.080
<v Speaker 1>about the late the leak and the three D printed

0:19:59.119 --> 0:20:02.240
<v Speaker 1>master keys, and I just thought i'd read a select

0:20:02.359 --> 0:20:05.399
<v Speaker 1>quote this was pretty interesting. Okay, sure. The t s

0:20:05.440 --> 0:20:08.399
<v Speaker 1>A spokesperson Mike England sent in an email to the

0:20:08.440 --> 0:20:12.040
<v Speaker 1>Intercept the reported ability to create keys for t s

0:20:12.080 --> 0:20:15.080
<v Speaker 1>A approved suitcase locks from a digital image does not

0:20:15.280 --> 0:20:19.760
<v Speaker 1>create a threat to aviation security. These consumer products are

0:20:19.960 --> 0:20:23.280
<v Speaker 1>peace of mind devices, not part of t s AS

0:20:23.320 --> 0:20:28.720
<v Speaker 1>aviation security regime. And also, and the same guy said,

0:20:29.240 --> 0:20:31.399
<v Speaker 1>carried in check bags are subject to the t s

0:20:31.480 --> 0:20:35.480
<v Speaker 1>AS electronics screening and manual inspection. In addition, the reported

0:20:35.480 --> 0:20:39.240
<v Speaker 1>availability of keys to unauthorized persons causes no loss of

0:20:39.280 --> 0:20:42.320
<v Speaker 1>physical security to bags while they are under t s

0:20:42.400 --> 0:20:45.720
<v Speaker 1>A control. In fact, the vast majority of bags are

0:20:45.760 --> 0:20:50.760
<v Speaker 1>not locked when checked in prior to flight. So what

0:20:50.800 --> 0:20:54.960
<v Speaker 1>they're saying is that, well, we're concerned with national security,

0:20:55.200 --> 0:21:02.280
<v Speaker 1>not your luggage is security. So it's not really our problem. Yeah,

0:21:02.400 --> 0:21:05.719
<v Speaker 1>not our problem. No, it's yeah, essentially don't matter. The

0:21:05.720 --> 0:21:08.080
<v Speaker 1>t s A. The t s AS purpose is not

0:21:08.160 --> 0:21:11.119
<v Speaker 1>to make certain that the bag you packed has the

0:21:11.160 --> 0:21:13.360
<v Speaker 1>same stuff in it when you get to where you're

0:21:13.400 --> 0:21:16.560
<v Speaker 1>going as when you left. It's just to make sure

0:21:16.600 --> 0:21:19.040
<v Speaker 1>that you're not going to hurt the airplane or anybody

0:21:19.080 --> 0:21:22.800
<v Speaker 1>on it, which I should put in is a is

0:21:22.840 --> 0:21:26.960
<v Speaker 1>a valid thing to want. Yeah, this perhaps was maybe

0:21:27.000 --> 0:21:30.280
<v Speaker 1>not the best way to communicate it, since it seems

0:21:30.320 --> 0:21:34.040
<v Speaker 1>like it's by by this way, I mean, this quote

0:21:34.119 --> 0:21:36.920
<v Speaker 1>almost seems like they are flipping me the bird and

0:21:37.080 --> 0:21:40.479
<v Speaker 1>saying saying, don't worry your stuff doesn't matter. They might

0:21:40.520 --> 0:21:43.119
<v Speaker 1>as well say, don't put a lock on it, you know,

0:21:43.240 --> 0:21:46.480
<v Speaker 1>because here they're saying, well, you know, it's it's going

0:21:46.520 --> 0:21:48.600
<v Speaker 1>to be within our care the whole time. I mean,

0:21:48.640 --> 0:21:50.480
<v Speaker 1>no one else is going to have access to it.

0:21:50.520 --> 0:21:55.240
<v Speaker 1>And I'm thinking the people that are handling the luggage

0:21:55.359 --> 0:21:57.960
<v Speaker 1>all along the pathway from the point where I handed

0:21:58.000 --> 0:22:01.520
<v Speaker 1>off to the point where I pick it up aren't

0:22:01.560 --> 0:22:08.400
<v Speaker 1>all necessarily upstanding citizens. I say that because I know

0:22:08.520 --> 0:22:11.920
<v Speaker 1>there have been incidents where people have found stuff missing

0:22:12.880 --> 0:22:15.680
<v Speaker 1>from their I mean, there's there's also just the mere

0:22:15.720 --> 0:22:19.040
<v Speaker 1>fact that if you're if you are distrustful of human people,

0:22:19.200 --> 0:22:22.840
<v Speaker 1>and you perhaps don't make it to the baggage carousel

0:22:23.240 --> 0:22:26.400
<v Speaker 1>exactly at the moment when your suitcase comes out, then

0:22:26.760 --> 0:22:29.840
<v Speaker 1>you know, a dishonest human person could walk up and

0:22:29.880 --> 0:22:31.840
<v Speaker 1>just kind of rummage through your stuff. It takes some

0:22:31.880 --> 0:22:34.080
<v Speaker 1>of it out. Yeah, well, yeah, especially if it's one

0:22:34.080 --> 0:22:36.919
<v Speaker 1>of those things where you ended up getting bumped on

0:22:36.960 --> 0:22:39.480
<v Speaker 1>a flight. You're delayed, but your luggage got on the

0:22:39.520 --> 0:22:41.600
<v Speaker 1>flight that you were supposed to be on, and then

0:22:41.600 --> 0:22:44.159
<v Speaker 1>it's going to be waiting for you for hours at

0:22:44.160 --> 0:22:46.440
<v Speaker 1>an airport. You know, there are a lot of reasons

0:22:46.440 --> 0:22:50.960
<v Speaker 1>why this, to me is not exactly comforting. Yeah. Yeah,

0:22:51.000 --> 0:22:55.680
<v Speaker 1>so perhaps not the most pc response from the t

0:22:55.920 --> 0:22:59.560
<v Speaker 1>s A. However, this does speak to a larger issue

0:22:59.720 --> 0:23:03.560
<v Speaker 1>with with three D printing and security. Yeah, because this

0:23:03.640 --> 0:23:06.280
<v Speaker 1>thing that just happened, this t s A keys event,

0:23:06.480 --> 0:23:09.400
<v Speaker 1>was not not a totally unique situation. I mean there

0:23:09.400 --> 0:23:13.240
<v Speaker 1>are other ways that photo analysis or three D printing

0:23:13.359 --> 0:23:16.760
<v Speaker 1>and things like that can affect physical security. I mean,

0:23:17.200 --> 0:23:20.240
<v Speaker 1>there are these ideas of three D printed bump keys.

0:23:20.359 --> 0:23:23.680
<v Speaker 1>I think you looked into this, Jonathan. Yeah, bump keys are, um,

0:23:24.440 --> 0:23:28.440
<v Speaker 1>they're interesting. So the really weird thing about bump keys

0:23:28.480 --> 0:23:30.639
<v Speaker 1>is you don't need a picture of the key to

0:23:30.880 --> 0:23:32.760
<v Speaker 1>create a bump key. You need a picture of the lock.

0:23:33.040 --> 0:23:35.960
<v Speaker 1>You need to see how the lock is shaped. From there,

0:23:36.840 --> 0:23:39.600
<v Speaker 1>you can create sort of a generic key that has

0:23:39.640 --> 0:23:42.720
<v Speaker 1>sort of generic little peaks and troughs in it, so

0:23:43.320 --> 0:23:45.919
<v Speaker 1>they don't have to match the way the actual key fits.

0:23:46.040 --> 0:23:48.280
<v Speaker 1>It just has to be low enough so it can

0:23:48.320 --> 0:23:51.400
<v Speaker 1>slide into the depth of the lock, all right. They're

0:23:51.400 --> 0:23:55.199
<v Speaker 1>called bump keys because you put the key in the

0:23:55.280 --> 0:23:59.440
<v Speaker 1>lock and you hammer it with a mallet, which jolts

0:23:59.560 --> 0:24:02.800
<v Speaker 1>the key into the lock, pushing the pins. The pins

0:24:02.800 --> 0:24:04.720
<v Speaker 1>are what keep the lock from being able to turn.

0:24:05.119 --> 0:24:07.720
<v Speaker 1>Pushes the pins up. It's like it's it's like you

0:24:07.800 --> 0:24:10.560
<v Speaker 1>just gave it a quick shove, so the pins bounce up,

0:24:10.600 --> 0:24:12.840
<v Speaker 1>and at that moment you have to turn the key.

0:24:13.000 --> 0:24:14.879
<v Speaker 1>And as you start turning the key, it's as if

0:24:14.920 --> 0:24:18.080
<v Speaker 1>you're using the actual key built for that lock, and

0:24:18.119 --> 0:24:22.280
<v Speaker 1>it will unlock the lock in question. So you would

0:24:22.440 --> 0:24:25.920
<v Speaker 1>three D print this kind of generic key and then

0:24:25.960 --> 0:24:29.159
<v Speaker 1>just use that hammer to go quick a quick uh

0:24:29.520 --> 0:24:32.480
<v Speaker 1>bump and then a turn. And apparently it takes a

0:24:32.480 --> 0:24:37.400
<v Speaker 1>little practice, takes some some finesse to get the timing

0:24:37.520 --> 0:24:41.400
<v Speaker 1>just right. Um, but it works. You can totally make

0:24:41.600 --> 0:24:44.679
<v Speaker 1>keys that will unlock locks this way. Yeah. And of

0:24:44.720 --> 0:24:48.359
<v Speaker 1>course there's just plain old lock picking, sure, yeah, which

0:24:48.680 --> 0:24:52.879
<v Speaker 1>requires a little bit more. Uh, practice and access to

0:24:53.040 --> 0:24:55.760
<v Speaker 1>lock picking tools, which are not hard to get, but

0:24:56.160 --> 0:24:59.720
<v Speaker 1>the practice takes time. Like it's it's a learned skill. Yeah,

0:24:59.760 --> 0:25:02.800
<v Speaker 1>it's not. As it's not as simple as as you

0:25:02.880 --> 0:25:05.880
<v Speaker 1>might think, but it's not, you know, impossible to learn.

0:25:05.920 --> 0:25:09.119
<v Speaker 1>There are plenty of lock picking groups out there, copy

0:25:09.200 --> 0:25:12.280
<v Speaker 1>groups that U do this stuff all the time. Hopefully

0:25:12.320 --> 0:25:15.840
<v Speaker 1>airport security people should be able to look at someone

0:25:15.920 --> 0:25:19.080
<v Speaker 1>and determine that they're sitting there trying to pick a lock,

0:25:19.680 --> 0:25:22.119
<v Speaker 1>sticking a lock pick gun into a lock, or or

0:25:22.160 --> 0:25:24.439
<v Speaker 1>they they see a person just like I would like

0:25:24.560 --> 0:25:28.320
<v Speaker 1>kneel down in front of a piece of luggage and

0:25:28.359 --> 0:25:32.480
<v Speaker 1>then unfold my lock picks in front of me and

0:25:33.040 --> 0:25:35.320
<v Speaker 1>picturing you like sitting on a skateboard and like and

0:25:35.359 --> 0:25:39.560
<v Speaker 1>like rolling along next to baggage carousel, like with your

0:25:39.600 --> 0:25:42.400
<v Speaker 1>with your little kit laid out on your knees. Yes,

0:25:42.480 --> 0:25:45.280
<v Speaker 1>that would be a little bit obvious. But also way

0:25:45.280 --> 0:25:48.080
<v Speaker 1>before three D printing, this was an issue too. Yeah.

0:25:48.119 --> 0:25:50.040
<v Speaker 1>I mean, well, I mean people have been talking about

0:25:50.080 --> 0:25:54.560
<v Speaker 1>various ways to reproduce keys from photos for years, right yeah, yeah,

0:25:54.600 --> 0:25:57.560
<v Speaker 1>So for example, at the a c M Conference on

0:25:57.600 --> 0:26:00.560
<v Speaker 1>Computer and Communication Security, a way back into the eight

0:26:01.000 --> 0:26:04.159
<v Speaker 1>there were a trio of security experts who presented a

0:26:04.280 --> 0:26:10.680
<v Speaker 1>product they called Sneaky as an E A K E

0:26:11.000 --> 0:26:14.800
<v Speaker 1>Y why because we love you A system for duplicating

0:26:14.800 --> 0:26:18.640
<v Speaker 1>a key that's not in your possession, so specifically by

0:26:18.640 --> 0:26:20.760
<v Speaker 1>taking a picture of a key being able to create

0:26:20.840 --> 0:26:25.120
<v Speaker 1>a copy of it. Uh. Here's here's a quote from there.

0:26:25.240 --> 0:26:30.320
<v Speaker 1>The abstract of their presentation, the access control provided by

0:26:30.320 --> 0:26:33.840
<v Speaker 1>a physical lock is based on the assumption that the

0:26:33.880 --> 0:26:39.359
<v Speaker 1>information content of the corresponding key is private, that duplication

0:26:39.600 --> 0:26:43.120
<v Speaker 1>should require either possession of the key or a priori

0:26:43.240 --> 0:26:47.440
<v Speaker 1>knowledge of how it was cut. However, the ever increasing

0:26:47.480 --> 0:26:51.840
<v Speaker 1>capabilities and prevalence of digital imaging technologies present a fundamental

0:26:52.000 --> 0:26:57.280
<v Speaker 1>challenge to this privacy assumption. Using modest imaging equipment and

0:26:57.400 --> 0:27:02.440
<v Speaker 1>standard computer vision algorithms, we demonstrate the effectiveness of physical

0:27:02.600 --> 0:27:08.120
<v Speaker 1>key tele duplication extracting the key's complete and precise bidding

0:27:08.200 --> 0:27:12.280
<v Speaker 1>code at a distance via optical decoding, and then cutting

0:27:12.320 --> 0:27:17.800
<v Speaker 1>precise duplicates. We describe our prototype system Sneaky and evaluate

0:27:17.880 --> 0:27:21.720
<v Speaker 1>its effectiveness in both laboratory and real world settings. Using

0:27:21.760 --> 0:27:24.960
<v Speaker 1>the most popular residential key types in the United States,

0:27:25.119 --> 0:27:28.440
<v Speaker 1>which is basically saying that if anyone has ever taken

0:27:28.480 --> 0:27:32.600
<v Speaker 1>a photograph of a key that you have, there's the

0:27:32.640 --> 0:27:35.399
<v Speaker 1>potential out there, even without three D printers, to produce

0:27:35.400 --> 0:27:38.200
<v Speaker 1>a copy of it. That's right. So all you kids

0:27:38.200 --> 0:27:41.680
<v Speaker 1>who wear your keys on your hips, yeah, start putting

0:27:41.680 --> 0:27:44.119
<v Speaker 1>those in pockets. They can keep the chain on them,

0:27:44.160 --> 0:27:48.280
<v Speaker 1>but put them in a pocket deep in those Jinko pockets. Yeah.

0:27:48.480 --> 0:27:52.359
<v Speaker 1>So hey, I like my chinkoes. So one of the

0:27:52.400 --> 0:27:54.480
<v Speaker 1>other things that that you want to talk about, Joe,

0:27:54.600 --> 0:27:58.120
<v Speaker 1>was how this goes beyond the t s A goes

0:27:58.160 --> 0:28:01.320
<v Speaker 1>beyond even physical locks and keys. Actually, oh sure, I mean,

0:28:01.359 --> 0:28:03.480
<v Speaker 1>and of course it applies to physical locks and keys,

0:28:03.520 --> 0:28:06.919
<v Speaker 1>but it's a broader security question because in in response

0:28:07.000 --> 0:28:10.400
<v Speaker 1>to this incident, I've seen many writers and security analysts

0:28:10.440 --> 0:28:14.480
<v Speaker 1>pointing out how that this is essentially a problem that's

0:28:14.560 --> 0:28:18.760
<v Speaker 1>inherent with backdoor systems. We often think of backdoors in

0:28:18.880 --> 0:28:22.760
<v Speaker 1>terms of software exploits, but the master key is a

0:28:22.800 --> 0:28:26.440
<v Speaker 1>physical form of a security back door, right, So what's

0:28:26.480 --> 0:28:29.080
<v Speaker 1>the idea of a backdoor. It's essentially that there is

0:28:29.119 --> 0:28:33.000
<v Speaker 1>a there is a secret way around known only to

0:28:33.280 --> 0:28:37.520
<v Speaker 1>supposedly legitimate authorities that can always get in through your

0:28:37.560 --> 0:28:41.240
<v Speaker 1>security measures. Yeah, I um. I was on an episode

0:28:41.400 --> 0:28:44.400
<v Speaker 1>of Daily Tech News show where we were talking about backdoors,

0:28:44.440 --> 0:28:47.920
<v Speaker 1>were specifically talking about the n S A and and backdoors.

0:28:48.960 --> 0:28:55.120
<v Speaker 1>Various law and law enforcement agencies often lobby to have

0:28:55.200 --> 0:29:01.320
<v Speaker 1>backdoors inserted into popular types of software. Uh, the argument

0:29:01.360 --> 0:29:04.960
<v Speaker 1>being that this would increase safety if they were able

0:29:05.000 --> 0:29:08.800
<v Speaker 1>to get access to these things quickly and stop actors

0:29:08.840 --> 0:29:11.520
<v Speaker 1>who would be who are who are trying to plan

0:29:11.560 --> 0:29:14.480
<v Speaker 1>out something that's going to be harmful to others, often

0:29:14.560 --> 0:29:18.360
<v Speaker 1>in the form of terrorist plans like sure so so

0:29:18.440 --> 0:29:21.560
<v Speaker 1>the ability to kind of peek in on telephone communications

0:29:21.960 --> 0:29:25.160
<v Speaker 1>along those lines exactly. And the point I made, and

0:29:25.200 --> 0:29:28.080
<v Speaker 1>it's something I still believe in today, is that you

0:29:28.240 --> 0:29:32.920
<v Speaker 1>do not increase security by introducing vulnerabilities into your system.

0:29:33.200 --> 0:29:36.720
<v Speaker 1>And a backdoor is by its nature of vulnerability. Yeah.

0:29:36.760 --> 0:29:40.520
<v Speaker 1>And frankly, they don't care about increasing security. I mean

0:29:40.600 --> 0:29:43.360
<v Speaker 1>that's not the goal is to increase your privacy or

0:29:43.400 --> 0:29:46.880
<v Speaker 1>your personal security. It's it's about another goal, which is

0:29:47.600 --> 0:29:50.840
<v Speaker 1>even if you take the authorities who want backdoors and

0:29:50.880 --> 0:29:53.480
<v Speaker 1>everything at their word and say they're not going to

0:29:53.560 --> 0:29:56.760
<v Speaker 1>abuse their power no matter what kind of system we're

0:29:56.760 --> 0:29:59.480
<v Speaker 1>talking about if there's a third party with a key

0:29:59.600 --> 0:30:02.440
<v Speaker 1>that all always works, there are ways that third party's

0:30:02.520 --> 0:30:05.040
<v Speaker 1>key can slip into the hands of the bad actors.

0:30:05.480 --> 0:30:09.120
<v Speaker 1>So even if you totally trust the government, which you know,

0:30:09.160 --> 0:30:11.480
<v Speaker 1>we're not saying it's not the point of the show

0:30:11.600 --> 0:30:14.040
<v Speaker 1>right now, one way or another. But let's let's pretend

0:30:14.080 --> 0:30:17.120
<v Speaker 1>you do totally trust the government and the authorities, it's

0:30:17.160 --> 0:30:20.320
<v Speaker 1>still a bad idea to have these back doors because

0:30:20.360 --> 0:30:23.520
<v Speaker 1>they always get out, and that that's exactly what what

0:30:23.680 --> 0:30:26.320
<v Speaker 1>my point was was. The idea that a back door

0:30:26.600 --> 0:30:30.600
<v Speaker 1>is is by its nature of vulnerability, it's it's a

0:30:30.600 --> 0:30:35.840
<v Speaker 1>away other than the preferred way to access a system.

0:30:36.120 --> 0:30:38.560
<v Speaker 1>Doesn't matter if it's a door, or if it's an

0:30:38.600 --> 0:30:41.240
<v Speaker 1>operating system, or if it's a piece of software, or

0:30:41.240 --> 0:30:43.719
<v Speaker 1>if it's a telephone, does not matter what it is.

0:30:44.240 --> 0:30:47.720
<v Speaker 1>It is another way that an actor can gain access

0:30:47.760 --> 0:30:51.960
<v Speaker 1>to a system, uh and and potentially cause quite a

0:30:51.960 --> 0:30:54.360
<v Speaker 1>bit of damage in the process. So I it is

0:30:54.440 --> 0:31:00.240
<v Speaker 1>my belief that back doors are nearly always a bad idea.

0:31:00.400 --> 0:31:03.160
<v Speaker 1>We all saw what kind of havoc they wreaked in

0:31:03.280 --> 0:31:08.880
<v Speaker 1>Jurassic Park. Yes, yes, oh, you're talking about Nedriya Nedri

0:31:09.040 --> 0:31:11.080
<v Speaker 1>had a backdoor. Yeah, I don't know if that was

0:31:11.120 --> 0:31:14.440
<v Speaker 1>for legitimate authorities, but that was for no. No, you

0:31:14.480 --> 0:31:18.480
<v Speaker 1>didn't say the magic word related purposes. I'm extrapolating on

0:31:18.520 --> 0:31:20.600
<v Speaker 1>the part. I mean, you know, did you create backdoors

0:31:20.640 --> 0:31:23.680
<v Speaker 1>and suddenly dinosaurs can run them up? Well, that is

0:31:23.720 --> 0:31:26.600
<v Speaker 1>a good part because it wasn't necessarily part of Nedri's

0:31:26.600 --> 0:31:29.120
<v Speaker 1>plan to have a losci raptors eat everybody. It's just

0:31:29.160 --> 0:31:32.320
<v Speaker 1>an unfortunate consequence. Yea, this this brings us back to

0:31:32.440 --> 0:31:36.920
<v Speaker 1>this is unix I know this, but anyway, I think

0:31:36.920 --> 0:31:38.560
<v Speaker 1>it would be interesting to talk about some of the

0:31:38.600 --> 0:31:44.200
<v Speaker 1>implications of this kind of event. Yeah, so, obviously we

0:31:44.280 --> 0:31:48.760
<v Speaker 1>could reach the conclusion that physical locks and keys have

0:31:48.960 --> 0:31:52.240
<v Speaker 1>had their day. We've already known that there were these

0:31:52.280 --> 0:31:55.600
<v Speaker 1>potential vulnerabilities. We've talked about those, We've talked about lock picking,

0:31:55.600 --> 0:31:58.680
<v Speaker 1>and we talked about the ability to replicate a key

0:31:58.720 --> 0:32:02.040
<v Speaker 1>simply from a picture. But this new story about three

0:32:02.120 --> 0:32:05.400
<v Speaker 1>D printing, coupled with the rise of three D printing

0:32:05.400 --> 0:32:08.800
<v Speaker 1>and popular culture, kind of drives at home yet again

0:32:08.840 --> 0:32:13.000
<v Speaker 1>that the physical lock and key is not a beat

0:32:13.040 --> 0:32:16.040
<v Speaker 1>all security measure, and that perhaps it's time to start

0:32:16.080 --> 0:32:19.240
<v Speaker 1>looking at alternatives. We need retin a scanners on everything.

0:32:20.120 --> 0:32:22.720
<v Speaker 1>Biometrics are part of it. But also this is not

0:32:22.800 --> 0:32:26.080
<v Speaker 1>the only type of story, embarrassing story about a lock

0:32:26.640 --> 0:32:29.680
<v Speaker 1>and a a way of getting access to that lock.

0:32:29.760 --> 0:32:32.000
<v Speaker 1>Did you guys ever hear about There was a story

0:32:32.040 --> 0:32:35.040
<v Speaker 1>that broke around two thousand five about the Kryptonite bike locks.

0:32:36.280 --> 0:32:38.840
<v Speaker 1>So I got a buddy. His name is Brian Brushwood,

0:32:39.000 --> 0:32:42.080
<v Speaker 1>and he's a magician and a scam artist, that's what

0:32:42.160 --> 0:32:44.880
<v Speaker 1>he calls himself. And so he did an episode of

0:32:44.920 --> 0:32:50.440
<v Speaker 1>Scam School recently where he actually showed this particular vulnerability

0:32:50.520 --> 0:32:54.240
<v Speaker 1>in action. So back in two thousand five, Kryptonite released

0:32:54.280 --> 0:32:57.920
<v Speaker 1>a bike lock that had a tubular lock to it.

0:32:58.040 --> 0:33:01.400
<v Speaker 1>So it uses a cylindrical key to activate the pens

0:33:01.400 --> 0:33:04.120
<v Speaker 1>and then you turn that it releases the lock. It's

0:33:04.120 --> 0:33:06.480
<v Speaker 1>sort of like a like like whistle shaped almost, yeah,

0:33:06.720 --> 0:33:10.000
<v Speaker 1>And so he showed that something that people had known

0:33:10.280 --> 0:33:13.080
<v Speaker 1>for quite some time, that that particular style of luck

0:33:13.480 --> 0:33:18.520
<v Speaker 1>could be defeated with a big pen casing. You take

0:33:18.560 --> 0:33:24.000
<v Speaker 1>the pen out of the pen and then plastic. Yeah,

0:33:24.040 --> 0:33:26.200
<v Speaker 1>you just wiggle that onto the lock and if you

0:33:26.200 --> 0:33:28.760
<v Speaker 1>wiggle it the right way, you can activate the lock,

0:33:28.840 --> 0:33:32.280
<v Speaker 1>and you've you've opened up a Kryptonite These are expensive locks,

0:33:32.320 --> 0:33:35.480
<v Speaker 1>by the way, Kryptonite bike lock, thus getting access to

0:33:35.720 --> 0:33:38.200
<v Speaker 1>not just the bike lock, but also the bike that

0:33:38.320 --> 0:33:41.560
<v Speaker 1>was locked to it. And uh. And so there were

0:33:41.600 --> 0:33:46.280
<v Speaker 1>some people who were criticizing Brian because they were saying, hey,

0:33:46.560 --> 0:33:50.200
<v Speaker 1>why don't show people how to steal bikes? And I

0:33:50.280 --> 0:33:54.720
<v Speaker 1>actually commented on his YouTube video and said, guys, he's

0:33:54.760 --> 0:33:59.040
<v Speaker 1>not showing you how to pick locks. This is information

0:33:59.080 --> 0:34:01.040
<v Speaker 1>that's been out there since two thousand five. What he's

0:34:01.040 --> 0:34:04.280
<v Speaker 1>showing you is which lock you absolutely should not be

0:34:04.400 --> 0:34:06.680
<v Speaker 1>using for your bicycle. All right, this is this is

0:34:06.680 --> 0:34:10.000
<v Speaker 1>important consumer information, right. This is the it's the white

0:34:10.000 --> 0:34:14.360
<v Speaker 1>hat hacker principle. Somebody shows you the vulnerabilities and your security.

0:34:14.400 --> 0:34:17.799
<v Speaker 1>Hopefully that should spur you to create better security. And

0:34:17.840 --> 0:34:21.640
<v Speaker 1>Kryptonite did do that. In in full disclosure, Kryptonite went back,

0:34:21.760 --> 0:34:24.840
<v Speaker 1>they redesigned their lock, they went with a disc shape

0:34:24.920 --> 0:34:28.640
<v Speaker 1>rather than a tube shape, and they offered an exchange program.

0:34:28.920 --> 0:34:31.759
<v Speaker 1>So they did their due diligence once once the vulnerability

0:34:31.880 --> 0:34:34.080
<v Speaker 1>was known, they you know, it wasn't like they washed

0:34:34.080 --> 0:34:37.759
<v Speaker 1>their hands and backed away. This is their business. Yeah,

0:34:37.840 --> 0:34:41.440
<v Speaker 1>so they went they did well, uh and uh and

0:34:41.440 --> 0:34:44.359
<v Speaker 1>and held up their end of the bargain uh and and.

0:34:44.400 --> 0:34:47.800
<v Speaker 1>Some other systems have certainly been created that are trying

0:34:47.880 --> 0:34:50.719
<v Speaker 1>to move away from physical keys. You know, the little

0:34:50.840 --> 0:34:53.960
<v Speaker 1>UH beepers on cars that will open your car door,

0:34:53.960 --> 0:34:57.440
<v Speaker 1>having a numerical keypad on your on your house right right.

0:34:57.520 --> 0:34:59.720
<v Speaker 1>A lot of them are things that are proximity based.

0:34:59.760 --> 0:35:01.959
<v Speaker 1>Like you have a smartphone that has a particular app

0:35:02.000 --> 0:35:05.120
<v Speaker 1>on it, you may be uh, you may have to

0:35:05.120 --> 0:35:07.680
<v Speaker 1>put in a pen in order to activate a lock

0:35:07.760 --> 0:35:09.960
<v Speaker 1>and unlock something as you're walking up to your front door.

0:35:10.200 --> 0:35:12.480
<v Speaker 1>I've seen some systems that are so proximity base that

0:35:12.520 --> 0:35:14.360
<v Speaker 1>you don't even have to do that. If you have

0:35:14.440 --> 0:35:17.720
<v Speaker 1>your phone on, you've paired it with the lock system,

0:35:17.800 --> 0:35:21.000
<v Speaker 1>and you get within range, it will automatically unlock. I

0:35:21.080 --> 0:35:24.680
<v Speaker 1>don't know that I'm particularly in favor of that approach,

0:35:24.800 --> 0:35:27.720
<v Speaker 1>but I do like the idea of using the pen system.

0:35:27.760 --> 0:35:32.120
<v Speaker 1>It's not full proof. No security system is ever full proof,

0:35:32.480 --> 0:35:36.920
<v Speaker 1>but it's an alternative to the physical key and lock. Now,

0:35:36.960 --> 0:35:39.919
<v Speaker 1>a lot of these systems also have a physical key

0:35:39.960 --> 0:35:43.520
<v Speaker 1>that you can use UM. So if that's if it's

0:35:43.520 --> 0:35:46.080
<v Speaker 1>not a double lock system. In other words, if the

0:35:46.160 --> 0:35:49.680
<v Speaker 1>same like physical lock and the digital lock are the same,

0:35:50.520 --> 0:35:53.520
<v Speaker 1>you might not be in any better shape, considering that

0:35:53.520 --> 0:35:56.640
<v Speaker 1>we've already talked about the vulnerabilities of physical locks. Yeah,

0:35:56.719 --> 0:36:01.560
<v Speaker 1>and there's also vulnerabilities involved in inometric systems too. We've

0:36:01.560 --> 0:36:04.120
<v Speaker 1>we've talked about that either here on tech stuff before

0:36:04.120 --> 0:36:08.880
<v Speaker 1>and thinking Okay, but because it's it's at this current

0:36:08.920 --> 0:36:13.080
<v Speaker 1>moment not all that difficult to fool a retina scanner

0:36:13.200 --> 0:36:15.960
<v Speaker 1>or a thumb print scanner, right, Yeah, there there are

0:36:15.960 --> 0:36:18.680
<v Speaker 1>certain ones that are are looking more promising, like the

0:36:18.719 --> 0:36:21.759
<v Speaker 1>ones that trace the veins underneath the skin and check

0:36:21.800 --> 0:36:24.560
<v Speaker 1>for blood flowing. Yeah, making sure that someone hasn't just

0:36:24.600 --> 0:36:27.319
<v Speaker 1>cut off your hand and used it to slap on

0:36:27.360 --> 0:36:29.920
<v Speaker 1>your front door. Um, in which case you may not

0:36:29.960 --> 0:36:32.319
<v Speaker 1>be worried so much about the burglary. There might be

0:36:32.360 --> 0:36:35.359
<v Speaker 1>other things that are pressing issues on your mind, like bleeding. Yeah,

0:36:35.400 --> 0:36:38.200
<v Speaker 1>that could be way up there. But yeah, this is

0:36:38.280 --> 0:36:40.200
<v Speaker 1>this is one of the things. We don't meant say

0:36:40.200 --> 0:36:43.239
<v Speaker 1>this nor to to cause fear, uncertainty and doubt, but

0:36:43.520 --> 0:36:48.759
<v Speaker 1>rather to raise awareness of security vulnerabilities. Maybe it's one

0:36:48.800 --> 0:36:50.759
<v Speaker 1>of those things that just makes you think before you

0:36:50.800 --> 0:36:52.480
<v Speaker 1>get a picture taken, like, oh, you know, I pres

0:36:52.480 --> 0:36:55.640
<v Speaker 1>shouldn't have my keys out, or you know, anything along

0:36:55.680 --> 0:37:00.440
<v Speaker 1>those lines where you want to practice good security measures. No,

0:37:00.400 --> 0:37:04.200
<v Speaker 1>not necessarily to go out and like by the latest

0:37:04.200 --> 0:37:07.160
<v Speaker 1>security system to outfit your your house. I mean, I

0:37:07.200 --> 0:37:10.000
<v Speaker 1>just use a cave troll is what I've got right

0:37:10.000 --> 0:37:14.680
<v Speaker 1>behind the front door. Very effective. But let's talk about

0:37:14.680 --> 0:37:18.720
<v Speaker 1>your puppy like that. He's a monster. Now, what if somebody,

0:37:18.760 --> 0:37:22.959
<v Speaker 1>the person who bred those cave trolls actually all taught them,

0:37:23.160 --> 0:37:26.120
<v Speaker 1>taught them all a secret password that only the company

0:37:26.200 --> 0:37:30.000
<v Speaker 1>has until they leak internal documents, and now people know

0:37:30.040 --> 0:37:32.880
<v Speaker 1>they can get past your troll by saying the magic word,

0:37:33.200 --> 0:37:36.480
<v Speaker 1>which is yar olsburg. I was concerned with that, but

0:37:36.520 --> 0:37:39.200
<v Speaker 1>it turns out that this particular cave troll only goes

0:37:39.239 --> 0:37:42.200
<v Speaker 1>into a grape vine if you say that. So apparently

0:37:42.239 --> 0:37:47.000
<v Speaker 1>there was musical theater at that particular cave troll UH university.

0:37:47.120 --> 0:37:50.800
<v Speaker 1>So I'm thankful for that. Uh. To be more serious, however,

0:37:51.320 --> 0:37:55.720
<v Speaker 1>obviously it's it's good to think about these things whenever

0:37:55.800 --> 0:37:58.440
<v Speaker 1>you're trying concerned about your security. When it comes to

0:37:58.480 --> 0:38:01.399
<v Speaker 1>t s a locks, I mean I don't have any

0:38:01.400 --> 0:38:03.640
<v Speaker 1>good advice for that at all right now. I don't

0:38:03.680 --> 0:38:05.560
<v Speaker 1>even know if I'll be using them at this point.

0:38:05.600 --> 0:38:07.960
<v Speaker 1>Oh yeah, well, I mean, you know, it's don't take

0:38:08.000 --> 0:38:11.879
<v Speaker 1>anything valuable on a plane. Yeah, that's that's that's pretty good.

0:38:11.960 --> 0:38:15.200
<v Speaker 1>The part part is when you go someplace and you

0:38:15.320 --> 0:38:19.200
<v Speaker 1>pick up stuff for people you love to bring back

0:38:19.560 --> 0:38:21.319
<v Speaker 1>to give to them. Like if I go on a

0:38:21.360 --> 0:38:24.560
<v Speaker 1>trip and I start buying souvenirs for people, then I

0:38:24.600 --> 0:38:26.560
<v Speaker 1>have a concern about that, although I could always ship it.

0:38:26.600 --> 0:38:30.719
<v Speaker 1>I guess stop having people that you love. It's slowly

0:38:30.760 --> 0:38:33.319
<v Speaker 1>turning out that way. I'm just getting grouchier as they

0:38:33.360 --> 0:38:35.759
<v Speaker 1>get older. No, I don't know. I mean, you know,

0:38:36.400 --> 0:38:40.040
<v Speaker 1>perhaps perhaps good advice if you have a few extra

0:38:40.080 --> 0:38:42.680
<v Speaker 1>bucks on you is to buy a regular lock. But

0:38:42.880 --> 0:38:46.560
<v Speaker 1>since even those aren't full proof. Yeah. I saw one

0:38:46.640 --> 0:38:48.920
<v Speaker 1>comment or on one of the articles I read saying

0:38:49.000 --> 0:38:53.960
<v Speaker 1>I always use zip ties. Interesting, is there cheap and

0:38:54.040 --> 0:38:56.040
<v Speaker 1>if the t s A Needs to get in there,

0:38:56.120 --> 0:38:58.799
<v Speaker 1>they'll just cut it off, Yeah, and then won't cause

0:38:58.880 --> 0:39:03.440
<v Speaker 1>damage to the luggage. That's probably that's probably the best approach.

0:39:03.480 --> 0:39:05.640
<v Speaker 1>And thinking that well, if they don't need to see it,

0:39:05.680 --> 0:39:07.920
<v Speaker 1>everything safe and if they do need to see it, well,

0:39:08.000 --> 0:39:10.239
<v Speaker 1>there's nothing I can do to stop them anyway, because

0:39:10.280 --> 0:39:13.560
<v Speaker 1>that's their job. They're they're trying to practice security for

0:39:13.800 --> 0:39:17.920
<v Speaker 1>a much larger group than just my stuff. They verify

0:39:18.040 --> 0:39:24.120
<v Speaker 1>that my cans of dog food are not actually something else. Yeah. Yeah, well,

0:39:24.160 --> 0:39:26.480
<v Speaker 1>at any rate, this was this was an interesting topic

0:39:26.560 --> 0:39:29.920
<v Speaker 1>to cover. Uh, we didn't get quite as angry as

0:39:29.960 --> 0:39:32.440
<v Speaker 1>we all thought we would, which I guess is good.

0:39:33.400 --> 0:39:35.719
<v Speaker 1>I think I got about as angry as I was anticipating.

0:39:35.800 --> 0:39:37.640
<v Speaker 1>I got about I think I got about three quarters

0:39:37.640 --> 0:39:41.839
<v Speaker 1>as angry as I was anticipating. Yeah, yeah, I had.

0:39:41.880 --> 0:39:47.799
<v Speaker 1>I had calm, dude, I'm calm. Alright, Well, I'm gonna

0:39:47.840 --> 0:39:50.560
<v Speaker 1>abide by that. Guys, if you have any suggestions for

0:39:50.640 --> 0:39:54.000
<v Speaker 1>future episodes of forward Thinking, I recommend you write to

0:39:54.120 --> 0:39:57.200
<v Speaker 1>us and tell us what those are. The email addresses

0:39:57.320 --> 0:40:00.400
<v Speaker 1>f W Thinking at how Stuffworks dot com. You can

0:40:00.480 --> 0:40:03.640
<v Speaker 1>drop us a line on Facebook, Twitter, or Google Plus.

0:40:03.680 --> 0:40:06.560
<v Speaker 1>At Twitter and Google Plus, we are FW thinking. Just

0:40:06.680 --> 0:40:09.239
<v Speaker 1>search FW thinking on Facebook. We'll pop right up. You

0:40:09.280 --> 0:40:11.520
<v Speaker 1>can leave us a message on there, and we will

0:40:11.560 --> 0:40:20.160
<v Speaker 1>talk to you again really soon. We're more on this

0:40:20.239 --> 0:40:23.200
<v Speaker 1>topic and the future of technology. This is forward sinking

0:40:23.320 --> 0:40:37.560
<v Speaker 1>dot com, brought to you by Toyota. Let's Go Places,