WEBVTT - Codes! Axis Cryptography in World War II

0:00:00.560 --> 0:00:03.760
<v Speaker 1>Welcome to Stuff you missed in History Class from how

0:00:03.800 --> 0:00:13.760
<v Speaker 1>Stuff Works dot com. Hello, and welcome to the podcast.

0:00:13.840 --> 0:00:17.040
<v Speaker 1>I'm Sarah Dowdy and today I am joined by a

0:00:17.160 --> 0:00:21.560
<v Speaker 1>very special guest, Jonathan Strickland. Hey there, So you guys

0:00:21.600 --> 0:00:25.000
<v Speaker 1>probably remember Jonathan Strickland. He joined um. He joined both

0:00:25.040 --> 0:00:27.520
<v Speaker 1>of us a few months ago as the Admiral for

0:00:27.720 --> 0:00:31.560
<v Speaker 1>our Renaissance Festival episode. But this time he is here

0:00:31.760 --> 0:00:37.479
<v Speaker 1>in his real life version, presenting on technology, which is

0:00:37.520 --> 0:00:41.559
<v Speaker 1>your your specialty, my forte. As they say, there will

0:00:41.600 --> 0:00:45.040
<v Speaker 1>be no hazas this particular episode. Maybe we could squeeze

0:00:45.080 --> 0:00:48.199
<v Speaker 1>one and at the end or something. But Jonathan is

0:00:48.280 --> 0:00:50.320
<v Speaker 1>the co host of tech Stuff is probably a lot

0:00:50.360 --> 0:00:53.200
<v Speaker 1>of y'all know, and he also is a staff writer

0:00:53.240 --> 0:00:58.200
<v Speaker 1>who specializes in technology articles and Deplina and I often

0:00:58.240 --> 0:01:02.280
<v Speaker 1>talk about how you would like somebody like Jonathan and

0:01:02.400 --> 0:01:06.760
<v Speaker 1>Chris to join us for technology related episodes sometimes when

0:01:06.760 --> 0:01:10.399
<v Speaker 1>we really want something better explained than we're able to do.

0:01:10.640 --> 0:01:13.280
<v Speaker 1>And we've actually covered a lot of the same topics

0:01:13.319 --> 0:01:15.920
<v Speaker 1>as you and Chris too, Yes, that's true. We've We've

0:01:15.959 --> 0:01:20.080
<v Speaker 1>covered several things, including Ada Lovelace, who I think got

0:01:20.080 --> 0:01:23.000
<v Speaker 1>an enormous amount of praise on both of our podcast

0:01:23.640 --> 0:01:27.640
<v Speaker 1>she was phenomenal, absolutely holomonal to be able to reach

0:01:27.680 --> 0:01:29.440
<v Speaker 1>a point where not only was she able to write

0:01:29.440 --> 0:01:32.160
<v Speaker 1>programs for a machine that did not yet exist, but

0:01:32.360 --> 0:01:35.760
<v Speaker 1>recognize that numbers can substitute in for things and actually

0:01:35.760 --> 0:01:40.680
<v Speaker 1>represent other forms of media like music or pictures at

0:01:40.680 --> 0:01:43.040
<v Speaker 1>a time where there was no device to do that.

0:01:43.160 --> 0:01:47.280
<v Speaker 1>On is beyond my imagination to do all that while

0:01:47.360 --> 0:01:50.480
<v Speaker 1>being the daughter of Lord Byron. Of course, well you know,

0:01:50.560 --> 0:01:53.560
<v Speaker 1>I would say that helps probably had a little dose

0:01:53.560 --> 0:01:56.800
<v Speaker 1>of the crazy in there too, but no, absolutely phenomenal

0:01:57.120 --> 0:01:59.360
<v Speaker 1>and other topics as well, But yes, and this is

0:01:59.400 --> 0:02:02.080
<v Speaker 1>one that that I know that stuff you missed in

0:02:02.080 --> 0:02:05.920
<v Speaker 1>history classes touched on related topics, and we at Tech

0:02:05.960 --> 0:02:08.519
<v Speaker 1>Stuff have talked about some related topics, but we wanted

0:02:08.560 --> 0:02:11.280
<v Speaker 1>to sort of look at the overall picture of what

0:02:11.360 --> 0:02:15.079
<v Speaker 1>cryptography was like during World War Two. And this will

0:02:15.120 --> 0:02:17.680
<v Speaker 1>be sort of the kickoff of a little series that

0:02:17.680 --> 0:02:19.760
<v Speaker 1>I'm going to do with a few other How Stuff

0:02:19.760 --> 0:02:23.639
<v Speaker 1>Works podcast co host who all focusing on something that's

0:02:23.720 --> 0:02:27.600
<v Speaker 1>history related but also focused on their specialty. So that's

0:02:27.600 --> 0:02:32.000
<v Speaker 1>why Jonathan has picked Codes Today, something that is tech

0:02:32.080 --> 0:02:36.119
<v Speaker 1>related but has a really fascinating history behind it too, Yes,

0:02:36.120 --> 0:02:39.560
<v Speaker 1>and that history stretches way back before World War two,

0:02:39.600 --> 0:02:42.359
<v Speaker 1>of course. Uh. And I even had a little crash

0:02:42.440 --> 0:02:44.959
<v Speaker 1>course in cryptography I wrote up so that we could

0:02:45.040 --> 0:02:48.080
<v Speaker 1>kind of have a common language to work from. And

0:02:48.240 --> 0:02:51.120
<v Speaker 1>it does come from a pair of Greek words. Essentially

0:02:51.120 --> 0:02:55.000
<v Speaker 1>means hidden writing is what cryptography really boils down to,

0:02:55.360 --> 0:02:58.760
<v Speaker 1>and it is the idea of hiding a message by

0:02:59.000 --> 0:03:02.520
<v Speaker 1>encoding it and so way, and very common way is

0:03:02.600 --> 0:03:05.520
<v Speaker 1>using a cipher where you are replacing letters within a

0:03:05.560 --> 0:03:09.600
<v Speaker 1>message with some other letter or symbol or number, and

0:03:10.000 --> 0:03:13.519
<v Speaker 1>you're using a very specific key so that someone who

0:03:13.520 --> 0:03:18.080
<v Speaker 1>receives that message, the intended recipient, can take the encoded message,

0:03:18.120 --> 0:03:20.799
<v Speaker 1>they take the key, and then using the key, they

0:03:20.880 --> 0:03:25.160
<v Speaker 1>decode the message. But ideally anyone else who intercepts said

0:03:25.160 --> 0:03:27.440
<v Speaker 1>message would just have a bunch of gibberish that they

0:03:27.560 --> 0:03:31.200
<v Speaker 1>could not understand. Now, in reality, a lot of these

0:03:31.200 --> 0:03:35.880
<v Speaker 1>ciphers don't remain secure forever, and we will see, right

0:03:36.240 --> 0:03:38.320
<v Speaker 1>and there we have some very good examples of that.

0:03:38.600 --> 0:03:40.760
<v Speaker 1>But there are a lot of different types of ciphers,

0:03:40.800 --> 0:03:44.440
<v Speaker 1>and one of those, the most basic is the mono

0:03:44.600 --> 0:03:49.080
<v Speaker 1>alphabetic cipher. That's where you use one symbol to replace

0:03:49.720 --> 0:03:52.600
<v Speaker 1>each letter, and probably everybody is familiar with that one.

0:03:52.640 --> 0:03:55.880
<v Speaker 1>It's what I used in my spy club as a kid.

0:03:56.000 --> 0:03:59.200
<v Speaker 1>It's pretty straightforward. Maybe when you're eight it seems like

0:03:59.240 --> 0:04:02.480
<v Speaker 1>it would be a breakable, but in reality it's pretty

0:04:02.520 --> 0:04:04.640
<v Speaker 1>easy to crack right right. This would be when you

0:04:04.880 --> 0:04:07.120
<v Speaker 1>might say, all right, let's shift all the letters over

0:04:07.240 --> 0:04:10.560
<v Speaker 1>four letters, and no one will ever figure it out, right,

0:04:10.920 --> 0:04:14.119
<v Speaker 1>So A becomes D and B becomes E and uh.

0:04:14.320 --> 0:04:17.880
<v Speaker 1>It seems at first, when you are unaware of how

0:04:17.920 --> 0:04:21.640
<v Speaker 1>to analyze cryptography that that would be be fairly secure.

0:04:22.040 --> 0:04:25.479
<v Speaker 1>But just using something simple as a frequency analysis, which

0:04:25.520 --> 0:04:30.240
<v Speaker 1>is typically the frequency that certain letter combinations appear in

0:04:30.279 --> 0:04:32.760
<v Speaker 1>any given language. So if you know that the message

0:04:32.800 --> 0:04:35.120
<v Speaker 1>was written in English, you know it's ciphered, but it's

0:04:35.120 --> 0:04:38.279
<v Speaker 1>an English based language, you could start looking for letter

0:04:38.320 --> 0:04:41.680
<v Speaker 1>combinations that would give away what the coded letters are.

0:04:41.760 --> 0:04:44.640
<v Speaker 1>So look for double letters for example. Those could be

0:04:44.680 --> 0:04:48.000
<v Speaker 1>ta s or l's, things like that, things word very

0:04:48.000 --> 0:04:50.479
<v Speaker 1>short words exactly if you haven't. If you if you

0:04:50.520 --> 0:04:53.520
<v Speaker 1>have your text actually broken up in the same grouping

0:04:53.680 --> 0:04:57.479
<v Speaker 1>of of letters as your plain text, words are that's

0:04:57.480 --> 0:04:59.880
<v Speaker 1>a dead giveaway, which is why a lot of ciphers

0:04:59.880 --> 0:05:03.240
<v Speaker 1>are written in five letter blocks, so that you might

0:05:03.279 --> 0:05:06.120
<v Speaker 1>even have two short words combined together or a very

0:05:06.160 --> 0:05:09.640
<v Speaker 1>long word broken across a couple of blocks, and it

0:05:09.680 --> 0:05:12.120
<v Speaker 1>makes it harder to detect, but even then pretty easy

0:05:12.160 --> 0:05:15.640
<v Speaker 1>to figure out exactly the analysis. So another version of

0:05:15.640 --> 0:05:18.000
<v Speaker 1>this one that's a little bit more complicated, is the

0:05:18.080 --> 0:05:22.719
<v Speaker 1>polyalphabetic ciphers, and those substitute each letter with a different

0:05:22.880 --> 0:05:26.400
<v Speaker 1>symbol based upon where the letter appeared in the message.

0:05:26.800 --> 0:05:31.080
<v Speaker 1>So instead of a direct substitution, just it's the first letter,

0:05:31.120 --> 0:05:33.040
<v Speaker 1>it's the second letter, and so on, it can be

0:05:33.080 --> 0:05:35.360
<v Speaker 1>like that. Yeah, and there's there's a couple different methods

0:05:35.360 --> 0:05:37.719
<v Speaker 1>of doing this where, for example, the first time the

0:05:37.800 --> 0:05:40.560
<v Speaker 1>letter if the letter A appears in your message, it

0:05:40.640 --> 0:05:44.279
<v Speaker 1>maybe in ciphered. I'm just grabbing the letter at random

0:05:44.279 --> 0:05:47.120
<v Speaker 1>with L. And the second time the letter A appears,

0:05:47.400 --> 0:05:51.560
<v Speaker 1>it may be the letter D. And it all depends

0:05:51.680 --> 0:05:55.440
<v Speaker 1>upon the specific set of rules you have set down

0:05:55.480 --> 0:05:58.240
<v Speaker 1>for that key the algorithm, if you like, that's the

0:05:58.520 --> 0:06:02.080
<v Speaker 1>specific protocol the you follow, and that does make it

0:06:02.160 --> 0:06:05.240
<v Speaker 1>much more difficult to break because you can't guarantee that

0:06:05.279 --> 0:06:07.760
<v Speaker 1>every time you see a certain cipher that it's going

0:06:07.800 --> 0:06:10.280
<v Speaker 1>to translate to the same letter. Moving on from there,

0:06:10.279 --> 0:06:14.240
<v Speaker 1>we get a little bit more complicated and have polygraphic ciphers.

0:06:14.320 --> 0:06:18.680
<v Speaker 1>Those use a combination of letters, numbers, or symbols for

0:06:18.800 --> 0:06:24.359
<v Speaker 1>each quoted letters, so we don't have this direct translation anymore.

0:06:24.440 --> 0:06:26.599
<v Speaker 1>It's not going to be something that you can just

0:06:26.720 --> 0:06:30.039
<v Speaker 1>break out into the original words in the plane text

0:06:30.120 --> 0:06:33.520
<v Speaker 1>to the cipher text. That's right. You. It's very confusing

0:06:33.520 --> 0:06:35.520
<v Speaker 1>when you first get one of these messages because you

0:06:35.560 --> 0:06:39.119
<v Speaker 1>can't be sure how many characters represent one single letter,

0:06:39.680 --> 0:06:42.240
<v Speaker 1>and by doing that you really make it more difficult

0:06:42.279 --> 0:06:44.480
<v Speaker 1>to break the code. And then I think the last

0:06:44.480 --> 0:06:47.320
<v Speaker 1>one we have here is the transposition ciphers, which it's

0:06:47.400 --> 0:06:50.280
<v Speaker 1>kind of like a word jumble, where you've taken the

0:06:50.400 --> 0:06:53.719
<v Speaker 1>letters of the of the message, the plane text message,

0:06:53.760 --> 0:06:55.640
<v Speaker 1>and you just mixed up the letters. So you're not

0:06:55.720 --> 0:06:59.680
<v Speaker 1>replacing any letters here, you're mixing them up according to

0:06:59.800 --> 0:07:04.560
<v Speaker 1>a in a prearranged code. So you might say, all, right,

0:07:05.360 --> 0:07:08.000
<v Speaker 1>letter of this message should appear first, then the fifth

0:07:08.040 --> 0:07:10.960
<v Speaker 1>letter of the message apers second, and you just follow

0:07:11.040 --> 0:07:12.880
<v Speaker 1>that key and as long as the other person has

0:07:12.920 --> 0:07:15.360
<v Speaker 1>the same key, they can unscramble it, but of course

0:07:15.400 --> 0:07:18.640
<v Speaker 1>that's not terribly safe either. People with a lot of

0:07:18.680 --> 0:07:21.800
<v Speaker 1>imagination can piece us together, sort of like Sunday Morning.

0:07:21.880 --> 0:07:25.000
<v Speaker 1>Not for your top secret message. Yeah, a hobbyist could

0:07:25.080 --> 0:07:28.520
<v Speaker 1>could crack that with enough ingenuity and time. So another

0:07:28.600 --> 0:07:30.480
<v Speaker 1>element in here, and one that we're going to be

0:07:30.520 --> 0:07:33.680
<v Speaker 1>talking about quite a bit in our second episode on

0:07:33.720 --> 0:07:37.200
<v Speaker 1>this uh this subject is codebook. So code books, of

0:07:37.200 --> 0:07:40.960
<v Speaker 1>course contain a list of phrases that linked to specific

0:07:40.960 --> 0:07:42.920
<v Speaker 1>code words. So if you were just reading them, they

0:07:43.000 --> 0:07:45.440
<v Speaker 1>might be familiar words, but they don't have any meaning

0:07:45.520 --> 0:07:48.640
<v Speaker 1>to you. You can't you can't decipher it. You can't

0:07:48.640 --> 0:07:51.520
<v Speaker 1>into it what the word might represent in any way

0:07:51.640 --> 0:07:54.520
<v Speaker 1>unless you have the book right. So you could possibly

0:07:54.600 --> 0:07:57.880
<v Speaker 1>break a cipher and you know that this next word

0:07:58.240 --> 0:08:01.920
<v Speaker 1>is hawk, but you don't know what hawk means. It

0:08:02.000 --> 0:08:04.520
<v Speaker 1>could it could mean a bird, but it might actually

0:08:04.640 --> 0:08:07.200
<v Speaker 1>stand for something else, probably does in the case of wartime,

0:08:07.760 --> 0:08:10.120
<v Speaker 1>And you know, you might be able to make some guesses,

0:08:10.200 --> 0:08:13.200
<v Speaker 1>but you're not necessarily going to know. So codebooks were

0:08:13.200 --> 0:08:17.440
<v Speaker 1>also very very important on both sides during the World

0:08:17.440 --> 0:08:20.040
<v Speaker 1>War Two, And if you combine that with ciphers, you

0:08:20.040 --> 0:08:23.280
<v Speaker 1>are getting a pretty tough code. Finally, and then a

0:08:23.360 --> 0:08:28.760
<v Speaker 1>related technique to cryptography is called steganography, which is hiding

0:08:28.880 --> 0:08:32.840
<v Speaker 1>a message within an image or some other kind of medium. Right,

0:08:32.920 --> 0:08:36.440
<v Speaker 1>this is really super cool stuff. This is where let's say,

0:08:36.440 --> 0:08:38.240
<v Speaker 1>Sarah that I met you on the street and I

0:08:38.280 --> 0:08:40.760
<v Speaker 1>handed you a postcard and the postcard just said hey,

0:08:40.760 --> 0:08:43.040
<v Speaker 1>how are you doing? And it has nothing else on

0:08:43.120 --> 0:08:44.920
<v Speaker 1>there's no other message there, and you think, oh, well,

0:08:44.920 --> 0:08:47.400
<v Speaker 1>that's just completely innocent. But on the flip side of

0:08:47.400 --> 0:08:50.720
<v Speaker 1>the the postcard, where the picture is, which looks like

0:08:50.760 --> 0:08:54.800
<v Speaker 1>this nice little landscape, you could maybe actually noticed that

0:08:54.840 --> 0:08:57.720
<v Speaker 1>along the edge of a lake, there's really a message

0:08:57.760 --> 0:09:00.080
<v Speaker 1>that's in there. And you look more carefully and you

0:09:00.120 --> 0:09:03.480
<v Speaker 1>see that there's something hidden and it's hidden from plain

0:09:03.559 --> 0:09:05.880
<v Speaker 1>sighte uh. And it can get a lot more complicated,

0:09:05.960 --> 0:09:08.280
<v Speaker 1>especially with today's technology, where you can hide things in

0:09:09.360 --> 0:09:12.840
<v Speaker 1>u R L, you can hide things within a QR code.

0:09:13.000 --> 0:09:15.520
<v Speaker 1>It's it's lots of different ways of hiding a message,

0:09:15.800 --> 0:09:17.760
<v Speaker 1>but it's done in such a way that from the

0:09:17.840 --> 0:09:22.400
<v Speaker 1>casual observer's perspective, no message even existed. I like this one,

0:09:22.440 --> 0:09:25.280
<v Speaker 1>although it doesn't sound quite as practical as the others,

0:09:25.400 --> 0:09:30.160
<v Speaker 1>especially for wartime communications. You're not really thinking romantic spy

0:09:30.280 --> 0:09:34.520
<v Speaker 1>sort of stuff. Yes, exactly, all right, So now that

0:09:34.559 --> 0:09:39.320
<v Speaker 1>we've gotten a background on cryptography, we can start talking

0:09:39.360 --> 0:09:43.360
<v Speaker 1>about how it was used in World War Two, which

0:09:43.440 --> 0:09:46.720
<v Speaker 1>is sort of the heyday almost it seems, of cryptography.

0:09:46.840 --> 0:09:49.000
<v Speaker 1>It's it's really I would say World War Two is

0:09:49.040 --> 0:09:53.800
<v Speaker 1>probably the foundation for modern cryptography. The developments that were

0:09:53.840 --> 0:09:56.760
<v Speaker 1>made during that era leading up to World War Two,

0:09:56.800 --> 0:10:01.680
<v Speaker 1>but really uh intensely built upon during the years of

0:10:01.720 --> 0:10:04.880
<v Speaker 1>World War Two that has led to to the way

0:10:04.920 --> 0:10:09.600
<v Speaker 1>we use cryptography today. So it's it's an important time

0:10:09.640 --> 0:10:12.280
<v Speaker 1>in history as far as this whole development of science

0:10:12.360 --> 0:10:14.200
<v Speaker 1>is concerned. It is. And we're going to start by

0:10:14.200 --> 0:10:18.480
<v Speaker 1>talking about the axis powers use of cryptography, partly because

0:10:18.520 --> 0:10:20.439
<v Speaker 1>we want to start this whole thing off by talking

0:10:20.440 --> 0:10:24.679
<v Speaker 1>about the Enigma machine. It's probably the most famous example

0:10:24.880 --> 0:10:27.360
<v Speaker 1>of cryptography in World War Two, I would say, and

0:10:27.480 --> 0:10:30.520
<v Speaker 1>something that we have both talked about on our podcast.

0:10:30.720 --> 0:10:33.600
<v Speaker 1>Deplena and I talked about it in our Alan Touring episode.

0:10:33.640 --> 0:10:37.120
<v Speaker 1>You and Chris talked about it in your Alan Touring episode.

0:10:36.640 --> 0:10:40.079
<v Speaker 1>It's something that I think most people out there are

0:10:40.600 --> 0:10:43.079
<v Speaker 1>they've at least heard of it. Yes, And if you

0:10:43.120 --> 0:10:44.800
<v Speaker 1>were to look at one of these things, it would

0:10:44.800 --> 0:10:47.160
<v Speaker 1>look like it was a typewriter and a whole bunch

0:10:47.160 --> 0:10:50.760
<v Speaker 1>of lightbulbs and some plugs going every which way, and

0:10:50.920 --> 0:10:53.120
<v Speaker 1>you might wonder what was the purpose. Looks like a

0:10:53.120 --> 0:10:56.240
<v Speaker 1>mad inventor thought. It really doesn't. And the person who

0:10:56.320 --> 0:10:58.400
<v Speaker 1>actually thought it up was not a mad inventor. He

0:10:58.520 --> 0:11:01.319
<v Speaker 1>was he was quite He was ingenious in his own way,

0:11:01.360 --> 0:11:04.920
<v Speaker 1>as Dr Arthur Sherbius, And that was in nineteen twenty three,

0:11:04.960 --> 0:11:07.640
<v Speaker 1>and he was inventing this not as a means for

0:11:07.800 --> 0:11:10.840
<v Speaker 1>the government to pass along secret messages to various branches

0:11:10.840 --> 0:11:14.480
<v Speaker 1>of the military or intermilitary messages. It wasn't meant for

0:11:14.480 --> 0:11:16.800
<v Speaker 1>that at all. It was meant for corporations to try

0:11:16.840 --> 0:11:19.960
<v Speaker 1>and send secret messages so they could keep corporate secrets,

0:11:20.320 --> 0:11:26.079
<v Speaker 1>so that other competitors wouldn't steal corporate information, private information private.

0:11:26.120 --> 0:11:29.600
<v Speaker 1>But of course the German government quickly realized that this

0:11:29.679 --> 0:11:34.320
<v Speaker 1>could be a useful tool for very secret communications, and

0:11:34.360 --> 0:11:38.960
<v Speaker 1>so in nineteen the German Navy started using a modified

0:11:39.120 --> 0:11:42.120
<v Speaker 1>version of the Enigma machine and and from there it

0:11:42.200 --> 0:11:44.600
<v Speaker 1>sort of picked out the German Army followed in nineteen

0:11:45.320 --> 0:11:48.480
<v Speaker 1>The Air Force started using one in nineteen thirty three.

0:11:48.520 --> 0:11:50.720
<v Speaker 1>We should say, though they were all modified, they were

0:11:50.760 --> 0:11:54.440
<v Speaker 1>all a complicated version of this commercial machine, right, and

0:11:54.440 --> 0:11:58.400
<v Speaker 1>they even evolved during the course of World War Two somewhat. Now,

0:11:58.600 --> 0:12:00.440
<v Speaker 1>if you want to know what the basic sheen is,

0:12:00.440 --> 0:12:05.040
<v Speaker 1>you have to imagine imagine a disk around wheel, all right,

0:12:05.120 --> 0:12:07.520
<v Speaker 1>and it's thick, It's about maybe half an inch thick,

0:12:08.160 --> 0:12:12.720
<v Speaker 1>and on either side of the wheel are contacts electrical

0:12:12.800 --> 0:12:17.160
<v Speaker 1>context that an electrical UH current can pass through. Along

0:12:17.200 --> 0:12:20.240
<v Speaker 1>the outer edge of the wheel, where if it were

0:12:20.280 --> 0:12:22.199
<v Speaker 1>a tire, this is the part that we make contact

0:12:22.240 --> 0:12:25.600
<v Speaker 1>with the ground. Along that outer edge are letters that

0:12:25.640 --> 0:12:29.000
<v Speaker 1>represent positions. Now you have three of these in a

0:12:29.080 --> 0:12:32.640
<v Speaker 1>basic Enigma machine, all right, and you the way you

0:12:32.679 --> 0:12:36.280
<v Speaker 1>set these, how you set them determines the pathway the

0:12:36.320 --> 0:12:39.640
<v Speaker 1>electricity takes when it comes in on one side and

0:12:39.720 --> 0:12:44.319
<v Speaker 1>goes out the other. Now, uh, you can change the

0:12:44.800 --> 0:12:48.080
<v Speaker 1>orientation of these reels in multiple ways, so that makes

0:12:48.120 --> 0:12:51.559
<v Speaker 1>it very complex. So this pathway could take lots of

0:12:51.559 --> 0:12:55.400
<v Speaker 1>little criss cross the ways. And what it boils down

0:12:55.400 --> 0:12:58.839
<v Speaker 1>to is the typewriter part with all the keys. When

0:12:58.880 --> 0:13:02.200
<v Speaker 1>you press a letter, it sends an electric signal into

0:13:02.360 --> 0:13:06.000
<v Speaker 1>the rotors. It goes through this complicated pathway that's determined

0:13:06.040 --> 0:13:08.880
<v Speaker 1>by the orientation of those rotors. When it comes out

0:13:08.920 --> 0:13:11.719
<v Speaker 1>the other side, it lights up a light bulb representing

0:13:11.800 --> 0:13:14.719
<v Speaker 1>a different letter when you So when you press the

0:13:14.800 --> 0:13:19.000
<v Speaker 1>letter A, perhaps the letter Q yes. And so it

0:13:19.040 --> 0:13:22.440
<v Speaker 1>takes two people to do this. Someone has the normal message,

0:13:22.480 --> 0:13:24.719
<v Speaker 1>the message that is supposed to be encoded, and they

0:13:24.760 --> 0:13:27.440
<v Speaker 1>press a key. There's a second person who watches the

0:13:27.520 --> 0:13:31.240
<v Speaker 1>light bulbs and writes down which letter lights up. And

0:13:31.480 --> 0:13:34.600
<v Speaker 1>after you press that A, the rotor, the first rotor

0:13:34.679 --> 0:13:37.920
<v Speaker 1>on the left rotates one position. So that means the

0:13:37.960 --> 0:13:41.640
<v Speaker 1>pathways for the that electric current to follow through have

0:13:41.880 --> 0:13:44.160
<v Speaker 1>changed from the first letter to the second. That's right.

0:13:44.160 --> 0:13:46.600
<v Speaker 1>So if the first two letters were A A for

0:13:46.640 --> 0:13:49.719
<v Speaker 1>some reason, and you pressed A and the Q lit up,

0:13:50.000 --> 0:13:53.600
<v Speaker 1>the second time you press A, perhaps the M lights up,

0:13:54.080 --> 0:13:56.360
<v Speaker 1>and every time after that's gonna light up differently. So

0:13:56.400 --> 0:13:59.640
<v Speaker 1>you already have so many possibilities just from that simple

0:13:59.720 --> 0:14:01.600
<v Speaker 1>disc option. But there's a way to make it even

0:14:01.600 --> 0:14:04.160
<v Speaker 1>more complicated, right there. There are two things that make

0:14:04.240 --> 0:14:06.679
<v Speaker 1>this even more complex. One is that once you go

0:14:06.760 --> 0:14:10.840
<v Speaker 1>through a certain number of of moves with that first rotor,

0:14:11.000 --> 0:14:14.079
<v Speaker 1>the second rotor can rotate, which means you've just added

0:14:14.080 --> 0:14:17.760
<v Speaker 1>a whole new set of variables. And with the German

0:14:17.840 --> 0:14:20.600
<v Speaker 1>Navy they had four rotors in their Enigma machines, which

0:14:20.640 --> 0:14:23.080
<v Speaker 1>means that once the third one would rotate, it just

0:14:23.120 --> 0:14:26.040
<v Speaker 1>made it even more complex. And this allows you to

0:14:26.080 --> 0:14:29.240
<v Speaker 1>have a key that does not repeat. It does mean

0:14:29.280 --> 0:14:31.880
<v Speaker 1>that whoever has the recipient, whoever the recipient is, they

0:14:31.880 --> 0:14:33.960
<v Speaker 1>have to have a machine set up the exact same

0:14:34.040 --> 0:14:36.640
<v Speaker 1>way that your machine was set up. Now, the other

0:14:36.680 --> 0:14:41.200
<v Speaker 1>thing that made this complicated was they had plug boards,

0:14:41.240 --> 0:14:44.280
<v Speaker 1>so unfair really, the plug boards, and what the plug

0:14:44.320 --> 0:14:46.800
<v Speaker 1>boards did was you were you would attach a cable

0:14:47.720 --> 0:14:52.440
<v Speaker 1>that would swap the input of a certain key with

0:14:52.480 --> 0:14:55.920
<v Speaker 1>another key. So let's stick with A. Let's say that

0:14:55.960 --> 0:14:58.240
<v Speaker 1>you have a plug in the A and a plug

0:14:58.280 --> 0:15:00.560
<v Speaker 1>in the H, which means every time you press A,

0:15:01.040 --> 0:15:05.320
<v Speaker 1>it's as if you had pressed H on an unaltered machine.

0:15:06.040 --> 0:15:09.160
<v Speaker 1>So that makes it even more complex. And the plugboards

0:15:09.160 --> 0:15:11.440
<v Speaker 1>were added a little later. That was an evolution of

0:15:11.480 --> 0:15:15.480
<v Speaker 1>the Enigma machine. And the Germans were so confident that

0:15:15.600 --> 0:15:19.560
<v Speaker 1>this machine was uncrackable that they never ever worried about

0:15:19.560 --> 0:15:24.760
<v Speaker 1>anyone intercepting their messages because those ciphered messages would be

0:15:24.960 --> 0:15:27.840
<v Speaker 1>impossible to decipher. They were a little too confident, though,

0:15:27.880 --> 0:15:30.760
<v Speaker 1>because there were a few problems with the whole thing,

0:15:31.360 --> 0:15:35.080
<v Speaker 1>one being that the machine couldn't encode a letter as itself.

0:15:35.120 --> 0:15:38.160
<v Speaker 1>So you've been using the example A A could never

0:15:38.240 --> 0:15:41.680
<v Speaker 1>be A no matter what combination of rotors you were using,

0:15:41.680 --> 0:15:44.840
<v Speaker 1>no matter how many cables were involved, A just couldn't

0:15:44.840 --> 0:15:46.520
<v Speaker 1>be A. That's a pretty big clue. I mean, it

0:15:46.560 --> 0:15:50.800
<v Speaker 1>doesn't sound like it reduces your your options that much,

0:15:50.880 --> 0:15:52.720
<v Speaker 1>but it really does if you're thinking about it in

0:15:52.800 --> 0:15:55.360
<v Speaker 1>terms of probability. Right, Yes, that's that was one of

0:15:55.360 --> 0:15:58.280
<v Speaker 1>the things Touring jumped on right away was he said, well,

0:15:58.440 --> 0:16:02.200
<v Speaker 1>if this machine cannot in code a letter as itself,

0:16:02.440 --> 0:16:05.640
<v Speaker 1>that removes one option out, and by removing one option

0:16:05.640 --> 0:16:09.280
<v Speaker 1>you have given us a foothold. That was definitely a weakness.

0:16:09.440 --> 0:16:12.240
<v Speaker 1>Another was that in order to make this work again,

0:16:12.280 --> 0:16:14.760
<v Speaker 1>you had to have two machines and you had to

0:16:14.760 --> 0:16:17.440
<v Speaker 1>have them both set up the same way, which meant

0:16:17.440 --> 0:16:19.960
<v Speaker 1>if someone were able to get hold of a machine

0:16:20.000 --> 0:16:24.040
<v Speaker 1>and the codebook so they you could see which which

0:16:24.080 --> 0:16:26.720
<v Speaker 1>set up was needed for any particular day. You know,

0:16:26.840 --> 0:16:29.600
<v Speaker 1>everyone had to know how to set their machine up

0:16:29.600 --> 0:16:33.800
<v Speaker 1>once they received the message, then they could intercept a

0:16:33.880 --> 0:16:37.720
<v Speaker 1>message and then interpret how to decipher it. Um, you

0:16:37.840 --> 0:16:40.000
<v Speaker 1>just had to know the day the message had been sent.

0:16:40.120 --> 0:16:41.680
<v Speaker 1>You had to know the day the message was sent,

0:16:41.760 --> 0:16:43.880
<v Speaker 1>so and you had to have a corresponding codebook that

0:16:43.920 --> 0:16:46.080
<v Speaker 1>would tell you the right setting for that day. But

0:16:46.160 --> 0:16:49.560
<v Speaker 1>even without that, once they started learning how the actual

0:16:49.760 --> 0:16:53.200
<v Speaker 1>machine worked, they were able to start thinking, how can

0:16:53.240 --> 0:16:57.400
<v Speaker 1>we simulate this by building something of our own that

0:16:57.520 --> 0:17:00.360
<v Speaker 1>can take this information and perhaps decide of it. So

0:17:00.360 --> 0:17:03.480
<v Speaker 1>if we intercept a message, we can if if even

0:17:03.520 --> 0:17:06.200
<v Speaker 1>if we don't know what the original settings were, perhaps

0:17:06.240 --> 0:17:09.960
<v Speaker 1>we'll be able to create something that can run enough

0:17:10.040 --> 0:17:13.400
<v Speaker 1>simulations through where we can crack the code. And Polish

0:17:13.400 --> 0:17:17.919
<v Speaker 1>mathematicians got a toe hold in this by intercepting an

0:17:18.080 --> 0:17:20.840
<v Speaker 1>Enigma machine, so they could see a little bit what

0:17:20.840 --> 0:17:22.960
<v Speaker 1>what they were dealing with and what kind of machine

0:17:22.960 --> 0:17:26.680
<v Speaker 1>would need to be created to possibly break this code. Yes,

0:17:26.760 --> 0:17:29.840
<v Speaker 1>and they ended up sharing that information with Bletchley Park,

0:17:29.960 --> 0:17:33.680
<v Speaker 1>which a famous famous institution there during World War Two.

0:17:33.720 --> 0:17:37.679
<v Speaker 1>That was that was codebreaker central for the British a

0:17:37.760 --> 0:17:40.320
<v Speaker 1>manor house, and I should take this opportunity to I

0:17:40.320 --> 0:17:42.520
<v Speaker 1>think one time we said it was in London. It's

0:17:42.520 --> 0:17:44.800
<v Speaker 1>outside of London. That was the whole point, because it

0:17:44.920 --> 0:17:48.160
<v Speaker 1>was more secure being away from the city. But yeah,

0:17:48.160 --> 0:17:51.560
<v Speaker 1>with this information that the Polish mathematicians had with their

0:17:51.600 --> 0:17:55.920
<v Speaker 1>intercepted Enigma, the teams at Bletchley Park started working on

0:17:56.880 --> 0:18:01.840
<v Speaker 1>building these early computers called bombs to a eventually simulate

0:18:02.119 --> 0:18:04.960
<v Speaker 1>the Enigma machine and figure out how it worked and

0:18:05.000 --> 0:18:06.680
<v Speaker 1>figure out how to break it. But what I think

0:18:06.800 --> 0:18:09.159
<v Speaker 1>is interesting is that this was I was talking to

0:18:09.200 --> 0:18:10.800
<v Speaker 1>you about this earlier, and it's kind of hard for

0:18:10.840 --> 0:18:13.199
<v Speaker 1>me to wrap my mind around. But they're working by

0:18:13.240 --> 0:18:16.679
<v Speaker 1>process of elimination. Rather than like, Okay, what was it

0:18:16.800 --> 0:18:18.800
<v Speaker 1>set on? It's more what was it? How was it

0:18:18.880 --> 0:18:23.639
<v Speaker 1>not set? Yes? Yeah, By eliminating all the potential factors,

0:18:23.720 --> 0:18:28.040
<v Speaker 1>they narrow it down to the one that it actually was. Uh.

0:18:28.240 --> 0:18:30.800
<v Speaker 1>It really reminds me of quantum computing. Actually, I'm not

0:18:30.840 --> 0:18:32.800
<v Speaker 1>going to go into it, don't get there. But but

0:18:32.840 --> 0:18:36.200
<v Speaker 1>I'm just saying a similar thing. You're eliminating all the

0:18:36.480 --> 0:18:40.280
<v Speaker 1>all of the possibilities to get down to the one reality.

0:18:40.359 --> 0:18:45.440
<v Speaker 1>And it is pretty amazing. The bombas that the Polish

0:18:45.480 --> 0:18:48.879
<v Speaker 1>mathematicians had created ended up informing the British when they

0:18:48.920 --> 0:18:52.440
<v Speaker 1>started creating the the bumba b O m b E.

0:18:53.000 --> 0:18:55.600
<v Speaker 1>I always like to say the bum and uh and

0:18:55.720 --> 0:18:59.760
<v Speaker 1>yeah that was that was a huge, huge jump in

0:19:00.000 --> 0:19:04.640
<v Speaker 1>of crypto cryptanalysis and just the British war effort in general.

0:19:05.080 --> 0:19:08.040
<v Speaker 1>And one thing about all of these these codes and

0:19:08.080 --> 0:19:10.840
<v Speaker 1>decoding them is there's so many different names. There's the

0:19:10.920 --> 0:19:14.159
<v Speaker 1>name of the machine, there's the name that the opposing

0:19:14.200 --> 0:19:17.280
<v Speaker 1>force usually calls the code, and then the name of

0:19:17.359 --> 0:19:21.359
<v Speaker 1>the machine that is able to decode it. But in

0:19:21.359 --> 0:19:25.480
<v Speaker 1>this case, the Allied efforts to decode the German messages

0:19:25.640 --> 0:19:28.840
<v Speaker 1>was known as Ultra. Yeah, it was known as Ultra,

0:19:28.960 --> 0:19:32.200
<v Speaker 1>but you never said it ever, Ultra. I just didn't

0:19:32.200 --> 0:19:35.560
<v Speaker 1>say anything at Fletchley Park, like it's all done through

0:19:35.600 --> 0:19:40.640
<v Speaker 1>semaphoreign mime. Uh No. Ultra was such a secret term

0:19:40.800 --> 0:19:43.480
<v Speaker 1>that you were not supposed to utter it to other people.

0:19:43.920 --> 0:19:47.080
<v Speaker 1>Ultra was just a general term that referred to intercepted

0:19:47.080 --> 0:19:52.119
<v Speaker 1>and deciphered messages. And because it was such secret information,

0:19:52.600 --> 0:19:55.920
<v Speaker 1>you could not you could not reveal that to anyone

0:19:56.000 --> 0:19:58.880
<v Speaker 1>who was not already classified to know it so much

0:19:58.920 --> 0:20:02.280
<v Speaker 1>so that there were people who lost their jobs, who

0:20:02.280 --> 0:20:06.919
<v Speaker 1>were court martialed because they refused to deliver sources of

0:20:07.000 --> 0:20:09.840
<v Speaker 1>information because it fell under the umbrella of ultra. And

0:20:09.920 --> 0:20:12.320
<v Speaker 1>so there are people who are discredited during the war

0:20:12.840 --> 0:20:15.520
<v Speaker 1>because they were maintaining this level of secrecy, which is

0:20:15.520 --> 0:20:20.720
<v Speaker 1>pretty phenomenal, and they had a huge burden, which is

0:20:20.880 --> 0:20:25.760
<v Speaker 1>the flip side to cryptography. If you've intercepted a message

0:20:25.760 --> 0:20:28.359
<v Speaker 1>and you've successfully deciphered it, and you now know what

0:20:28.520 --> 0:20:31.879
<v Speaker 1>that information is, how do you act on that? Because

0:20:31.920 --> 0:20:34.040
<v Speaker 1>if you act on it in a way that reveals

0:20:34.040 --> 0:20:37.520
<v Speaker 1>to the enemy that you have understood what their messages are,

0:20:37.880 --> 0:20:41.000
<v Speaker 1>they are going to take efforts to change the way

0:20:41.000 --> 0:20:43.359
<v Speaker 1>that they are encoding things, thus putting you back to

0:20:43.480 --> 0:20:46.040
<v Speaker 1>square one. As long as your enemy feels that their

0:20:46.080 --> 0:20:50.280
<v Speaker 1>code is unbreakable, you're in a great position because they're

0:20:50.320 --> 0:20:53.320
<v Speaker 1>not going to take any more precautions with it. Otherwise

0:20:53.359 --> 0:20:56.000
<v Speaker 1>they can just develop a new machine, developed a more

0:20:56.040 --> 0:20:58.600
<v Speaker 1>difficult code. And yeah, like you said, you're back at

0:20:58.600 --> 0:21:02.920
<v Speaker 1>square one, then yes, and it is. I mean, it's

0:21:02.960 --> 0:21:05.199
<v Speaker 1>just it's it's hard to think about because you know

0:21:05.280 --> 0:21:08.160
<v Speaker 1>that a lot of these messages had life or death

0:21:08.200 --> 0:21:12.480
<v Speaker 1>consequences exactly, and they had to take very careful consideration

0:21:12.520 --> 0:21:15.080
<v Speaker 1>of how to act on it so that they could

0:21:15.520 --> 0:21:19.240
<v Speaker 1>preserve as many lives as possible without tipping their hand.

0:21:19.480 --> 0:21:21.840
<v Speaker 1>Was it information that could have been procured from some

0:21:22.000 --> 0:21:25.000
<v Speaker 1>other sources aside from breaking the code or how important

0:21:25.160 --> 0:21:31.240
<v Speaker 1>was it? Fortunately for the Allies, the Germans were extremely

0:21:31.320 --> 0:21:35.000
<v Speaker 1>confident that the Enigma code was unbreakable. And I think

0:21:35.600 --> 0:21:37.879
<v Speaker 1>the only way that they would have I think, I

0:21:37.920 --> 0:21:41.439
<v Speaker 1>think what their normal routine was the Germans this is

0:21:42.119 --> 0:21:44.840
<v Speaker 1>would be that if they felt that the code was endangered,

0:21:44.840 --> 0:21:47.280
<v Speaker 1>they would issue new codebooks and they would have a

0:21:47.280 --> 0:21:51.440
<v Speaker 1>new set of codebooks go out to the field rather

0:21:51.520 --> 0:21:54.639
<v Speaker 1>than scrap the system and start with something new, so

0:21:54.680 --> 0:21:56.880
<v Speaker 1>they'd stick with the system. They would just say, oh, well,

0:21:56.880 --> 0:22:00.600
<v Speaker 1>what's what is at risk? Here are the physical codebooks

0:22:00.600 --> 0:22:03.320
<v Speaker 1>that tell people what settings they need to have the

0:22:03.400 --> 0:22:05.760
<v Speaker 1>Enigma machine on. And I didn't really talk about but

0:22:05.760 --> 0:22:09.000
<v Speaker 1>the recipient of the message. To to de cipher a

0:22:09.040 --> 0:22:13.680
<v Speaker 1>message from the the coded one, you would give the

0:22:13.680 --> 0:22:16.600
<v Speaker 1>the ciphered message to a typist who would have their

0:22:16.600 --> 0:22:18.680
<v Speaker 1>own Enigma machines set up just like the first one,

0:22:19.440 --> 0:22:22.320
<v Speaker 1>they pressed the first letter, so if that A was

0:22:22.359 --> 0:22:24.560
<v Speaker 1>a QUE, they would press Q and the the A

0:22:24.720 --> 0:22:26.960
<v Speaker 1>light bulb lights up and so then you would have

0:22:26.960 --> 0:22:30.879
<v Speaker 1>a second person taking down the flat text message exactly. UM.

0:22:30.920 --> 0:22:34.320
<v Speaker 1>And I kind of was interested that the secrecy for

0:22:34.359 --> 0:22:37.520
<v Speaker 1>all of this really extended beyond the war to the

0:22:37.520 --> 0:22:41.359
<v Speaker 1>the BOMBA machines were all destroyed on Churchill's orders. After

0:22:41.440 --> 0:22:43.600
<v Speaker 1>the war. I read one account of one of the

0:22:43.640 --> 0:22:47.080
<v Speaker 1>women who had worked on the machines at Bletchley Park

0:22:47.160 --> 0:22:49.879
<v Speaker 1>and talking about how her crew just happily destroyed them

0:22:49.920 --> 0:22:53.959
<v Speaker 1>because they were so temperamental. They were just glad to

0:22:54.240 --> 0:22:57.800
<v Speaker 1>see them go. That's an unusual story either. There are

0:22:57.800 --> 0:23:02.840
<v Speaker 1>a lot of stories about destroy void cryptography machines because

0:23:02.920 --> 0:23:05.960
<v Speaker 1>it was just considered to be too dangerous to let

0:23:06.000 --> 0:23:10.160
<v Speaker 1>that information out further technology that could still be useful.

0:23:10.720 --> 0:23:13.679
<v Speaker 1>Although today, of course, most of these machines have been rebuilt.

0:23:13.800 --> 0:23:15.640
<v Speaker 1>You can see a lot of them if you visit

0:23:15.680 --> 0:23:18.080
<v Speaker 1>Bletchley Park, which I think is cool that they've They've

0:23:18.080 --> 0:23:20.200
<v Speaker 1>gone to the trouble of illustrating these because if you

0:23:20.240 --> 0:23:22.320
<v Speaker 1>watch a video of one, it's a little easier too

0:23:22.880 --> 0:23:26.399
<v Speaker 1>to comprehend than if you're just trying to read about

0:23:26.440 --> 0:23:29.480
<v Speaker 1>it or hearing about it too, to see exactly how

0:23:29.920 --> 0:23:32.240
<v Speaker 1>they were right. And there's some software out there as

0:23:32.240 --> 0:23:35.960
<v Speaker 1>well that simulates a lot of these different machines so

0:23:36.000 --> 0:23:39.280
<v Speaker 1>that you could type in a message and it would

0:23:39.280 --> 0:23:41.919
<v Speaker 1>come out as a ciphered message. And again you have

0:23:42.040 --> 0:23:44.480
<v Speaker 1>a friend who has that same software running, and you

0:23:44.480 --> 0:23:47.120
<v Speaker 1>tell them, all right, set your software to this setting

0:23:47.280 --> 0:23:49.200
<v Speaker 1>and run this message through and see what you get.

0:23:49.600 --> 0:23:52.520
<v Speaker 1>And it might say, you know, you are a poopy head.

0:23:53.480 --> 0:23:56.639
<v Speaker 1>It's all the messages I get from Chris all the time.

0:23:57.000 --> 0:24:00.199
<v Speaker 1>It's really worth worth coding. Yeah, it takes a lot

0:24:00.240 --> 0:24:04.240
<v Speaker 1>of effort to get that across. Another thing, though, is

0:24:04.440 --> 0:24:07.000
<v Speaker 1>Enigma kind of gets all the glory. I'd say, you know,

0:24:07.080 --> 0:24:10.080
<v Speaker 1>it's the only with if we were saying earlier that

0:24:10.119 --> 0:24:12.440
<v Speaker 1>it's probably when most people are familiar with, and it

0:24:12.520 --> 0:24:15.560
<v Speaker 1>might also be the only German code that people are

0:24:15.600 --> 0:24:18.600
<v Speaker 1>familiar with. Sure, and it's not the only German code

0:24:18.600 --> 0:24:22.159
<v Speaker 1>by a long shot. You wanted to speak specifically to

0:24:22.200 --> 0:24:26.560
<v Speaker 1>the Lawrenz machines, which the Lawrence machine was interesting. It

0:24:26.640 --> 0:24:29.359
<v Speaker 1>was a steam powered machine, so a little bit different

0:24:29.400 --> 0:24:32.119
<v Speaker 1>and also the kind of old school little steam punky,

0:24:32.280 --> 0:24:35.159
<v Speaker 1>little steam punky. Uh. It actually would send a message

0:24:35.600 --> 0:24:39.960
<v Speaker 1>over telephone wire, over a telegraph wire, um, and you

0:24:39.960 --> 0:24:43.399
<v Speaker 1>would have two machines set up where you would type

0:24:43.400 --> 0:24:46.959
<v Speaker 1>in a message onto one machine. It encodes it using

0:24:47.160 --> 0:24:51.919
<v Speaker 1>an ex or algorithm. And I to to explain that

0:24:51.920 --> 0:24:54.359
<v Speaker 1>would probably take an entire podcast on its own, but

0:24:54.440 --> 0:24:56.919
<v Speaker 1>just just to say that each letter is a symbol

0:24:57.320 --> 0:25:03.399
<v Speaker 1>assigned a certain binary value, and then there's a key

0:25:03.440 --> 0:25:06.520
<v Speaker 1>that also has a binary value. You add those two

0:25:06.760 --> 0:25:09.919
<v Speaker 1>values together, it creates a third value that becomes the

0:25:09.960 --> 0:25:13.119
<v Speaker 1>ciphered text. So as long as the other machine again

0:25:13.160 --> 0:25:16.320
<v Speaker 1>has the right key, uh, then you can decipher it.

0:25:16.440 --> 0:25:20.119
<v Speaker 1>And again the Germans were very confident about this. They thought, well,

0:25:20.359 --> 0:25:23.400
<v Speaker 1>we've got this. The key is is this this role

0:25:23.440 --> 0:25:27.359
<v Speaker 1>of tape. Essentially that both sides, both the sender and

0:25:27.400 --> 0:25:31.159
<v Speaker 1>the recipient, they have identical strips of tape that have

0:25:31.320 --> 0:25:35.040
<v Speaker 1>these values in it. The h the coded message gets

0:25:35.040 --> 0:25:37.679
<v Speaker 1>sent across the wire, they run the tape through the

0:25:37.760 --> 0:25:40.520
<v Speaker 1>receiving machine and then they get the plain text information.

0:25:41.200 --> 0:25:44.480
<v Speaker 1>Thinking that no one in between would ever be able

0:25:44.720 --> 0:25:47.760
<v Speaker 1>to crack that code, so there wasn't a whole lot

0:25:47.800 --> 0:25:51.240
<v Speaker 1>of fear about intercepting those messages either on the side

0:25:51.280 --> 0:25:53.760
<v Speaker 1>of the Germans, but there should have been. There should

0:25:53.760 --> 0:25:56.119
<v Speaker 1>have been, I mean Lorenz who have used for just

0:25:56.200 --> 0:25:59.159
<v Speaker 1>the most important information. It was reserved for high command

0:25:59.200 --> 0:26:02.280
<v Speaker 1>for Hitler. Kind of ironic if you think about how

0:26:02.320 --> 0:26:05.520
<v Speaker 1>they were so confident with Enigma that they wanted this

0:26:05.640 --> 0:26:10.160
<v Speaker 1>extra code, but it was eventually broken by the machine.

0:26:10.240 --> 0:26:13.200
<v Speaker 1>Colossus and um Letzley Park had a quote, and I

0:26:13.240 --> 0:26:14.960
<v Speaker 1>kind of wanted to get your opinion on this. They

0:26:15.040 --> 0:26:20.120
<v Speaker 1>called it the world's first practical electronic digital information processing machine,

0:26:20.640 --> 0:26:25.040
<v Speaker 1>a forerunner of today's computers. Yes, it was the first

0:26:25.200 --> 0:26:28.080
<v Speaker 1>of that nature. Uh, you can look at any act

0:26:28.160 --> 0:26:30.640
<v Speaker 1>which was not yet built. It was not finished until

0:26:32.359 --> 0:26:36.879
<v Speaker 1>um and all the other preceding computers were electro mechanical,

0:26:37.240 --> 0:26:40.240
<v Speaker 1>meaning that there were actually gears in parts that moved,

0:26:40.560 --> 0:26:44.959
<v Speaker 1>not just electronic circuits created by either wires you know

0:26:45.040 --> 0:26:47.280
<v Speaker 1>today we think of microchips. Back in the day, we're

0:26:47.280 --> 0:26:51.320
<v Speaker 1>talking about actual physical wires running to and fro and everywhere.

0:26:51.480 --> 0:26:53.800
<v Speaker 1>That's why these machines tended to be the size of

0:26:54.920 --> 0:26:58.199
<v Speaker 1>fairly sized room. Colossus is an apt term. Yeah, there

0:26:58.240 --> 0:27:01.639
<v Speaker 1>were there were ten of them and they were huge. Um, yeah,

0:27:02.440 --> 0:27:06.320
<v Speaker 1>that's perfectly accurate. It is definitely a predecessor to today's computer.

0:27:06.359 --> 0:27:09.320
<v Speaker 1>And of course, just as you would imagine today's computer,

0:27:09.359 --> 0:27:11.960
<v Speaker 1>the computer that's on your desktop, perhaps the computer that

0:27:12.000 --> 0:27:15.240
<v Speaker 1>you have in a pocket or in a bag near

0:27:15.320 --> 0:27:19.119
<v Speaker 1>you right now, far more powerful than Colossus. And I

0:27:19.160 --> 0:27:21.560
<v Speaker 1>watched the video of Colossus, you know, recommending these two

0:27:21.560 --> 0:27:23.440
<v Speaker 1>folks to to check them out and kind of get

0:27:23.440 --> 0:27:25.640
<v Speaker 1>a better feel for how these things look and how

0:27:25.640 --> 0:27:28.480
<v Speaker 1>they work. It reminded me almost of a workout machine,

0:27:28.560 --> 0:27:33.040
<v Speaker 1>partly because of the tapes all wrapped around the little reels,

0:27:33.119 --> 0:27:35.800
<v Speaker 1>and that combined with a wall of electronics, it really

0:27:35.840 --> 0:27:39.840
<v Speaker 1>does take up an entire room. So that's amazing to

0:27:39.840 --> 0:27:43.840
<v Speaker 1>to think that that is a computer predecessor. Yep, yep.

0:27:43.960 --> 0:27:48.080
<v Speaker 1>And again it was there to simulate these Lorenz machines

0:27:48.240 --> 0:27:51.840
<v Speaker 1>and try and crack what those codes were, and it

0:27:51.920 --> 0:27:57.119
<v Speaker 1>was a phenomenal achievement as far as technology is concerned. Okay,

0:27:57.119 --> 0:28:00.640
<v Speaker 1>so we've probably discussed Germany pretty thorough lead by now,

0:28:01.760 --> 0:28:06.160
<v Speaker 1>so we're gonna move over to Japan. And one thing

0:28:06.240 --> 0:28:10.520
<v Speaker 1>that I found really fascinating was that Japanese communications had

0:28:10.520 --> 0:28:14.439
<v Speaker 1>been monitored by the United States long long before World

0:28:14.440 --> 0:28:17.240
<v Speaker 1>War Two began, right, more than a decade before, and

0:28:17.359 --> 0:28:20.040
<v Speaker 1>Japan was not aware of that for quite a long

0:28:20.080 --> 0:28:22.800
<v Speaker 1>time too, But that that tends to be the best way.

0:28:22.920 --> 0:28:26.800
<v Speaker 1>That's usually how it happens, if you're doing everything correctly,

0:28:26.840 --> 0:28:29.040
<v Speaker 1>if you're doing things how you should. So, yeah, the

0:28:29.080 --> 0:28:34.399
<v Speaker 1>American said started screening Japanese telegrams between diplomats in November

0:28:34.680 --> 0:28:38.640
<v Speaker 1>nineteen one. And these were really simple messages, so nothing

0:28:38.680 --> 0:28:40.560
<v Speaker 1>like what we've been talking about with the Enigma. They

0:28:40.560 --> 0:28:44.360
<v Speaker 1>were easy to break, and they gave the Cipher Bureau,

0:28:44.440 --> 0:28:48.200
<v Speaker 1>which was the name of this UM code breaking organization

0:28:48.240 --> 0:28:52.080
<v Speaker 1>in the US at the time and its director, Herbert Yardley,

0:28:52.200 --> 0:28:56.520
<v Speaker 1>access to a lot of useful information. So it's diplomatic information,

0:28:56.640 --> 0:29:00.680
<v Speaker 1>it's not military, but still gives you some helpful stuff

0:29:00.720 --> 0:29:04.400
<v Speaker 1>if you're negotiating treaties, you know, that sort of thing.

0:29:05.880 --> 0:29:10.240
<v Speaker 1>Definitely a little inside peak, some insider trading on a

0:29:10.320 --> 0:29:13.960
<v Speaker 1>grand scale, that's what this is. But by the late

0:29:14.040 --> 0:29:18.360
<v Speaker 1>nineteen twenties, this uh to do this, they relied on

0:29:18.440 --> 0:29:22.239
<v Speaker 1>domestic cable companies in information, which is something kind of

0:29:22.240 --> 0:29:25.760
<v Speaker 1>relevant to this. But by the late nineteen twenties, use

0:29:25.840 --> 0:29:29.600
<v Speaker 1>of that information and plus monitoring of airwaves started to

0:29:29.640 --> 0:29:34.360
<v Speaker 1>become kind of distasteful, frowned upon, and so eventually the

0:29:34.400 --> 0:29:39.720
<v Speaker 1>cipher Bureau dissolved and Yardley, out of work trying to

0:29:39.760 --> 0:29:42.680
<v Speaker 1>make some money during the Great Depression, decided to write

0:29:42.720 --> 0:29:46.040
<v Speaker 1>a book and write a series of articles for the

0:29:46.120 --> 0:29:50.960
<v Speaker 1>Saturday Evening Post on codes and code breaking. His experiences

0:29:51.080 --> 0:29:56.560
<v Speaker 1>experience monitoring the information coming out of Japan, and it

0:29:56.960 --> 0:30:00.800
<v Speaker 1>sets some shock waves going through the world that this

0:30:00.920 --> 0:30:04.640
<v Speaker 1>information was so easily available. This this kind of proves

0:30:04.720 --> 0:30:07.960
<v Speaker 1>why it's important to keep that secret parts secret because

0:30:08.080 --> 0:30:10.960
<v Speaker 1>once once it got out that this was very easy

0:30:11.040 --> 0:30:14.200
<v Speaker 1>for them to break the codes. The message that sends

0:30:14.320 --> 0:30:17.520
<v Speaker 1>is we need to look at how we are ciphering

0:30:17.520 --> 0:30:21.480
<v Speaker 1>our messages, how we're encoding things, and try to introduce

0:30:21.520 --> 0:30:26.520
<v Speaker 1>as much randomness as possible. And randomness is what makes

0:30:26.560 --> 0:30:29.160
<v Speaker 1>codes so difficult to break. You know, once you start

0:30:29.160 --> 0:30:32.680
<v Speaker 1>being able to detect patterns, it's game over because it's

0:30:32.680 --> 0:30:35.000
<v Speaker 1>just a matter of time before you can start, before

0:30:35.040 --> 0:30:37.680
<v Speaker 1>you have to before that code gets cracked. So you

0:30:37.720 --> 0:30:40.320
<v Speaker 1>want to avoid patterns as much as possible and have

0:30:40.360 --> 0:30:43.280
<v Speaker 1>as much randomness in there as possible. But here's the trick.

0:30:44.440 --> 0:30:49.680
<v Speaker 1>Random is hard. Computers are not truly good at producing

0:30:49.800 --> 0:30:53.840
<v Speaker 1>random numbers. They are pseudo random because they're still following

0:30:53.840 --> 0:30:58.120
<v Speaker 1>a set of rules in order to create random numbers.

0:30:58.520 --> 0:31:02.360
<v Speaker 1>And on top of that, there needs to be someone

0:31:02.400 --> 0:31:04.760
<v Speaker 1>else out there who has the same set of random

0:31:04.840 --> 0:31:07.120
<v Speaker 1>data so they can decode the message you send them.

0:31:07.440 --> 0:31:09.520
<v Speaker 1>So there's going to be at least one copy of

0:31:09.560 --> 0:31:13.600
<v Speaker 1>whatever random, quote unquote random message you create or random

0:31:13.680 --> 0:31:16.760
<v Speaker 1>key you create in order to cipher a message. But

0:31:16.880 --> 0:31:20.880
<v Speaker 1>that was what really got countries around the world thinking,

0:31:21.240 --> 0:31:24.880
<v Speaker 1>how can we create more of a random feel for

0:31:24.960 --> 0:31:29.920
<v Speaker 1>our encoding technology, the random Yeah, if we don't, then

0:31:30.040 --> 0:31:31.960
<v Speaker 1>our messages get cracked. We might as well just be

0:31:32.000 --> 0:31:34.480
<v Speaker 1>sending plain text. It would be a lot easier and

0:31:34.520 --> 0:31:37.160
<v Speaker 1>a lot faster. And so that did sort of lead

0:31:37.200 --> 0:31:42.280
<v Speaker 1>to a shift in adopting these more complex mechanical machines,

0:31:42.320 --> 0:31:44.400
<v Speaker 1>like we've talked about already with the Enigma, which was

0:31:44.440 --> 0:31:47.800
<v Speaker 1>from the twenties, adopting machines more like that rather than

0:31:47.920 --> 0:31:52.720
<v Speaker 1>these old style codes right right, And the Japanese chose

0:31:52.880 --> 0:31:57.120
<v Speaker 1>a slightly different approach. Their machines did not look like

0:31:57.200 --> 0:32:00.480
<v Speaker 1>the Enigma and did not. While they were able to

0:32:00.480 --> 0:32:03.800
<v Speaker 1>generate randomness in a very similar way that the Enigma

0:32:03.840 --> 0:32:07.560
<v Speaker 1>machine did, so the outcome was very similar, the actual

0:32:07.680 --> 0:32:13.200
<v Speaker 1>mechanics were different. To explain, you want to know how Okay,

0:32:13.200 --> 0:32:17.080
<v Speaker 1>So it's an electro magnetic device and it's called it's

0:32:17.120 --> 0:32:21.120
<v Speaker 1>a step switching device as opposed to rotors, but very

0:32:21.160 --> 0:32:25.320
<v Speaker 1>similar in that if you encode a character, there is

0:32:25.360 --> 0:32:30.040
<v Speaker 1>a step switch that moves the encoder one step further

0:32:30.200 --> 0:32:33.360
<v Speaker 1>so that the next key you press gets coded to

0:32:33.440 --> 0:32:34.880
<v Speaker 1>a different one than it would be if it had

0:32:34.880 --> 0:32:38.640
<v Speaker 1>been the first key. That sounds really complicated, but really again, well,

0:32:38.680 --> 0:32:41.440
<v Speaker 1>we'll stick with the a's and the a's right that

0:32:41.440 --> 0:32:43.880
<v Speaker 1>that you're coding two a's in a row. Obviously this

0:32:43.920 --> 0:32:46.600
<v Speaker 1>would not be the case with the Japanese typewriter. But

0:32:47.320 --> 0:32:50.120
<v Speaker 1>if you press the letter A, then the first step

0:32:50.280 --> 0:32:53.760
<v Speaker 1>would be to encode that to whatever the setting has it.

0:32:53.840 --> 0:32:56.680
<v Speaker 1>So we'll go with H and then the second that

0:32:56.680 --> 0:33:01.520
<v Speaker 1>that would then step up the code a step. You

0:33:01.560 --> 0:33:04.400
<v Speaker 1>press A again, it would then code to a different

0:33:04.480 --> 0:33:09.600
<v Speaker 1>letter so z and very much the same way as

0:33:09.600 --> 0:33:13.720
<v Speaker 1>the Enigma machine, but the actual parts didn't move the

0:33:13.760 --> 0:33:18.160
<v Speaker 1>same way. Whereas the Enigma had these rotors. The Japanese

0:33:18.160 --> 0:33:23.600
<v Speaker 1>typewriters used this this electromantic step system, and and they

0:33:23.600 --> 0:33:26.520
<v Speaker 1>had interesting code names they did. So. The first of

0:33:26.720 --> 0:33:30.920
<v Speaker 1>these electromagnetic code machines created by the Japanese was called

0:33:30.960 --> 0:33:34.480
<v Speaker 1>the cipher Machine Type A. It was known as red

0:33:34.640 --> 0:33:36.560
<v Speaker 1>to the U s, and the code it produced was

0:33:36.600 --> 0:33:39.840
<v Speaker 1>known as red um. That code was fully broken though

0:33:39.880 --> 0:33:43.719
<v Speaker 1>in nineteen seven, with a clue from one word the

0:33:43.800 --> 0:33:47.400
<v Speaker 1>Japanese word for and essentially was enough of a enough

0:33:47.440 --> 0:33:50.480
<v Speaker 1>of a hint for them to break code red. Yeah. Again,

0:33:50.520 --> 0:33:52.719
<v Speaker 1>it's one of those things where they're looking for repetition

0:33:52.760 --> 0:33:55.280
<v Speaker 1>and patterns, and if it's a word that's used a lot,

0:33:55.920 --> 0:33:59.040
<v Speaker 1>and if you're if you don't have enough steps there,

0:33:59.120 --> 0:34:03.920
<v Speaker 1>if you're key repeats fairly frequently, then you run the

0:34:04.040 --> 0:34:07.560
<v Speaker 1>danger of someone using frequency analysis on your message and

0:34:07.600 --> 0:34:09.480
<v Speaker 1>figuring out what it means. That was one of the

0:34:09.560 --> 0:34:11.400
<v Speaker 1>things that the Enigma was so good about was that

0:34:11.440 --> 0:34:16.160
<v Speaker 1>because there were so many possible combinations, that unless your

0:34:16.160 --> 0:34:21.919
<v Speaker 1>message was incredibly long and i'm talking novel length, then

0:34:22.080 --> 0:34:24.520
<v Speaker 1>you're not going to have to worry about the pattern

0:34:24.640 --> 0:34:27.399
<v Speaker 1>forming because you are not going to run out of

0:34:27.440 --> 0:34:31.239
<v Speaker 1>those variations. Well, and another problem too is that the

0:34:31.520 --> 0:34:36.000
<v Speaker 1>Japanese were sending several standard messages with their messages, so

0:34:36.200 --> 0:34:38.719
<v Speaker 1>well we should go back to So they did decipher

0:34:38.880 --> 0:34:42.439
<v Speaker 1>the code sent out by RED, and by that point,

0:34:42.440 --> 0:34:46.800
<v Speaker 1>though by night messages through RED announced that there was

0:34:46.840 --> 0:34:49.160
<v Speaker 1>another machine. That's probably a mistake too, to announce your

0:34:49.200 --> 0:34:53.960
<v Speaker 1>new machine through your old one that has been compromised.

0:34:54.040 --> 0:34:59.040
<v Speaker 1>And that new announcement was for the alphabetical typewriter, which

0:34:59.080 --> 0:35:02.000
<v Speaker 1>was codenamed Purple. That's probably the more famous of the two. Yes,

0:35:02.040 --> 0:35:05.799
<v Speaker 1>Purple is definitely more famous. And I read although from

0:35:05.800 --> 0:35:10.360
<v Speaker 1>a source that I consider questionable, so this could be apocryphal.

0:35:11.320 --> 0:35:14.040
<v Speaker 1>I want to proceed my my message with that that

0:35:14.120 --> 0:35:17.000
<v Speaker 1>the reason why I was called purple is because that was,

0:35:17.040 --> 0:35:20.160
<v Speaker 1>in fact the color of the binders that the United

0:35:20.200 --> 0:35:23.160
<v Speaker 1>States used to hold all the intercepted and deciphered messages.

0:35:23.840 --> 0:35:27.600
<v Speaker 1>A good story, yeah, I mean it seems legit. As

0:35:27.600 --> 0:35:30.399
<v Speaker 1>they say on the interwebs. I do have to say, well,

0:35:30.520 --> 0:35:33.919
<v Speaker 1>researching this though code read code Purple, I just kept

0:35:33.920 --> 0:35:38.319
<v Speaker 1>on getting a lot of information on air quality. Yeah,

0:35:38.719 --> 0:35:42.680
<v Speaker 1>but also very fitting for Atlanta. It is uh and

0:35:43.640 --> 0:35:47.000
<v Speaker 1>they the the United States was able to crack these

0:35:47.000 --> 0:35:51.520
<v Speaker 1>codes too. Um. The purple codes were not as sophisticated

0:35:51.560 --> 0:35:55.240
<v Speaker 1>as the Enigma machines were. Uh. And the United States

0:35:55.719 --> 0:35:59.399
<v Speaker 1>cracked them. And again, these are mostly diplomatic messages, they're

0:35:59.440 --> 0:36:02.880
<v Speaker 1>not military messages. But the United States is keeping tabs

0:36:02.880 --> 0:36:05.439
<v Speaker 1>on what's going on in the in the Pacific, and

0:36:05.719 --> 0:36:12.359
<v Speaker 1>they called their interception and deciphered messages. Uh. Magic, because

0:36:12.400 --> 0:36:14.960
<v Speaker 1>that's what it seems like when you're able to decode something.

0:36:15.000 --> 0:36:18.879
<v Speaker 1>I guess very tinker tailor soldier spy. Yes it is. Yes,

0:36:18.960 --> 0:36:21.680
<v Speaker 1>Gary Oldman would have had a lot of work during

0:36:21.760 --> 0:36:24.719
<v Speaker 1>this time, and it took him a while to decode it.

0:36:24.760 --> 0:36:26.640
<v Speaker 1>That we shouldn't make it sound like it was just

0:36:26.760 --> 0:36:30.239
<v Speaker 1>an easy tak No, it took quite some time. It

0:36:30.280 --> 0:36:32.240
<v Speaker 1>took more than a year a year and a half

0:36:32.600 --> 0:36:35.839
<v Speaker 1>of hard work to crack the code. But they were

0:36:35.920 --> 0:36:40.840
<v Speaker 1>able to figure that out. Um. And Uh, it's interesting

0:36:41.280 --> 0:36:45.960
<v Speaker 1>the person who discovered the correlation was someone that you

0:36:46.040 --> 0:36:49.560
<v Speaker 1>might not consider it first considering the time period. Right,

0:36:49.880 --> 0:36:52.920
<v Speaker 1>so we're in the middle of it was in September

0:36:52.960 --> 0:36:55.759
<v Speaker 1>n So World War two is is going on. The

0:36:55.800 --> 0:36:59.480
<v Speaker 1>Americans are not really they're just really monitoring at the moment.

0:37:00.080 --> 0:37:04.080
<v Speaker 1>The person who who discovered the correlation in a in

0:37:04.120 --> 0:37:06.279
<v Speaker 1>a couple of messages which was enough to allow us

0:37:06.280 --> 0:37:11.680
<v Speaker 1>to break the code, was Genevieve Grossian. So a woman

0:37:12.000 --> 0:37:15.359
<v Speaker 1>was the one who discovered the correlation. And again, it's

0:37:15.360 --> 0:37:18.480
<v Speaker 1>one of those things where we often overlook the people

0:37:18.520 --> 0:37:22.239
<v Speaker 1>who first make these these uh discoveries, because you know,

0:37:22.320 --> 0:37:25.200
<v Speaker 1>the big story about breaking the code is interesting, but

0:37:25.280 --> 0:37:27.879
<v Speaker 1>sometimes we lose sight of the people. And I thought, well,

0:37:27.920 --> 0:37:31.799
<v Speaker 1>that's someone that we should know about clearly, because this

0:37:31.840 --> 0:37:34.520
<v Speaker 1>is someone who was able to find the first stepping

0:37:34.560 --> 0:37:36.920
<v Speaker 1>stone that allowed us to crack the code. Alan Turing's

0:37:36.960 --> 0:37:41.080
<v Speaker 1>getting his moment. There's plenty to go around. Um, so

0:37:41.280 --> 0:37:44.000
<v Speaker 1>you know the timeline. By this point, you're probably thinking, well,

0:37:44.040 --> 0:37:50.640
<v Speaker 1>if Purple was cracked in ninety, um, what about Pearl Harbor?

0:37:50.719 --> 0:37:53.959
<v Speaker 1>How much was known? They were diplomatic messages, so there's

0:37:54.040 --> 0:37:58.760
<v Speaker 1>no evidence that they were receiving information about Pearl Harbor.

0:37:59.080 --> 0:38:02.359
<v Speaker 1>That doesn't mean though, there wasn't some pretty important information

0:38:02.880 --> 0:38:07.040
<v Speaker 1>that was gained from understanding Purple. Yeah, there was. There's

0:38:07.080 --> 0:38:11.320
<v Speaker 1>still some confusion and there are plenty of conspiracy theories

0:38:11.360 --> 0:38:14.560
<v Speaker 1>about how much information was gleaned from Purple that could

0:38:14.640 --> 0:38:18.600
<v Speaker 1>have prevented, could have at least prevented or at least

0:38:18.800 --> 0:38:23.640
<v Speaker 1>prepared everyone in Hawaii for this attack. And uh, there

0:38:23.760 --> 0:38:28.239
<v Speaker 1>was no specific message ever intercepted and decipher that had

0:38:28.280 --> 0:38:31.880
<v Speaker 1>anything to do with a specific attack on Pearl Harbor,

0:38:32.360 --> 0:38:36.080
<v Speaker 1>according to all official records. And again, conspiracy theorists might

0:38:36.160 --> 0:38:38.759
<v Speaker 1>disagree with that ben In here, maybe we have to

0:38:38.800 --> 0:38:41.360
<v Speaker 1>go with what history gives us, right, and what history

0:38:41.400 --> 0:38:45.360
<v Speaker 1>says is that there was no way of knowing directly

0:38:45.480 --> 0:38:48.600
<v Speaker 1>through the intercepted messages about the attack on Pearl Harbor.

0:38:49.320 --> 0:38:51.800
<v Speaker 1>History would have unfolded a very different way. I'm sure

0:38:52.200 --> 0:38:55.000
<v Speaker 1>had there been. What's ironic is that some of the

0:38:55.040 --> 0:38:58.719
<v Speaker 1>most important information that was gleaned from these messages was

0:38:58.760 --> 0:39:03.600
<v Speaker 1>about Germany rather than Japan. Ironic because of how how

0:39:03.640 --> 0:39:06.600
<v Speaker 1>proud they were of the Enigma. All this information was

0:39:06.640 --> 0:39:10.000
<v Speaker 1>really getting out through Purple anyway, that probably would have

0:39:10.040 --> 0:39:12.319
<v Speaker 1>made the Germans a little kind of upset. Yeah. The

0:39:12.400 --> 0:39:17.160
<v Speaker 1>Japanese ambassador to Berlin, a man named hiroshi Oshima. He

0:39:17.719 --> 0:39:21.040
<v Speaker 1>was pretty descriptive while talking about what was going on

0:39:21.239 --> 0:39:24.680
<v Speaker 1>in Germany and what the Nazi defenses were like and

0:39:24.719 --> 0:39:29.360
<v Speaker 1>all that information was being picked up through through magic um,

0:39:29.400 --> 0:39:32.920
<v Speaker 1>so a lot of information that ultimately helped prepare for

0:39:33.000 --> 0:39:35.760
<v Speaker 1>the D Day invasion. So Pearl Harbor is off the table,

0:39:35.840 --> 0:39:38.520
<v Speaker 1>possibly unless we're going to go conspiracy theory on it.

0:39:38.880 --> 0:39:43.840
<v Speaker 1>But d JA so still an important code to have broken. Yeah,

0:39:43.920 --> 0:39:47.319
<v Speaker 1>it's uh, it's amazing to me when you look at

0:39:47.840 --> 0:39:51.719
<v Speaker 1>some of the mistakes that were made, because often mistakes

0:39:51.719 --> 0:39:54.560
<v Speaker 1>are the only reason why certain codes were ever broken

0:39:54.600 --> 0:39:57.280
<v Speaker 1>in the first place. Either there were mistakes and procedure

0:39:57.600 --> 0:40:01.360
<v Speaker 1>where someone has set up a really secure system, but

0:40:01.440 --> 0:40:04.360
<v Speaker 1>the people part of the system isn't so secure. My

0:40:04.400 --> 0:40:08.080
<v Speaker 1>favorite example of that is somebody making a mistake in

0:40:08.239 --> 0:40:12.640
<v Speaker 1>the typing of the message and instead of resetting everything

0:40:13.000 --> 0:40:15.960
<v Speaker 1>so that the code is secure again, just typing out

0:40:15.960 --> 0:40:19.640
<v Speaker 1>a corrected message on the same setting, right, which makes

0:40:19.680 --> 0:40:23.040
<v Speaker 1>for just very slight differences between the two messages, right,

0:40:23.080 --> 0:40:25.960
<v Speaker 1>And that that was huge. That was an enormous help.

0:40:26.000 --> 0:40:29.239
<v Speaker 1>I mean, the protocol for that was if you were

0:40:29.280 --> 0:40:31.560
<v Speaker 1>to send a message and you made a mistake while

0:40:31.760 --> 0:40:34.680
<v Speaker 1>in ciphering it, that you were supposed to set it

0:40:34.719 --> 0:40:37.640
<v Speaker 1>to a new whatever machine was involved, you were supposed

0:40:37.640 --> 0:40:40.160
<v Speaker 1>to set to the next start over, start from scratch,

0:40:40.200 --> 0:40:42.600
<v Speaker 1>Start from scratch with a new setting, so that all

0:40:42.680 --> 0:40:45.120
<v Speaker 1>the message is going to be completely different because that

0:40:45.200 --> 0:40:48.560
<v Speaker 1>way the Allies don't know that it's the same message.

0:40:48.920 --> 0:40:51.880
<v Speaker 1>But by setting it back to the setting that was

0:40:51.920 --> 0:40:54.400
<v Speaker 1>for the first time you try to transmit it, that

0:40:54.480 --> 0:40:57.799
<v Speaker 1>means two copies of this message go out and that's

0:40:57.960 --> 0:41:01.239
<v Speaker 1>enough for the Allies to say, wait a minute, this

0:41:01.320 --> 0:41:04.560
<v Speaker 1>was in coomat. We can figure this out and we

0:41:04.560 --> 0:41:07.919
<v Speaker 1>can start working on what has gone wrong for them

0:41:08.000 --> 0:41:10.480
<v Speaker 1>and right for us. So human error is a is

0:41:10.480 --> 0:41:13.480
<v Speaker 1>a big part of these codes ultimately being cracked. It

0:41:13.520 --> 0:41:17.400
<v Speaker 1>seems ultimately yes, I would say that things everything from

0:41:17.520 --> 0:41:22.520
<v Speaker 1>using common salutations or a common prefix to whatever the

0:41:22.560 --> 0:41:28.200
<v Speaker 1>message is, that would often give the the analysts enough

0:41:28.239 --> 0:41:31.279
<v Speaker 1>information to work on to start cracking a code. Even

0:41:31.320 --> 0:41:34.600
<v Speaker 1>a weather report. The standards between a weather report the

0:41:34.680 --> 0:41:38.080
<v Speaker 1>numbers or directions of wind might be different, but it's

0:41:38.080 --> 0:41:40.239
<v Speaker 1>going to have a lot of the same vocabulary and

0:41:40.280 --> 0:41:43.840
<v Speaker 1>that weather report information. That's also a good point because

0:41:44.640 --> 0:41:47.040
<v Speaker 1>one thing that the British thought of while they were

0:41:47.239 --> 0:41:50.840
<v Speaker 1>trying to capture Enigma machines so they could get Enigma

0:41:50.880 --> 0:41:53.360
<v Speaker 1>machines and codebooks so that they be you know, the

0:41:53.480 --> 0:41:57.680
<v Speaker 1>Enigma machine was was fairly portable, fairly in the sense

0:41:57.719 --> 0:42:00.239
<v Speaker 1>that you could put one on a ship with much

0:42:01.120 --> 0:42:05.480
<v Speaker 1>The Lorens not portable. Uh, And the Purple machines were

0:42:05.520 --> 0:42:08.880
<v Speaker 1>not terribly portable either. In fact, uh, they just it

0:42:08.960 --> 0:42:11.200
<v Speaker 1>was once you once you built one, that's pretty much

0:42:11.200 --> 0:42:13.560
<v Speaker 1>where it stayed. But the Enigma machine was different. You

0:42:13.600 --> 0:42:16.960
<v Speaker 1>could actually move those around with effort. They were not

0:42:17.360 --> 0:42:22.200
<v Speaker 1>It wasn't a laptop, but it The British figured out

0:42:22.239 --> 0:42:25.560
<v Speaker 1>that the Germans were probably using Enigma codes not just

0:42:25.680 --> 0:42:30.040
<v Speaker 1>on official military craft, but also on things like ships

0:42:30.080 --> 0:42:34.480
<v Speaker 1>that were taking weather measurements, so weather research ships that

0:42:34.520 --> 0:42:38.120
<v Speaker 1>are not military ships. And they thought, well, why are

0:42:38.200 --> 0:42:42.279
<v Speaker 1>we focusing on capturing a German navy vessel when we

0:42:42.320 --> 0:42:44.839
<v Speaker 1>could capture one of these weather ships and get hold

0:42:44.840 --> 0:42:47.239
<v Speaker 1>of the code books that way. And in fact, that's

0:42:47.280 --> 0:42:49.080
<v Speaker 1>what a lot that's how a lot of the codes

0:42:49.120 --> 0:42:52.200
<v Speaker 1>were broken. They found code books that were accurate for

0:42:52.280 --> 0:42:56.880
<v Speaker 1>that that time period and we're able to start cracking codes.

0:42:57.360 --> 0:43:02.080
<v Speaker 1>So that's another instance of a mistake where you know,

0:43:02.160 --> 0:43:05.960
<v Speaker 1>you have to balance out who gets access to your

0:43:05.960 --> 0:43:09.640
<v Speaker 1>secret message at different levels of codes. Yeah, yeah, it

0:43:09.760 --> 0:43:14.000
<v Speaker 1>was because, again, if the machines had worked exactly correctly,

0:43:14.080 --> 0:43:15.839
<v Speaker 1>and that all the people had done what they were

0:43:15.840 --> 0:43:19.200
<v Speaker 1>supposed to do perfectly, and if the codebooks had remained

0:43:19.239 --> 0:43:23.600
<v Speaker 1>perfectly secure, the Enigma code was uncrackable. Next time, though,

0:43:23.600 --> 0:43:27.240
<v Speaker 1>we are going to be talking about some truly uncrackable codes.

0:43:28.280 --> 0:43:32.359
<v Speaker 1>We'll be talking about the Allies use of cryptography during

0:43:32.400 --> 0:43:35.760
<v Speaker 1>World War Two, So it'll it'll take us full circle

0:43:35.920 --> 0:43:40.080
<v Speaker 1>from this discussion of Enigma and Purple and Lawrens and

0:43:40.160 --> 0:43:44.000
<v Speaker 1>get into some codes that aren't based on machines, which

0:43:44.040 --> 0:43:48.359
<v Speaker 1>is a pretty huge difference. Indeed more portable for sure,

0:43:49.880 --> 0:43:52.400
<v Speaker 1>So that'll be next time. I don't know, do you

0:43:52.480 --> 0:43:56.000
<v Speaker 1>have any other comments were for the use of codes

0:43:56.120 --> 0:43:58.920
<v Speaker 1>by the Axis. I think I think we've really covered

0:43:58.920 --> 0:44:00.959
<v Speaker 1>it pretty well. What central thing to me is something

0:44:00.960 --> 0:44:03.280
<v Speaker 1>that I'll talk about more in our next episode about

0:44:03.280 --> 0:44:07.759
<v Speaker 1>how this sort of technology has evolved in how we

0:44:07.840 --> 0:44:10.000
<v Speaker 1>use it today. But that will be a good bookend.

0:44:10.040 --> 0:44:12.440
<v Speaker 1>I think that it will be how we wrap things up.

0:44:12.520 --> 0:44:15.160
<v Speaker 1>So if you want to let us know your ideas

0:44:15.280 --> 0:44:19.200
<v Speaker 1>about the access use of codes or just codes and

0:44:19.480 --> 0:44:22.359
<v Speaker 1>spies and all sorts of things during World War two.

0:44:22.440 --> 0:44:24.920
<v Speaker 1>You can email us. We're at history podcast at how

0:44:24.960 --> 0:44:28.480
<v Speaker 1>stuff works dot com. We're also on Twitter at Misston History,

0:44:28.560 --> 0:44:31.360
<v Speaker 1>and we are on Facebook and gosh, I'm sure we

0:44:31.400 --> 0:44:35.000
<v Speaker 1>have articles on codes, don't we. Oh yeah, I wrote one.

0:44:35.120 --> 0:44:36.640
<v Speaker 1>Did you write one? Well, then you go ahead and

0:44:36.640 --> 0:44:38.759
<v Speaker 1>find us off. Oh yeah. So go to how stuff

0:44:38.800 --> 0:44:42.560
<v Speaker 1>works dot com and look up code breaking because that

0:44:42.719 --> 0:44:44.879
<v Speaker 1>was one of my earliest articles. And I've been here

0:44:44.920 --> 0:44:48.280
<v Speaker 1>for nearly six years and started the same week. Yeah

0:44:48.440 --> 0:44:50.799
<v Speaker 1>and uh, And to this day it remains one of

0:44:50.840 --> 0:44:54.160
<v Speaker 1>my favorites because it was just such a fascinating world.

0:44:54.200 --> 0:44:57.560
<v Speaker 1>And I even include in that article a code that

0:44:57.640 --> 0:45:01.560
<v Speaker 1>you can break, so fun, get out your your um

0:45:01.600 --> 0:45:05.000
<v Speaker 1>cereal box sort of decoders and go for it. All right,

0:45:05.040 --> 0:45:08.160
<v Speaker 1>pretty much all you need. So How Code Breaking Works

0:45:08.200 --> 0:45:19.400
<v Speaker 1>by Jonathan Strickland at www dot how stuff works dot com.

0:45:16.160 --> 0:45:21.520
<v Speaker 1>M for more on this and thousands of other topics.

0:45:21.840 --> 0:45:47.040
<v Speaker 1>Is it how stuff works dot com.