WEBVTT - How Encryption Works

0:00:00.320 --> 0:00:02.880
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.240 --> 0:00:08.800
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:08.920 --> 0:00:12.080
<v Speaker 1>tech stuff from how stuff Works dot Com, brought to

0:00:12.080 --> 0:00:15.160
<v Speaker 1>you by Visas. Y'all have things we like to think about.

0:00:15.400 --> 0:00:18.840
<v Speaker 1>Online fraud shouldn't be one of them, because with every purchase,

0:00:19.239 --> 0:00:24.800
<v Speaker 1>Visa prevents to texts and resolves online fraud safe secure pieces.

0:00:26.000 --> 0:00:28.760
<v Speaker 1>Other ladies and gentlemen, welcome to the podcast. My name

0:00:28.800 --> 0:00:31.400
<v Speaker 1>is Chris Colette. I'm an editor here at How Stuff Works,

0:00:31.720 --> 0:00:34.360
<v Speaker 1>and today I have with me in the studio right here,

0:00:34.440 --> 0:00:38.040
<v Speaker 1>sitting here Jonathan Strickland, one of our writers in the

0:00:38.080 --> 0:00:42.199
<v Speaker 1>flesh Ye, And today we are going to talk about

0:00:42.320 --> 0:00:45.680
<v Speaker 1>some encryption things, things that you might want to keep

0:00:45.720 --> 0:00:47.760
<v Speaker 1>an eye on because this could be an issue of

0:00:47.760 --> 0:00:51.519
<v Speaker 1>great personal significance. Yes, uh. In fact, it was an

0:00:51.520 --> 0:00:55.160
<v Speaker 1>issue of great personal significance for about forty million people recently.

0:00:55.960 --> 0:00:58.280
<v Speaker 1>Um actually probably not that many. That was the That

0:00:58.400 --> 0:01:01.120
<v Speaker 1>was the total number of people acted by a recent

0:01:01.880 --> 0:01:06.039
<v Speaker 1>UH discovery. The federal government had a sting operation where

0:01:06.120 --> 0:01:12.039
<v Speaker 1>they identified eleven international computer hackers who are accused of

0:01:12.040 --> 0:01:15.440
<v Speaker 1>stealing the information of forty million people and some of

0:01:15.480 --> 0:01:20.800
<v Speaker 1>that included pen numbers, which was a that's huge news. Yeah,

0:01:20.840 --> 0:01:23.839
<v Speaker 1>because the thing about it is if somebody has your

0:01:24.160 --> 0:01:27.440
<v Speaker 1>debit card number, they can't do an awful lot with

0:01:27.520 --> 0:01:30.840
<v Speaker 1>it unless they have your pen, your personal identification number.

0:01:31.560 --> 0:01:35.720
<v Speaker 1>So for hackers to get hold of the number and

0:01:35.840 --> 0:01:39.360
<v Speaker 1>the pen, then they're in business because that allowed them

0:01:39.400 --> 0:01:43.640
<v Speaker 1>to create or at least there the authorities are alleging

0:01:43.680 --> 0:01:47.960
<v Speaker 1>that they were able to create fake debit cards with

0:01:48.080 --> 0:01:50.960
<v Speaker 1>numbers and they were allowed to get use those to

0:01:50.960 --> 0:01:52.680
<v Speaker 1>get money. Yeah, they could go to any a t

0:01:52.920 --> 0:01:54.760
<v Speaker 1>M and use that and put in the pin number

0:01:54.840 --> 0:01:58.000
<v Speaker 1>because the number and the pen matched. Uh. The they

0:01:58.400 --> 0:02:00.160
<v Speaker 1>a t M had no way of knowing that this

0:02:00.320 --> 0:02:05.840
<v Speaker 1>was uh, you know, someone impersonating an innocent victim and

0:02:06.200 --> 0:02:08.200
<v Speaker 1>the guy could withdraw money. Now, whether or not this

0:02:08.280 --> 0:02:11.080
<v Speaker 1>actually happened will that remains to be seen. We we haven't.

0:02:11.280 --> 0:02:15.320
<v Speaker 1>We don't have all the information just yet. But um,

0:02:15.360 --> 0:02:19.040
<v Speaker 1>this kind of leads into a discussion about what encryption.

0:02:19.200 --> 0:02:22.640
<v Speaker 1>Encryption is, how it works, why it works, and why

0:02:22.960 --> 0:02:27.800
<v Speaker 1>it's difficult, uh to to crack it. So kind of

0:02:27.840 --> 0:02:30.919
<v Speaker 1>give you an overview of encryption. That's essentially you're talking

0:02:30.919 --> 0:02:36.040
<v Speaker 1>about encoding information, so that only the person or organization

0:02:36.680 --> 0:02:39.400
<v Speaker 1>that receives that information will be able to decode it

0:02:39.760 --> 0:02:43.080
<v Speaker 1>and get at that information. Um. And this is done

0:02:43.240 --> 0:02:47.480
<v Speaker 1>with a key, So the key decodes the encrypted message.

0:02:48.040 --> 0:02:49.360
<v Speaker 1>And there are a couple of different ways you can

0:02:49.400 --> 0:02:54.280
<v Speaker 1>do this right right, Um, Actually, encryption goes back centuries.

0:02:54.560 --> 0:02:57.200
<v Speaker 1>You know, it's something we think about as being sort

0:02:57.200 --> 0:02:59.640
<v Speaker 1>of a new thing. You mean, you hear about famous

0:02:59.680 --> 0:03:03.400
<v Speaker 1>encrypt and like the the Enigma machine from Germany during

0:03:03.440 --> 0:03:06.600
<v Speaker 1>World War Two is a famous way of encrypting messages

0:03:06.880 --> 0:03:10.079
<v Speaker 1>used in wartime. And sure that's you know, the military

0:03:10.120 --> 0:03:15.080
<v Speaker 1>has used codes and encryption, you know, for you know,

0:03:15.120 --> 0:03:17.360
<v Speaker 1>as long as there have been militaries, you know, people

0:03:17.400 --> 0:03:21.920
<v Speaker 1>sending encoded messages. But when we're talking about this, basically

0:03:22.000 --> 0:03:25.120
<v Speaker 1>they're there are two sides to encryption. It's generally the

0:03:25.120 --> 0:03:28.400
<v Speaker 1>way it's done in electronic transmissions. Uh, there is a

0:03:28.520 --> 0:03:30.239
<v Speaker 1>there are two keys. There's a private key and a

0:03:30.280 --> 0:03:35.240
<v Speaker 1>public key, and basically to to get at the encrypted information,

0:03:35.280 --> 0:03:38.280
<v Speaker 1>you have to have both pieces of information right right

0:03:38.280 --> 0:03:41.520
<v Speaker 1>the way. Now, there is one other way you can

0:03:41.560 --> 0:03:43.840
<v Speaker 1>do this besides the public private key, there's there's the

0:03:43.920 --> 0:03:48.880
<v Speaker 1>symmetric key. Encryption approach, but it's it's less secure. Uh,

0:03:48.960 --> 0:03:51.720
<v Speaker 1>symmetric key encryption. What that means is that you have

0:03:52.160 --> 0:03:55.160
<v Speaker 1>two keys that are exactly the same. They can both

0:03:55.720 --> 0:03:58.360
<v Speaker 1>encode and decode information. It's kind of like having a

0:03:58.440 --> 0:04:00.800
<v Speaker 1>decoder ring, you know, like you'd get out of a

0:04:00.880 --> 0:04:05.240
<v Speaker 1>serial box. Kids still eat cereal, right, yeah? Okay, So

0:04:05.480 --> 0:04:09.040
<v Speaker 1>so they basically each person has an identical codebook, right,

0:04:09.120 --> 0:04:11.000
<v Speaker 1>and the person on one end is encoding it with

0:04:11.080 --> 0:04:13.200
<v Speaker 1>the codebook. And you know, you passed through a message

0:04:13.200 --> 0:04:15.960
<v Speaker 1>on your friend who uses the identical codebook and can

0:04:16.040 --> 0:04:18.400
<v Speaker 1>decode the message exactly. The problem with that is if

0:04:18.440 --> 0:04:21.159
<v Speaker 1>anyone else grabs hold of that codebook, they can also

0:04:21.240 --> 0:04:23.800
<v Speaker 1>decode the message, so it's not terribly secure. That's where

0:04:23.800 --> 0:04:27.919
<v Speaker 1>the public private key comes in. Now, in this situation,

0:04:28.400 --> 0:04:31.000
<v Speaker 1>you would have a private key that belongs to you,

0:04:31.080 --> 0:04:33.320
<v Speaker 1>it's on your computer, that's the only place it's ever

0:04:33.360 --> 0:04:35.279
<v Speaker 1>going to be found. And then you have a separate

0:04:35.360 --> 0:04:37.760
<v Speaker 1>key called a public key that you can give to

0:04:38.000 --> 0:04:41.720
<v Speaker 1>whomever so that they can encode information, send it to you,

0:04:41.800 --> 0:04:46.000
<v Speaker 1>and only your private key can decode that information. Um.

0:04:46.279 --> 0:04:50.560
<v Speaker 1>And this this is a this is a secure, more

0:04:50.640 --> 0:04:53.240
<v Speaker 1>secure way of doing things than the symmetric key, because

0:04:53.560 --> 0:04:55.920
<v Speaker 1>it's designed in such a way that you can't figure

0:04:55.920 --> 0:04:59.080
<v Speaker 1>out what the private key is based solely on the

0:04:59.120 --> 0:05:01.440
<v Speaker 1>public key. So you can stare at the public key

0:05:01.440 --> 0:05:03.600
<v Speaker 1>all day long and you're not going to figure out

0:05:03.720 --> 0:05:07.080
<v Speaker 1>what what the right process is to decode that information.

0:05:07.400 --> 0:05:09.599
<v Speaker 1>And on the flip side, if you encode something with

0:05:09.640 --> 0:05:13.320
<v Speaker 1>your private key and send it out, well, because because

0:05:13.360 --> 0:05:15.719
<v Speaker 1>the public key is public, because other people can get

0:05:15.760 --> 0:05:19.240
<v Speaker 1>hold of it, the information in that message won't be secure,

0:05:19.440 --> 0:05:24.000
<v Speaker 1>but it is verifiable that it came from you, So

0:05:24.080 --> 0:05:27.240
<v Speaker 1>it becomes kind of a digital signature, right You're you're saying, well,

0:05:27.560 --> 0:05:30.560
<v Speaker 1>the public key can only decode informations that came from

0:05:30.560 --> 0:05:33.599
<v Speaker 1>this particular private key, so we know the information came

0:05:33.600 --> 0:05:36.640
<v Speaker 1>from him. The information itself isn't secure, but at least

0:05:36.680 --> 0:05:40.000
<v Speaker 1>you know, like it's an authentication. It's it's like a

0:05:40.040 --> 0:05:43.240
<v Speaker 1>digital signature. You know, you can it's absolutely verifiable that

0:05:43.320 --> 0:05:47.760
<v Speaker 1>it came from this person. Um, you know what. There

0:05:47.839 --> 0:05:50.479
<v Speaker 1>is one way around that though, if somewhere were able

0:05:50.520 --> 0:05:53.040
<v Speaker 1>to get hold of your, say your laptop computer with

0:05:53.080 --> 0:05:57.039
<v Speaker 1>your digital signature, you know, embedded in the computer, and

0:05:57.160 --> 0:06:00.920
<v Speaker 1>you weren't encrypting your log in information. If it were

0:06:00.960 --> 0:06:04.760
<v Speaker 1>just on then they could sign documents, which you know

0:06:04.960 --> 0:06:07.880
<v Speaker 1>is another important part of encryption. It's not just for

0:06:08.320 --> 0:06:10.760
<v Speaker 1>you know, your your pin number at your bank. You've

0:06:10.800 --> 0:06:13.320
<v Speaker 1>got all kinds of other things that that could uh

0:06:13.480 --> 0:06:16.440
<v Speaker 1>stand to be encrypted, especially if you have, uh, you know,

0:06:16.560 --> 0:06:20.240
<v Speaker 1>very private information. If you have, say, uh, your bank

0:06:20.279 --> 0:06:24.440
<v Speaker 1>account information on your computer. Um, my wife keeps a

0:06:24.480 --> 0:06:26.880
<v Speaker 1>backup of our financial data on there. Well, if she

0:06:27.400 --> 0:06:31.320
<v Speaker 1>were to not encrypt the log into her computer, someone

0:06:31.360 --> 0:06:34.000
<v Speaker 1>could break into our house, open the computer up and

0:06:34.040 --> 0:06:37.640
<v Speaker 1>see all that information because the log into the computer

0:06:37.800 --> 0:06:41.680
<v Speaker 1>is wide open. Um. You know, they're they're all kinds

0:06:41.680 --> 0:06:44.400
<v Speaker 1>of other things to Email is one of the most

0:06:44.560 --> 0:06:48.440
<v Speaker 1>common places that you're going to see encryption. Um, you know,

0:06:48.440 --> 0:06:52.600
<v Speaker 1>where you're actually aware of it being there. Um. There

0:06:52.600 --> 0:06:56.600
<v Speaker 1>are ways to add that to your email program uh,

0:06:56.720 --> 0:07:00.360
<v Speaker 1>programs like Pretty Good Privacy or there are There are

0:07:00.360 --> 0:07:05.520
<v Speaker 1>actually some open source encryption standards, and even Google is

0:07:05.560 --> 0:07:09.320
<v Speaker 1>talking about the possibility of adding a new open source

0:07:09.400 --> 0:07:12.760
<v Speaker 1>encryption standard a p I, so that other people can

0:07:12.800 --> 0:07:16.480
<v Speaker 1>incorporate that into their into their products. And I imagine

0:07:16.560 --> 0:07:18.400
<v Speaker 1>and you know, they don't say that, but I'm just

0:07:18.400 --> 0:07:20.480
<v Speaker 1>guessing that it's probably gonna end up in Gmail too,

0:07:21.040 --> 0:07:24.240
<v Speaker 1>so that you can say encrypted messages back and forth.

0:07:25.000 --> 0:07:29.400
<v Speaker 1>And you might be wondering how all this encoding happens. UM.

0:07:29.440 --> 0:07:34.320
<v Speaker 1>It's generally uh accomplished through the use of a hashing

0:07:34.440 --> 0:07:40.240
<v Speaker 1>algorithm to create a hash value. Now, an algorithm is

0:07:40.240 --> 0:07:43.400
<v Speaker 1>a set of instructions that that machines follow to to

0:07:43.560 --> 0:07:47.600
<v Speaker 1>complete a certain task. With a hash value hashing algorithm,

0:07:48.080 --> 0:07:51.960
<v Speaker 1>what what happens is that it takes an agreed upon number.

0:07:51.960 --> 0:07:54.880
<v Speaker 1>For example, this is just one of many different versions

0:07:54.880 --> 0:07:58.119
<v Speaker 1>of hashing, but takes an agreed upon number that both

0:07:58.200 --> 0:08:01.200
<v Speaker 1>the public and private key no, and it multiplies it

0:08:01.240 --> 0:08:05.120
<v Speaker 1>by a different number, and without anyone knowing what that

0:08:05.160 --> 0:08:07.480
<v Speaker 1>different number is. There's you know what what you end

0:08:07.520 --> 0:08:09.760
<v Speaker 1>up with is the product of those two numbers. UM.

0:08:09.800 --> 0:08:12.640
<v Speaker 1>If you don't know the identity of either of the

0:08:13.520 --> 0:08:18.200
<v Speaker 1>two factors that went into making this product. UM, that's

0:08:18.240 --> 0:08:20.240
<v Speaker 1>where the encryption comes in. You have to be able

0:08:20.280 --> 0:08:24.040
<v Speaker 1>to say, hey, this number was arrived at by multiplying

0:08:24.520 --> 0:08:27.680
<v Speaker 1>this number by this number. I'm the right person, let

0:08:27.680 --> 0:08:31.119
<v Speaker 1>me see that information. UM. That kind of plays into

0:08:31.640 --> 0:08:35.520
<v Speaker 1>r s A encryption, which is uh the idea that

0:08:35.640 --> 0:08:40.800
<v Speaker 1>computers are really really bad at figuring out uh, the

0:08:40.880 --> 0:08:44.080
<v Speaker 1>factors of a very very very very large number. We're

0:08:44.080 --> 0:08:46.319
<v Speaker 1>talking about a hundred and twenty eight bit number, so

0:08:46.640 --> 0:08:51.360
<v Speaker 1>uh uh this is this is a very large figure

0:08:51.400 --> 0:08:56.160
<v Speaker 1>that that you have to take into account. So the

0:08:57.160 --> 0:08:58.720
<v Speaker 1>what a computer has to do is it has to

0:08:58.760 --> 0:09:01.160
<v Speaker 1>go through and try and figure each of those factors,

0:09:01.200 --> 0:09:04.120
<v Speaker 1>finding the largest prime numbers that that factored together to

0:09:04.120 --> 0:09:08.079
<v Speaker 1>to make this uh product um and computers take can

0:09:08.080 --> 0:09:10.880
<v Speaker 1>take millions and millions of years to do this with

0:09:11.240 --> 0:09:15.040
<v Speaker 1>a really really large number. Uh. In fact, the only

0:09:15.200 --> 0:09:19.760
<v Speaker 1>real way of of cracking it right now, at least

0:09:19.760 --> 0:09:22.640
<v Speaker 1>as far as people are theorizing, is to create a

0:09:22.720 --> 0:09:29.240
<v Speaker 1>quantum computer. Yeah. Quantum computers operate on a much different level. Yeah,

0:09:29.320 --> 0:09:33.160
<v Speaker 1>it's it's kind of a mysterious, magical level almost because

0:09:33.520 --> 0:09:37.240
<v Speaker 1>you may know that the classic computers operate by looking

0:09:37.280 --> 0:09:39.400
<v Speaker 1>at bits, so it's either a zero or it's a one,

0:09:39.520 --> 0:09:42.400
<v Speaker 1>But with quantum computers it's a little bit more bizarre.

0:09:42.520 --> 0:09:44.800
<v Speaker 1>It can be both a zero and a one, or

0:09:44.840 --> 0:09:48.240
<v Speaker 1>a zero or a one or anything in between, which

0:09:48.280 --> 0:09:51.240
<v Speaker 1>is kind of hard to get your mind wrapped around,

0:09:51.640 --> 0:09:55.880
<v Speaker 1>and quantum computers have uh the potential of being able

0:09:55.920 --> 0:09:58.959
<v Speaker 1>to crack this really hard encryption. It's through the use

0:09:59.000 --> 0:10:02.960
<v Speaker 1>of something called s wars algorithm UM, and it's a

0:10:03.080 --> 0:10:07.320
<v Speaker 1>really really complicated, complicated process. It's it's really hard to

0:10:07.360 --> 0:10:10.440
<v Speaker 1>explain in layman's terms, so we won't really get into

0:10:10.440 --> 0:10:13.520
<v Speaker 1>it here because I'm not a mathematician and I'm sure

0:10:13.520 --> 0:10:18.120
<v Speaker 1>i'd stumble along the way. But it's it's because quantum

0:10:18.120 --> 0:10:20.959
<v Speaker 1>computers are not actually viable right now. We can't really

0:10:20.960 --> 0:10:24.880
<v Speaker 1>make a stable quantum computer of any significant size. It's

0:10:24.920 --> 0:10:28.280
<v Speaker 1>something to worry about, but it's further down the road, right,

0:10:28.320 --> 0:10:31.400
<v Speaker 1>So it's very unlikely that you're going to have to

0:10:31.440 --> 0:10:35.079
<v Speaker 1>worry if you come up with a reasonable uh level

0:10:35.080 --> 0:10:38.280
<v Speaker 1>of encryption on your computer that it's you know, nothing's

0:10:38.320 --> 0:10:41.920
<v Speaker 1>going to be able to hack it easily, right, you know.

0:10:41.960 --> 0:10:44.200
<v Speaker 1>But the more complex you can make your passwords, the

0:10:44.240 --> 0:10:47.840
<v Speaker 1>more involved you can you can get your encryption. If

0:10:47.840 --> 0:10:50.520
<v Speaker 1>you could take it up to or even two six

0:10:50.600 --> 0:10:54.319
<v Speaker 1>bit encryption, it's just going to take a computer longer

0:10:54.360 --> 0:10:58.160
<v Speaker 1>to try to break the code and decrypt your messages

0:10:58.480 --> 0:11:01.440
<v Speaker 1>or you know, get into your file else. So you

0:11:01.480 --> 0:11:04.079
<v Speaker 1>know that that if you can take the steps necessary,

0:11:04.120 --> 0:11:06.680
<v Speaker 1>you can make sure that your your private information is

0:11:06.720 --> 0:11:09.760
<v Speaker 1>more private. Of course, that doesn't really help when you're

0:11:09.880 --> 0:11:12.640
<v Speaker 1>talking about someone else's network, like you know, your local

0:11:12.640 --> 0:11:15.760
<v Speaker 1>mall the wireless networks that they used to to get

0:11:15.760 --> 0:11:17.720
<v Speaker 1>that information. Yeah, it kind of brings us back to

0:11:17.760 --> 0:11:19.880
<v Speaker 1>the story we were talking about at the beginning. So

0:11:19.920 --> 0:11:23.040
<v Speaker 1>how did these guys managed to crack this encryption? Well,

0:11:23.080 --> 0:11:26.800
<v Speaker 1>we don't really know right now, but the one theory

0:11:26.840 --> 0:11:29.360
<v Speaker 1>is that they actually managed to get hold of the

0:11:29.480 --> 0:11:33.800
<v Speaker 1>key that unlocks this information. That they did not actually

0:11:34.120 --> 0:11:38.240
<v Speaker 1>decrypt it through some sort of complex hacking system. They

0:11:38.280 --> 0:11:42.240
<v Speaker 1>just managed to get hold of that special dacoder ring. Um.

0:11:42.320 --> 0:11:45.680
<v Speaker 1>So if that's the case, then encryption is not nearly

0:11:45.720 --> 0:11:49.800
<v Speaker 1>as badly off as as we would think Otherwise, If, however,

0:11:49.840 --> 0:11:53.600
<v Speaker 1>they found a way to decrypt that themselves without the key,

0:11:53.640 --> 0:11:56.839
<v Speaker 1>that's something to really really start to freak out about.

0:11:56.920 --> 0:12:01.080
<v Speaker 1>I think we all have things to think about, like say,

0:12:01.200 --> 0:12:03.160
<v Speaker 1>what's the best site to buy a new leather jacket,

0:12:03.640 --> 0:12:06.679
<v Speaker 1>whether to buy the three or six megapixel cameras. But

0:12:06.800 --> 0:12:09.800
<v Speaker 1>thankfully we don't need to think about online fraud because

0:12:09.840 --> 0:12:12.400
<v Speaker 1>for every purchase you make. Visa keeps an eye out

0:12:12.440 --> 0:12:16.040
<v Speaker 1>for fraud with real time fraud monitoring and by making

0:12:16.040 --> 0:12:19.480
<v Speaker 1>sure you're not liable for any unauthorized purchases. How's that

0:12:19.559 --> 0:12:25.680
<v Speaker 1>for peace of mind, safe secure Visa. Yeah, the authorities

0:12:25.720 --> 0:12:29.040
<v Speaker 1>in the article I read in an MSNBC said that,

0:12:30.280 --> 0:12:31.959
<v Speaker 1>you know, there really wasn't any reason to worry. It

0:12:32.000 --> 0:12:34.719
<v Speaker 1>didn't appear like this is a widespread phenomenon, and then

0:12:34.760 --> 0:12:38.760
<v Speaker 1>not sure that that it actually happened the way that

0:12:39.040 --> 0:12:42.319
<v Speaker 1>they think that it may have happened. But if if

0:12:42.360 --> 0:12:45.160
<v Speaker 1>these uh, these hackers were able to figure this out,

0:12:45.920 --> 0:12:47.559
<v Speaker 1>you know, we may be moving on to a new

0:12:47.600 --> 0:12:50.839
<v Speaker 1>standard in encryption in a very short time. Yeah. Nothing

0:12:50.880 --> 0:12:54.400
<v Speaker 1>like nothing like impending doom to really get you get

0:12:54.400 --> 0:12:57.000
<v Speaker 1>the gears running right right. Well, I guess that's about

0:12:57.040 --> 0:12:59.720
<v Speaker 1>all we have right now for encryption. But if you'd

0:12:59.760 --> 0:13:02.880
<v Speaker 1>like to learn more, you can read how encryption works

0:13:02.960 --> 0:13:05.480
<v Speaker 1>at how stuff works dot com and we'll talk to

0:13:05.480 --> 0:13:09.320
<v Speaker 1>you again soon. Let us know what you think. Send

0:13:09.320 --> 0:13:15.720
<v Speaker 1>an email to podcast at how stuff works dot com.

0:13:15.800 --> 0:13:18.400
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:13:18.679 --> 0:13:19.880
<v Speaker 1>It's ready, are you