WEBVTT - Rerun: When Secrets Aren't Secret

0:00:04.440 --> 0:00:12.239
<v Speaker 1>Welcome to Tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.240 --> 0:00:15.520
<v Speaker 1>and welcome to tech Stuff. I'm your host, Jonathan Strickland.

0:00:15.520 --> 0:00:18.400
<v Speaker 1>I'm an executive producer with iHeart Podcasts. And how the

0:00:18.440 --> 0:00:23.320
<v Speaker 1>tech are you. I am currently on vacation. Hopefully I'm

0:00:23.360 --> 0:00:25.799
<v Speaker 1>having a good time, and I hope you're having a

0:00:25.800 --> 0:00:28.000
<v Speaker 1>good time wherever you happen to be as well. But

0:00:28.120 --> 0:00:30.160
<v Speaker 1>in the meantime, I thought I would bring you an

0:00:30.240 --> 0:00:33.960
<v Speaker 1>episode that we published originally on February seventeenth, twenty twenty.

0:00:34.360 --> 0:00:38.400
<v Speaker 1>It's titled When Secrets Aren't Secret. This is about the

0:00:38.680 --> 0:00:42.440
<v Speaker 1>curious case of the CIA, the Central Intelligence Agency of

0:00:42.479 --> 0:00:46.240
<v Speaker 1>the United States of America, owning and operating an encryption company,

0:00:46.680 --> 0:00:50.080
<v Speaker 1>which seems to be a bit of a conflict. Let's

0:00:50.120 --> 0:00:53.360
<v Speaker 1>listen in. So I want to talk about the business

0:00:53.400 --> 0:00:57.680
<v Speaker 1>of communication and secrets and also the business of eavesdropping

0:00:57.840 --> 0:01:02.560
<v Speaker 1>and why all of this gets real dodgy, real fast.

0:01:03.360 --> 0:01:07.920
<v Speaker 1>So the initial story doesn't involve China or five G Networks.

0:01:08.200 --> 0:01:11.080
<v Speaker 1>It goes further back than that. It actually concerns a

0:01:11.160 --> 0:01:15.959
<v Speaker 1>Swiss company called cryptoag and its ties to the Central

0:01:16.000 --> 0:01:20.399
<v Speaker 1>Intelligence Agency aka the CIA in the United States. The

0:01:20.400 --> 0:01:23.920
<v Speaker 1>story is all about the battle between secrecy and surveillance,

0:01:24.319 --> 0:01:27.000
<v Speaker 1>and it's also about trust, as in, whom do you

0:01:27.080 --> 0:01:30.560
<v Speaker 1>trust when you want to send a secure communication to

0:01:30.600 --> 0:01:35.120
<v Speaker 1>someone else? If you're using some sort of technology to

0:01:35.360 --> 0:01:41.640
<v Speaker 1>encrypt your stuff, who makes that encryption you know, strategy,

0:01:41.720 --> 0:01:46.080
<v Speaker 1>whether it's it's software or actual device or whatever it

0:01:46.120 --> 0:01:48.960
<v Speaker 1>may be, who's making that and can they be trusted?

0:01:49.000 --> 0:01:52.120
<v Speaker 1>And as it turns out, those are difficult questions to

0:01:52.160 --> 0:01:56.320
<v Speaker 1>answer than would readily seem apparent. Now, the story for

0:01:56.360 --> 0:02:00.840
<v Speaker 1>this really begins with a Swedish inventor named ARV Gerard

0:02:01.120 --> 0:02:06.240
<v Speaker 1>Dom who was born in eighteen sixty nine. He worked

0:02:06.360 --> 0:02:09.960
<v Speaker 1>in textile mills before he would start creating his own

0:02:10.080 --> 0:02:15.120
<v Speaker 1>version of a cipher machine sometime around nineteen fifteen or so. So,

0:02:15.480 --> 0:02:20.000
<v Speaker 1>what the heck is a cipher machine? Heck? What's a cipher? Well,

0:02:20.040 --> 0:02:23.079
<v Speaker 1>a cipher is a code. It's a way of hiding

0:02:23.360 --> 0:02:25.639
<v Speaker 1>the meaning of a message. And there are a lot

0:02:25.680 --> 0:02:30.639
<v Speaker 1>of different approaches to encoding information, and there are a

0:02:30.639 --> 0:02:33.920
<v Speaker 1>lot of strategies that actually employ multiple versions of this,

0:02:34.040 --> 0:02:37.520
<v Speaker 1>multiple schemes. So, for example, one way to have a

0:02:37.560 --> 0:02:41.000
<v Speaker 1>code is to use words that refer to something else,

0:02:41.520 --> 0:02:44.919
<v Speaker 1>So instead of saying a military tank, you might say Thomas.

0:02:45.600 --> 0:02:48.280
<v Speaker 1>You know, because you got Thomas the tank engine, and

0:02:48.320 --> 0:02:51.680
<v Speaker 1>you go from Thomas the tank engine to military tank

0:02:51.760 --> 0:02:54.520
<v Speaker 1>and there you are. So if you referred to a

0:02:54.560 --> 0:02:57.560
<v Speaker 1>Thomas you might be talking about a tank. That would

0:02:57.560 --> 0:02:59.600
<v Speaker 1>be a very bad code, or at least a very

0:02:59.639 --> 0:03:03.760
<v Speaker 1>easy to decipher code. But that's a version of codes

0:03:03.800 --> 0:03:06.560
<v Speaker 1>where you have a codebook that tells you what certain

0:03:06.600 --> 0:03:11.280
<v Speaker 1>words or phrases actually are meant to convey. Then you

0:03:11.400 --> 0:03:14.880
<v Speaker 1>have ciphers in which you replace the letters of a

0:03:14.919 --> 0:03:18.440
<v Speaker 1>message with some other letter or symbol, and the simplest

0:03:18.520 --> 0:03:21.960
<v Speaker 1>of these is a shift cipher, sometimes also called a

0:03:22.080 --> 0:03:26.160
<v Speaker 1>Caesar cipher. And with these ciphers, you write on a message,

0:03:26.320 --> 0:03:30.440
<v Speaker 1>but you shift all the letters some predetermined number down

0:03:30.720 --> 0:03:33.840
<v Speaker 1>or up the alphabet. So if you had a shift

0:03:33.919 --> 0:03:38.040
<v Speaker 1>cipher with just one shift one step, that would mean

0:03:38.320 --> 0:03:40.960
<v Speaker 1>that you would use the letter B to represent the

0:03:41.040 --> 0:03:44.200
<v Speaker 1>letter A, you would use the letter C to represent

0:03:44.240 --> 0:03:47.440
<v Speaker 1>the letter B, and so on down the alphabet. So

0:03:47.440 --> 0:03:49.480
<v Speaker 1>if someone else were to get hold of the message

0:03:49.680 --> 0:03:53.240
<v Speaker 1>at casual glance, the message would appear to be gibberish.

0:03:53.320 --> 0:03:56.840
<v Speaker 1>But of course that particular cipher is super easy to decode,

0:03:57.160 --> 0:04:00.520
<v Speaker 1>even if you are shifting further up or down the alphabet.

0:04:00.760 --> 0:04:04.400
<v Speaker 1>Let's say you're shifting up ten spots instead of one. Well,

0:04:04.600 --> 0:04:08.520
<v Speaker 1>just because of the nature of language, someone with even

0:04:08.760 --> 0:04:11.200
<v Speaker 1>a little bit of patience would be able to probably

0:04:11.240 --> 0:04:14.280
<v Speaker 1>break that code pretty quickly. Well. In the early twentieth

0:04:14.360 --> 0:04:18.159
<v Speaker 1>century and victors were working on mechanical systems that would

0:04:18.200 --> 0:04:22.240
<v Speaker 1>create stronger ciphers, and initially these were mostly thought of

0:04:22.360 --> 0:04:27.000
<v Speaker 1>as a way to protect business communications like financial communications

0:04:27.040 --> 0:04:32.520
<v Speaker 1>between banks, for example, or sometimes political messages between different

0:04:33.360 --> 0:04:36.400
<v Speaker 1>parts of the world, like a government and its embassy

0:04:36.440 --> 0:04:39.760
<v Speaker 1>in another country. That over time they would be adopted

0:04:39.800 --> 0:04:43.080
<v Speaker 1>by militaries around the world to send secret communications back

0:04:43.080 --> 0:04:46.240
<v Speaker 1>and forth between headquarters and units in the field, and

0:04:46.320 --> 0:04:49.960
<v Speaker 1>these communications needed to be much more secure than a

0:04:50.040 --> 0:04:55.680
<v Speaker 1>caesar cipher could potentially offer. So the basic idea behind

0:04:55.680 --> 0:04:59.000
<v Speaker 1>these cipher machines was that you would have a device.

0:04:59.720 --> 0:05:02.000
<v Speaker 1>Sometime times it would look like a typewriter. Sometimes it

0:05:02.040 --> 0:05:05.279
<v Speaker 1>would have a hand crank on it, but typically there'd

0:05:05.279 --> 0:05:09.080
<v Speaker 1>be at least one dial, if not several dials, and

0:05:09.160 --> 0:05:11.760
<v Speaker 1>perhaps some other components that would allow the operator to

0:05:11.960 --> 0:05:16.719
<v Speaker 1>set the machine to establish the cipher. So you choose

0:05:16.720 --> 0:05:20.240
<v Speaker 1>your settings, and then the operator would take a message

0:05:20.640 --> 0:05:23.440
<v Speaker 1>that is meant to be encoded and then put it

0:05:23.560 --> 0:05:26.640
<v Speaker 1>through this machine in some way. Maybe they're using a keyboard,

0:05:27.080 --> 0:05:30.800
<v Speaker 1>maybe they're using a series of keys and levers. However

0:05:30.839 --> 0:05:34.479
<v Speaker 1>it may be they're actually typing out the message in

0:05:34.600 --> 0:05:38.159
<v Speaker 1>plain text. But the cipher machines would have some sort

0:05:38.200 --> 0:05:41.680
<v Speaker 1>of gears or other chains or systems that would turn

0:05:41.880 --> 0:05:44.560
<v Speaker 1>with each letter type, and it would change the cipher

0:05:44.640 --> 0:05:47.360
<v Speaker 1>as it did, so change the nature of it. And

0:05:47.400 --> 0:05:50.880
<v Speaker 1>this was a really clever way to confound code breakers,

0:05:51.040 --> 0:05:55.440
<v Speaker 1>particularly if the machine was really well designed. So let's

0:05:55.440 --> 0:05:58.760
<v Speaker 1>say you are an operator and you have the word

0:05:58.880 --> 0:06:02.839
<v Speaker 1>book that you need to encode using one of these machines.

0:06:03.240 --> 0:06:05.600
<v Speaker 1>So you have one of these particular machines. You type

0:06:05.640 --> 0:06:08.839
<v Speaker 1>the letter B into the device, which, because of the

0:06:08.880 --> 0:06:12.640
<v Speaker 1>settings for this particular session, will now print out the

0:06:12.720 --> 0:06:16.280
<v Speaker 1>letter G. So the letter G means B with this

0:06:16.320 --> 0:06:20.800
<v Speaker 1>particular cipher. The gears inside the machine turn after you've

0:06:20.839 --> 0:06:23.320
<v Speaker 1>typed in the letter B, which prints out as G,

0:06:23.960 --> 0:06:26.400
<v Speaker 1>So now the cipher is actually different. You type in

0:06:26.440 --> 0:06:29.359
<v Speaker 1>the first O in book and you get another G

0:06:29.960 --> 0:06:33.320
<v Speaker 1>because of the way the cipher works. Then the gears

0:06:33.360 --> 0:06:36.040
<v Speaker 1>turn again. You type in the second O, and now

0:06:36.080 --> 0:06:39.320
<v Speaker 1>the machine prints out the letter F. The gears turn again,

0:06:39.400 --> 0:06:42.120
<v Speaker 1>you type out the letter K, and you get the

0:06:42.160 --> 0:06:47.080
<v Speaker 1>print out of K, So the printed word says ggf

0:06:47.360 --> 0:06:51.960
<v Speaker 1>K rather than book. Well, to decode the message, you

0:06:51.960 --> 0:06:54.840
<v Speaker 1>would typically need the same sort of machine that was

0:06:54.920 --> 0:06:56.920
<v Speaker 1>used to encode it, and you would need to know

0:06:56.960 --> 0:06:59.920
<v Speaker 1>what settings the operator had been using when they started

0:07:00.160 --> 0:07:02.279
<v Speaker 1>the message, and you would have to set up your

0:07:02.320 --> 0:07:06.920
<v Speaker 1>machine to mirror that, and then you would end up

0:07:07.040 --> 0:07:09.840
<v Speaker 1>taking the encoded message and you would start typing that

0:07:10.000 --> 0:07:13.400
<v Speaker 1>out and the process would essentially reverse itself and it

0:07:13.400 --> 0:07:16.640
<v Speaker 1>would allow the operator to read out the original message.

0:07:17.040 --> 0:07:20.640
<v Speaker 1>So in our example, the operator on the other side

0:07:20.640 --> 0:07:24.400
<v Speaker 1>would take GGFK and enter that into their machine and

0:07:24.400 --> 0:07:27.720
<v Speaker 1>they would get the print out book. Now a couple

0:07:27.720 --> 0:07:31.200
<v Speaker 1>of caveats here. Not all cipher machines are created equal

0:07:31.680 --> 0:07:36.160
<v Speaker 1>right or were used to their best advantage. Sometimes people

0:07:36.280 --> 0:07:39.600
<v Speaker 1>made bad decisions when it came to either designing cipher

0:07:39.680 --> 0:07:43.960
<v Speaker 1>machines or implementing them. For example, the big wigs might

0:07:44.000 --> 0:07:47.000
<v Speaker 1>decide that, in no circumstance would you ever have a

0:07:47.080 --> 0:07:52.040
<v Speaker 1>letter represented by itself. You would never allow that to happen.

0:07:52.200 --> 0:07:57.320
<v Speaker 1>So in the example I just gave where GGFK means book,

0:07:57.960 --> 0:08:01.240
<v Speaker 1>that last k wouldn't work. You would have to have

0:08:01.280 --> 0:08:05.040
<v Speaker 1>the device go to a different letter because it would

0:08:05.080 --> 0:08:09.160
<v Speaker 1>not allow itself to replicate a letter with a representation

0:08:09.280 --> 0:08:12.920
<v Speaker 1>of itself. Other rules that could cause problems on the

0:08:12.680 --> 0:08:15.960
<v Speaker 1>road might be a rule against the doubling of letters

0:08:16.320 --> 0:08:20.080
<v Speaker 1>like the gg and GGFK. And the reason that these

0:08:20.160 --> 0:08:23.800
<v Speaker 1>are problems is that if you have a code breaker

0:08:24.120 --> 0:08:28.200
<v Speaker 1>who's really looking at these codes closely, and that code

0:08:28.200 --> 0:08:30.840
<v Speaker 1>breaker starts to figure out that there are restrictions to

0:08:30.920 --> 0:08:34.360
<v Speaker 1>the code, they can build that into their code breaking

0:08:34.480 --> 0:08:37.520
<v Speaker 1>models in an effort to crack the code. Because as

0:08:37.559 --> 0:08:41.240
<v Speaker 1>you put in restrictions, that means you're reducing variables. And

0:08:41.320 --> 0:08:45.040
<v Speaker 1>anyone who has worked in any sort of mathematics, particularly

0:08:45.080 --> 0:08:49.160
<v Speaker 1>stuff like algebra, you know that to solve complicated problems

0:08:49.160 --> 0:08:52.680
<v Speaker 1>you need to reduce variables. As you reduce variables, you

0:08:52.800 --> 0:08:56.320
<v Speaker 1>make it easier to solve problems. So it was actually

0:08:56.360 --> 0:08:58.280
<v Speaker 1>this sort of thing that would lead to the British

0:08:58.360 --> 0:09:02.400
<v Speaker 1>cryptographers breaking German codes during World War Two. It wasn't

0:09:02.520 --> 0:09:06.240
<v Speaker 1>that the technology itself was necessarily faulty. It was that

0:09:06.520 --> 0:09:10.640
<v Speaker 1>the Germans were kind of using bad methodology with some

0:09:10.760 --> 0:09:15.720
<v Speaker 1>of their equipment, and that's what gave an inroad for

0:09:15.840 --> 0:09:19.240
<v Speaker 1>code breakers. Now, if you want to learn way more

0:09:19.600 --> 0:09:22.800
<v Speaker 1>about how these machines actually work, you can listen to

0:09:23.080 --> 0:09:26.920
<v Speaker 1>tech Stuff Ponders and Enigma. That's a classic episode that

0:09:27.040 --> 0:09:31.679
<v Speaker 1>originally published way back on October nineteenth, twenty eleven, and

0:09:31.760 --> 0:09:34.840
<v Speaker 1>I actually did a tech Stuff Classic rerun of that

0:09:34.920 --> 0:09:40.000
<v Speaker 1>episode on October twelfth, twenty eighteen. The Enigma machine is

0:09:40.080 --> 0:09:43.520
<v Speaker 1>the most famous cipher device that was made in the

0:09:43.559 --> 0:09:47.640
<v Speaker 1>early twentieth century. It was made and used by the Germans,

0:09:47.800 --> 0:09:50.840
<v Speaker 1>and it was used extensively by the German military during

0:09:50.840 --> 0:09:53.679
<v Speaker 1>World War Two. And in that podcast, my old co

0:09:53.720 --> 0:09:56.880
<v Speaker 1>host Chris Paulette and I talk about how a really

0:09:56.880 --> 0:10:00.760
<v Speaker 1>good cipher one that's super hard to crack, is also

0:10:01.200 --> 0:10:04.679
<v Speaker 1>a pain in the patookas to use because of that complexity,

0:10:05.160 --> 0:10:08.720
<v Speaker 1>and that's mainly why officials would put rules in place

0:10:08.760 --> 0:10:12.920
<v Speaker 1>that ultimately would service the downfall for their technology, because

0:10:13.240 --> 0:10:15.960
<v Speaker 1>using the tech without those rules in place was possible,

0:10:16.080 --> 0:10:20.040
<v Speaker 1>but not always fast enough to be practical. This would

0:10:20.120 --> 0:10:23.080
<v Speaker 1>prove to be a problem with cryptography in general. You

0:10:23.120 --> 0:10:26.760
<v Speaker 1>want a system that's secure enough that you're reasonably certain

0:10:26.800 --> 0:10:30.120
<v Speaker 1>a person who intercepts the message would be unable to

0:10:30.160 --> 0:10:32.520
<v Speaker 1>make header tail of it. Right. That's the whole purpose

0:10:32.559 --> 0:10:36.840
<v Speaker 1>of cryptography is to make any unauthorized person incapable of

0:10:36.880 --> 0:10:41.080
<v Speaker 1>reading the message. But you also want your solution to

0:10:41.120 --> 0:10:44.800
<v Speaker 1>be practical enough that your intended recipient can decode the

0:10:44.840 --> 0:10:48.679
<v Speaker 1>message with a minimum of fuss, particularly if it relates

0:10:48.679 --> 0:10:52.200
<v Speaker 1>to a time sensitive issue. So in this case, you

0:10:52.280 --> 0:10:55.720
<v Speaker 1>had Germans using these same settings on their Enigma machines

0:10:56.160 --> 0:10:59.360
<v Speaker 1>for longer than they were supposed to, or they were

0:10:59.559 --> 0:11:03.200
<v Speaker 1>co locating codebooks with the Enigma machines and those fell

0:11:03.240 --> 0:11:06.240
<v Speaker 1>into Allied hands who were able to use those two

0:11:06.440 --> 0:11:11.600
<v Speaker 1>decode messages. To this day, balancing out practical applications with

0:11:11.679 --> 0:11:16.160
<v Speaker 1>security remains a challenge. It may make it take longer

0:11:16.400 --> 0:11:19.040
<v Speaker 1>for a message to get through from one point to another,

0:11:19.360 --> 0:11:22.720
<v Speaker 1>which a lot of people don't accept in the age

0:11:22.720 --> 0:11:26.240
<v Speaker 1>of information traveling at the speed of light. Or it

0:11:26.440 --> 0:11:30.760
<v Speaker 1>just may be a pain to encrypt and decrypt, which

0:11:30.840 --> 0:11:35.440
<v Speaker 1>also ends up becoming a barrier to adoption and implementation. Okay,

0:11:35.720 --> 0:11:39.400
<v Speaker 1>let's get back to our story. So it's the nineteen tens, right,

0:11:39.440 --> 0:11:44.000
<v Speaker 1>It's around nineteen fifteen. Arred Garaddam has patented an encryption device.

0:11:44.040 --> 0:11:48.000
<v Speaker 1>He got that patent by nineteen nineteen and to manufacture

0:11:48.080 --> 0:11:51.680
<v Speaker 1>and market the device, Dom would work with business partners

0:11:51.880 --> 0:11:57.360
<v Speaker 1>to create a company originally called Cryptograph or ab Cryptograph,

0:11:57.840 --> 0:12:00.800
<v Speaker 1>and one of Dom's investors was a guy named Carl

0:12:01.080 --> 0:12:04.880
<v Speaker 1>Wilhelm Heglan who had made his money in Russia in

0:12:04.920 --> 0:12:08.480
<v Speaker 1>the oil business. But then the Russian Revolution happened and

0:12:08.520 --> 0:12:12.079
<v Speaker 1>Haglan fled with his family and they returned to Haglund's

0:12:12.120 --> 0:12:15.520
<v Speaker 1>homeland of Sweden. They brought the family with them, and

0:12:16.240 --> 0:12:21.360
<v Speaker 1>Boris Haglan was a Carl Wilhelm Hegland's son, and Boris

0:12:21.440 --> 0:12:25.440
<v Speaker 1>was given a position in Dom's company in return for

0:12:25.480 --> 0:12:29.360
<v Speaker 1>this financial investment from his father. Now Boris would actually

0:12:29.400 --> 0:12:32.960
<v Speaker 1>prove to be quite the entrepreneur. In nineteen twenty five,

0:12:33.080 --> 0:12:36.080
<v Speaker 1>he would take over the company entirely. He became the

0:12:36.120 --> 0:12:39.480
<v Speaker 1>new head of the company. He would rename it Crypto

0:12:39.679 --> 0:12:43.760
<v Speaker 1>Technic in nineteen thirty two, and then when the Nazis

0:12:43.880 --> 0:12:47.719
<v Speaker 1>rose to power, he fled Sweden for Switzerland and re

0:12:47.880 --> 0:12:51.800
<v Speaker 1>established his company there, and it was this company that

0:12:51.840 --> 0:12:56.040
<v Speaker 1>he established that would later become known as Cryptoag, the

0:12:56.120 --> 0:12:59.600
<v Speaker 1>focus of our episode really well. In the meantime, his

0:12:59.640 --> 0:13:04.120
<v Speaker 1>company continued to produce new cipher machines, incorporating new features

0:13:04.160 --> 0:13:06.440
<v Speaker 1>in an effort to build machines that were able to

0:13:06.440 --> 0:13:09.800
<v Speaker 1>create stronger codes. And again, this was mostly for business

0:13:09.880 --> 0:13:13.080
<v Speaker 1>use or occasional government use, but the rise of World

0:13:13.160 --> 0:13:16.360
<v Speaker 1>War II would create a new market as military sought

0:13:16.360 --> 0:13:19.720
<v Speaker 1>ways to send messages securely without fear that their plans

0:13:19.720 --> 0:13:22.600
<v Speaker 1>would be shown to an enemy. And that's when the

0:13:22.679 --> 0:13:26.000
<v Speaker 1>United States would enter into the picture, setting the stage

0:13:26.040 --> 0:13:30.840
<v Speaker 1>for the company's future in ways Hageland could not have anticipated.

0:13:31.440 --> 0:13:34.319
<v Speaker 1>I'll explain more when we come back, but first let's

0:13:34.360 --> 0:13:47.200
<v Speaker 1>take a quick break. So when World War two broke out,

0:13:47.480 --> 0:13:51.959
<v Speaker 1>the United States military would become one of Cryptoag's customers,

0:13:52.480 --> 0:13:56.000
<v Speaker 1>and when the Nazis invaded Norway in nineteen forty, Hageland

0:13:56.040 --> 0:13:59.160
<v Speaker 1>would again move operations. This time he moved to the

0:13:59.240 --> 0:14:03.400
<v Speaker 1>United States. His company's encryption device, known as the M

0:14:03.520 --> 0:14:06.839
<v Speaker 1>two nine, would be produced in the US. According to

0:14:06.920 --> 0:14:10.440
<v Speaker 1>the Washington Post, there was a typewriter factory in upstate

0:14:10.480 --> 0:14:12.920
<v Speaker 1>New York that would end up making around one hundred

0:14:12.960 --> 0:14:18.319
<v Speaker 1>and forty thousand of these M two nine encryption devices,

0:14:18.400 --> 0:14:21.680
<v Speaker 1>and Hagland negotiated with the US Army and landed an

0:14:21.760 --> 0:14:27.800
<v Speaker 1>eight point six million dollar contract, a princely sum today,

0:14:28.120 --> 0:14:31.440
<v Speaker 1>but certainly a princely sum way back in nineteen forty.

0:14:32.120 --> 0:14:37.360
<v Speaker 1>Hegland's devices lacked the sophistication of Germany's Enigma machine. They

0:14:37.360 --> 0:14:41.560
<v Speaker 1>weren't nearly as complex, nor were they as capable of

0:14:41.640 --> 0:14:48.320
<v Speaker 1>creating very tough encryption, so codebreakers could suss out the

0:14:48.360 --> 0:14:52.280
<v Speaker 1>original messages that were created on an M two nine

0:14:52.480 --> 0:14:55.400
<v Speaker 1>if they were given enough time and attention, and for

0:14:55.440 --> 0:14:59.080
<v Speaker 1>that reason, the Army primarily relied on these devices to

0:14:59.160 --> 0:15:03.360
<v Speaker 1>disguise extra dreamly time sensitive orders. So the logic was,

0:15:03.800 --> 0:15:06.600
<v Speaker 1>by the time someone had actually broken the code, the

0:15:06.680 --> 0:15:10.640
<v Speaker 1>information would be worthless anyway, because whatever was being covered

0:15:10.640 --> 0:15:13.440
<v Speaker 1>in the message would have already happened. It would have

0:15:13.480 --> 0:15:16.440
<v Speaker 1>been something that was more imminent, so you wouldn't be

0:15:16.480 --> 0:15:18.360
<v Speaker 1>able to act on the information, even though you'd be

0:15:18.360 --> 0:15:21.520
<v Speaker 1>able to at least decode what had been said. So

0:15:21.800 --> 0:15:24.040
<v Speaker 1>you wouldn't want to use these devices for any sort

0:15:24.080 --> 0:15:29.480
<v Speaker 1>of long term plans because they were crackable. People could

0:15:29.640 --> 0:15:33.880
<v Speaker 1>crack the codes with given enough a time. Now. Around

0:15:33.960 --> 0:15:38.240
<v Speaker 1>that same time, Haglan became good friends with another cryptographer

0:15:38.560 --> 0:15:42.840
<v Speaker 1>named William Friedman. Freedman was born in Russia. Actually, so

0:15:43.000 --> 0:15:48.400
<v Speaker 1>was Haglan. Hegland's parents were Swedish, but when they had

0:15:48.440 --> 0:15:52.600
<v Speaker 1>Boris he was the family was in Russia. So Friedman's

0:15:52.600 --> 0:15:55.880
<v Speaker 1>family left Russia when Friedman was just a baby back

0:15:55.880 --> 0:15:59.160
<v Speaker 1>in eighteen ninety two due to a rise in anti

0:15:59.160 --> 0:16:03.880
<v Speaker 1>Semitism in Russia and Friedman his family's Jewish. So Freedman

0:16:04.280 --> 0:16:09.200
<v Speaker 1>grew up loving codes and cryptography and became fascinated with them.

0:16:10.160 --> 0:16:14.120
<v Speaker 1>He joined a private research lab. He met and then

0:16:14.440 --> 0:16:18.080
<v Speaker 1>courted and then married a woman named Elizabeth Smith, who

0:16:18.240 --> 0:16:22.280
<v Speaker 1>on her own was an accomplished cryptographer, a brilliant cryptographer.

0:16:22.840 --> 0:16:25.840
<v Speaker 1>And they both sort of worked for George Fabian, and

0:16:25.880 --> 0:16:28.000
<v Speaker 1>that was the guy who owned the private research lab.

0:16:28.320 --> 0:16:32.800
<v Speaker 1>Fabian sounds like the sort of person who really belonged

0:16:32.800 --> 0:16:35.480
<v Speaker 1>in the Renaissance as far as I'm concerned. In the

0:16:35.520 --> 0:16:39.840
<v Speaker 1>Renaissance you had rich nobles who would become patrons of

0:16:39.960 --> 0:16:45.880
<v Speaker 1>great thinkers and philosophers and artists. Fabian he established this

0:16:45.960 --> 0:16:48.560
<v Speaker 1>private research lab in order to look into stuff that

0:16:48.600 --> 0:16:50.720
<v Speaker 1>he just thought was interesting, which I think is kind

0:16:50.720 --> 0:16:54.240
<v Speaker 1>of cool, maybe a little eccentric. Well, when the United

0:16:54.280 --> 0:16:58.440
<v Speaker 1>States entered World War One, the Friedman's husband and wife

0:16:58.440 --> 0:17:01.680
<v Speaker 1>would work in code breaking for the United States, and

0:17:01.880 --> 0:17:06.600
<v Speaker 1>the cryptologic division of the research lab became the genesis

0:17:06.880 --> 0:17:11.359
<v Speaker 1>for the American Cryptography Service. So William Freeman would later

0:17:11.440 --> 0:17:15.159
<v Speaker 1>become the chief cryptoanalyst. In fact, he termed the or

0:17:15.160 --> 0:17:18.719
<v Speaker 1>he coined the term cryptoanalysis for the United States, and

0:17:18.840 --> 0:17:23.399
<v Speaker 1>would lead the future Signals Intelligence Service before going on

0:17:23.520 --> 0:17:27.800
<v Speaker 1>to serve in other intelligence agencies as a cryptographer. So

0:17:28.040 --> 0:17:32.160
<v Speaker 1>Friedman was very much working in the same world as Hegeland,

0:17:32.240 --> 0:17:35.280
<v Speaker 1>though you could say that these were from opposing perspectives, right,

0:17:35.359 --> 0:17:38.280
<v Speaker 1>because Hegeland's company was all about producing machines that could

0:17:38.280 --> 0:17:43.080
<v Speaker 1>incipher messages, while Freedman was largely interested in finding methods

0:17:43.119 --> 0:17:47.560
<v Speaker 1>to decipher codes. Though Freeman also worked in theory as

0:17:47.560 --> 0:17:51.320
<v Speaker 1>well to talk about different ways to create stronger ciphers.

0:17:51.400 --> 0:17:53.560
<v Speaker 1>And we'll come back to Freedman in just a moment.

0:17:53.960 --> 0:17:56.880
<v Speaker 1>So Hegelan would stay in the US until World War

0:17:56.920 --> 0:18:00.600
<v Speaker 1>Two ended in Europe, and he had become extremely wealthy

0:18:00.720 --> 0:18:03.479
<v Speaker 1>due to the lucrative army contract he had made, and

0:18:03.520 --> 0:18:06.080
<v Speaker 1>he had built many professional and personal relationships in the

0:18:06.200 --> 0:18:09.639
<v Speaker 1>United States so he would have strong ties to the US.

0:18:10.160 --> 0:18:13.560
<v Speaker 1>He then returned to Europe to again re establish his

0:18:13.680 --> 0:18:18.800
<v Speaker 1>company there. Meanwhile, American intelligence officials were starting to get

0:18:18.840 --> 0:18:22.760
<v Speaker 1>a little worried because code breaking was growing increasingly difficult

0:18:23.080 --> 0:18:28.320
<v Speaker 1>due to sophisticated machines running complicated systems to create these codes.

0:18:28.880 --> 0:18:31.920
<v Speaker 1>And if you had little insight into how those machines

0:18:31.960 --> 0:18:36.720
<v Speaker 1>worked or which systems they were following at any given time,

0:18:37.400 --> 0:18:39.960
<v Speaker 1>you had really little hope of breaking a code in

0:18:40.000 --> 0:18:42.520
<v Speaker 1>a reasonable amount of time. So it was very clear

0:18:42.600 --> 0:18:45.959
<v Speaker 1>that a lot of people were having really secret conversations

0:18:46.280 --> 0:18:50.040
<v Speaker 1>that American spies were unable to decipher, and that just

0:18:50.200 --> 0:18:53.560
<v Speaker 1>rubbed the Americans the wrong way. I'm going to get

0:18:53.600 --> 0:18:58.720
<v Speaker 1>a little critical of my country in this episode, anyway.

0:18:58.920 --> 0:19:03.280
<v Speaker 1>In nineteen fifty one, on Hageland's company introduced the CX

0:19:03.520 --> 0:19:07.520
<v Speaker 1>fifty two cipher machine, and this one was sophisticated enough

0:19:07.560 --> 0:19:11.080
<v Speaker 1>to present a code that American intelligence agents viewed as

0:19:11.240 --> 0:19:15.520
<v Speaker 1>practically unbreakable at the time, and that in turn prompted

0:19:15.600 --> 0:19:21.680
<v Speaker 1>some heated internal discussions within the US intelligence community and

0:19:21.920 --> 0:19:24.359
<v Speaker 1>what should officials do about this? Because there was a

0:19:24.400 --> 0:19:29.440
<v Speaker 1>real worry that countries might go out and buy Hageland's products.

0:19:29.640 --> 0:19:32.359
<v Speaker 1>I mean, that's what Hagland was making them for. And

0:19:32.520 --> 0:19:34.560
<v Speaker 1>if they did that, they would all be able to

0:19:34.600 --> 0:19:38.280
<v Speaker 1>communicate secretly, and the Americans would be unable to snoop

0:19:38.320 --> 0:19:42.000
<v Speaker 1>out what was going on. And boy, howdy does America

0:19:42.040 --> 0:19:46.040
<v Speaker 1>hate that. So American officials gave a sort of carrot

0:19:46.040 --> 0:19:49.720
<v Speaker 1>and a stick offer to Hagland. So on the one hand,

0:19:50.200 --> 0:19:53.080
<v Speaker 1>they were a big customer for his company, right, the

0:19:53.160 --> 0:19:59.240
<v Speaker 1>United States represented a significant potential customer for Hageland's products.

0:19:59.560 --> 0:20:01.800
<v Speaker 1>He didn't want that source of revenue to go away.

0:20:01.920 --> 0:20:06.439
<v Speaker 1>So there was that They also had a whole bunch

0:20:06.480 --> 0:20:11.320
<v Speaker 1>of old M two nine cipher devices that were manufactured

0:20:11.359 --> 0:20:15.359
<v Speaker 1>in America during World War Two, and there was at

0:20:15.440 --> 0:20:19.879
<v Speaker 1>least the implied threat that if Hagelan wouldn't be you know,

0:20:20.280 --> 0:20:24.919
<v Speaker 1>cooperative with the US, maybe the Americans might let a

0:20:24.960 --> 0:20:28.040
<v Speaker 1>few thousand M two nine s get sold off to

0:20:28.119 --> 0:20:31.760
<v Speaker 1>countries around the world, and that would undercut Crypto's own

0:20:31.920 --> 0:20:35.879
<v Speaker 1>sales in the process. I mean, if you are a

0:20:36.200 --> 0:20:39.439
<v Speaker 1>country you know, the head of an agency in a

0:20:39.720 --> 0:20:44.119
<v Speaker 1>smaller country with limited resources, and the United States says, hey,

0:20:44.200 --> 0:20:49.240
<v Speaker 1>we'll sell you these old but totally working cipher machines

0:20:49.600 --> 0:20:52.880
<v Speaker 1>for much less than that brand new, shiny cipher machine.

0:20:53.200 --> 0:20:55.040
<v Speaker 1>You're going to go with the cheaper model as long

0:20:55.080 --> 0:20:58.439
<v Speaker 1>as it works, and that means that Crypto would not

0:20:58.560 --> 0:21:04.520
<v Speaker 1>be making any sale. Then there was William Friedman, Hageland's

0:21:04.560 --> 0:21:08.159
<v Speaker 1>old buddy. In nineteen fifty one, Freeman was then serving

0:21:08.200 --> 0:21:11.320
<v Speaker 1>as the head of the Cryptographic Division of the Armed

0:21:11.440 --> 0:21:16.800
<v Speaker 1>Forces Security Agency or AFSA AFSA. The following year he

0:21:16.800 --> 0:21:19.679
<v Speaker 1>would become the head of the Cryptology Department for the

0:21:19.840 --> 0:21:24.359
<v Speaker 1>National Security Agency, or the NSA. But it was in

0:21:24.440 --> 0:21:27.080
<v Speaker 1>nineteen fifty one when Friedman would act on behalf of

0:21:27.119 --> 0:21:31.920
<v Speaker 1>the US government and met secretly with Hagelan in Washington,

0:21:32.040 --> 0:21:35.800
<v Speaker 1>d c. So Friedman goes up to Hagelan with a

0:21:35.840 --> 0:21:42.159
<v Speaker 1>fairly thorny proposition. The deal was this, Hageland was to

0:21:42.200 --> 0:21:45.880
<v Speaker 1>continue creating cipher machines just as the company had been,

0:21:46.640 --> 0:21:51.040
<v Speaker 1>but Crypto would only sell the most sophisticated of those

0:21:51.119 --> 0:21:54.399
<v Speaker 1>machines to a list of countries that the United States

0:21:54.440 --> 0:21:59.320
<v Speaker 1>would provide to Hageland, and that would represent countries with

0:21:59.400 --> 0:22:02.879
<v Speaker 1>whom the un U had very good relations, so allies

0:22:02.920 --> 0:22:05.280
<v Speaker 1>and that sort of thing. They were the only countries

0:22:05.320 --> 0:22:08.520
<v Speaker 1>who would be allowed to buy the top of the

0:22:08.600 --> 0:22:13.160
<v Speaker 1>line products. Crypto would be allowed to sell older, more

0:22:13.720 --> 0:22:17.600
<v Speaker 1>vulnerable or weak machines to any country that was not

0:22:18.000 --> 0:22:20.760
<v Speaker 1>on that list. So in other words, Freeman was asking

0:22:20.800 --> 0:22:25.359
<v Speaker 1>Hegeland to kind of put on a preference list certain

0:22:25.440 --> 0:22:33.680
<v Speaker 1>countries and then everyone else would get older, more vulnerable technologies. However,

0:22:33.960 --> 0:22:36.600
<v Speaker 1>that's the extent of that deal. It didn't go further

0:22:36.680 --> 0:22:38.800
<v Speaker 1>than that, but it's still a pretty big request, and

0:22:39.280 --> 0:22:42.560
<v Speaker 1>you can kind of understand where the US was coming from.

0:22:42.920 --> 0:22:46.119
<v Speaker 1>At least, you know, they clearly did not want the

0:22:46.200 --> 0:22:50.120
<v Speaker 1>job to be even harder when it came to breaking codes.

0:22:50.680 --> 0:22:54.120
<v Speaker 1>And Hegeland would ultimately agree to this deal, and whether

0:22:54.160 --> 0:22:56.679
<v Speaker 1>it was he saw a guaranteed payout from the US

0:22:56.720 --> 0:22:59.040
<v Speaker 1>and so it was strictly a business decision. He just

0:22:59.400 --> 0:23:02.000
<v Speaker 1>fello was in Goswel to turn down this offer, or

0:23:02.040 --> 0:23:05.120
<v Speaker 1>he felt a strong sense of loyalty toward a country

0:23:05.160 --> 0:23:07.520
<v Speaker 1>that had made him a millionaire, or maybe it was

0:23:07.600 --> 0:23:10.639
<v Speaker 1>some combination of these and other factors. I don't know,

0:23:10.720 --> 0:23:14.280
<v Speaker 1>but whatever it was, he said yes, and this would

0:23:14.320 --> 0:23:18.040
<v Speaker 1>mark the beginning of the US intelligence community having a

0:23:18.160 --> 0:23:23.200
<v Speaker 1>direct interest in a company that was selling cryptographic equipment,

0:23:23.240 --> 0:23:26.320
<v Speaker 1>that is Crypto. But at this point it was still

0:23:26.359 --> 0:23:30.000
<v Speaker 1>a fairly limited agreement. Crypto could still sell equipment to

0:23:30.080 --> 0:23:33.119
<v Speaker 1>countries all around the world, though any country that was

0:23:33.240 --> 0:23:36.439
<v Speaker 1>not on the US Best Buddy list would only have

0:23:36.520 --> 0:23:40.680
<v Speaker 1>access to the older devices. Now this wasn't because US

0:23:40.680 --> 0:23:44.240
<v Speaker 1>officials were feeling benevolent or anything like that. I don't

0:23:44.280 --> 0:23:46.960
<v Speaker 1>want to paint it as that. There was a very

0:23:47.040 --> 0:23:51.560
<v Speaker 1>real desire in America to push Crypto for a much

0:23:51.600 --> 0:23:55.520
<v Speaker 1>more shady deal. Intelligence officials were hoping that they could

0:23:55.600 --> 0:24:00.000
<v Speaker 1>work directly with Crypto to design machines that were produced

0:24:00.119 --> 0:24:04.680
<v Speaker 1>codes that Americans could quickly break. People would think they

0:24:04.680 --> 0:24:07.840
<v Speaker 1>were sending secure messages, but in reality the Americans would

0:24:07.840 --> 0:24:11.200
<v Speaker 1>be able to decode those messages fairly quickly. But William

0:24:11.200 --> 0:24:16.000
<v Speaker 1>Friedman discouraged anyone from America from going to Hageland with

0:24:16.040 --> 0:24:19.040
<v Speaker 1>such an offer for several years. He said Hageland would

0:24:19.040 --> 0:24:22.280
<v Speaker 1>never go for it. It would be deeply offensive to him.

0:24:22.359 --> 0:24:25.560
<v Speaker 1>You're going to destroy this relationship we have let's not

0:24:26.480 --> 0:24:29.919
<v Speaker 1>you know, let's let's hold back rather than have a loss.

0:24:30.560 --> 0:24:33.000
<v Speaker 1>And hey, there were other companies out there, right, I mean,

0:24:33.320 --> 0:24:36.159
<v Speaker 1>it's not like you had to buy from Crypto or

0:24:36.200 --> 0:24:38.400
<v Speaker 1>else you'd have no way to communicate secretly. You could

0:24:38.400 --> 0:24:42.800
<v Speaker 1>always get cipher machines and cryptography machines from some other source,

0:24:42.920 --> 0:24:46.520
<v Speaker 1>right well. Part of the deal that the US made

0:24:47.040 --> 0:24:50.879
<v Speaker 1>included substantial amounts of money meant to go toward marketing.

0:24:51.200 --> 0:24:55.040
<v Speaker 1>The US wanted Crypto to be the world leader in

0:24:55.119 --> 0:24:59.679
<v Speaker 1>the market for this sort of device, mostly in an

0:24:59.720 --> 0:25:02.560
<v Speaker 1>effort to make sure that some other crypto company didn't

0:25:02.560 --> 0:25:07.040
<v Speaker 1>come along with better, more difficult to crack solutions, because

0:25:07.040 --> 0:25:09.560
<v Speaker 1>that would just set America back again. So the US

0:25:09.800 --> 0:25:13.119
<v Speaker 1>supplied money year after year to Crypto to renew this

0:25:13.200 --> 0:25:16.360
<v Speaker 1>agreement and to keep the company going even if things

0:25:16.359 --> 0:25:19.879
<v Speaker 1>should get lean, all the while trying to promote cryptos

0:25:20.000 --> 0:25:23.720
<v Speaker 1>products and hold back any of Crypto's competitors. It was

0:25:23.760 --> 0:25:28.280
<v Speaker 1>pretty brutal. Things slowly began to change as time went on.

0:25:28.720 --> 0:25:32.199
<v Speaker 1>The Invention of the transistor would bring on tons of

0:25:32.200 --> 0:25:36.680
<v Speaker 1>innovation and miniaturization. So in the past electric circuits were

0:25:36.800 --> 0:25:41.200
<v Speaker 1>physically enormous because you had to have components like vacuum tubes,

0:25:41.560 --> 0:25:43.439
<v Speaker 1>and those took up a lot of space, and they

0:25:43.440 --> 0:25:45.919
<v Speaker 1>also gave off a lot of heat, which generally is

0:25:46.320 --> 0:25:49.679
<v Speaker 1>bad not just for humans but also for electronics. But

0:25:49.920 --> 0:25:52.600
<v Speaker 1>in the mid nineteen sixties that was all starting to change.

0:25:52.640 --> 0:25:55.919
<v Speaker 1>Electronic circuits could now be made much smaller thanks to

0:25:55.960 --> 0:25:59.200
<v Speaker 1>the transistor, and they made it possible for all sorts

0:25:59.359 --> 0:26:03.480
<v Speaker 1>of new gaps like pocket radios and desktop computers further

0:26:03.520 --> 0:26:07.400
<v Speaker 1>down the line, and yes, new types of cryptographic machines.

0:26:08.400 --> 0:26:11.840
<v Speaker 1>Hagelan was facing a very real problem at that point.

0:26:12.200 --> 0:26:18.160
<v Speaker 1>His company was built around mechanical cryptographic devices. These were

0:26:18.160 --> 0:26:23.159
<v Speaker 1>machines that relied on physical components like gears and levers

0:26:23.320 --> 0:26:26.760
<v Speaker 1>and chains. But the electronic era was heading in a

0:26:26.800 --> 0:26:31.120
<v Speaker 1>different direction, and the crypto company wasn't in a position

0:26:31.240 --> 0:26:34.840
<v Speaker 1>to keep up. If Hagelan wanted to compete, he was

0:26:34.880 --> 0:26:38.800
<v Speaker 1>going to need help. And when someone needs help, that

0:26:38.960 --> 0:26:42.000
<v Speaker 1>means they are vulnerable. Now, if you're in a position

0:26:42.040 --> 0:26:45.399
<v Speaker 1>to help someone, you can more or less selflessly help

0:26:45.520 --> 0:26:48.400
<v Speaker 1>that person to get them out of that vulnerable position,

0:26:49.160 --> 0:26:53.240
<v Speaker 1>or you can attempt to exploit it. And the US

0:26:53.320 --> 0:26:57.720
<v Speaker 1>intelligence community with the NSSA at the forefront took option

0:26:57.960 --> 0:27:02.800
<v Speaker 1>number two. THESA, as I said. The National Security Agency

0:27:03.320 --> 0:27:06.639
<v Speaker 1>was founded in nineteen fifty two, just five years after

0:27:06.720 --> 0:27:11.119
<v Speaker 1>the Central Intelligence Agency was founded. It's primarily focused on

0:27:11.440 --> 0:27:15.679
<v Speaker 1>signals intelligence, and that is the interception and decoding of

0:27:15.760 --> 0:27:19.919
<v Speaker 1>messages for the purposes of gathering intelligence. Over at the NSA,

0:27:20.400 --> 0:27:25.119
<v Speaker 1>an analyst named Peter Jenks hypothesized that with care, you

0:27:25.200 --> 0:27:30.280
<v Speaker 1>could create an electronic cryptographic system that would seem to

0:27:30.359 --> 0:27:35.240
<v Speaker 1>be random, but it would actually depend upon a repeated

0:27:35.440 --> 0:27:39.399
<v Speaker 1>pattern at regular intervals, and a casual glance at the

0:27:39.440 --> 0:27:41.399
<v Speaker 1>code would make it seem as though the system was

0:27:41.440 --> 0:27:45.480
<v Speaker 1>following a complicated algorithm and producing an uncrackable code because

0:27:45.520 --> 0:27:49.359
<v Speaker 1>of some sort of random element. But the repetition of

0:27:49.400 --> 0:27:52.720
<v Speaker 1>the pattern would actually make code breakers with sufficient computing

0:27:52.760 --> 0:27:56.919
<v Speaker 1>power able to decode the messages. It wouldn't be easy,

0:27:57.119 --> 0:27:59.560
<v Speaker 1>it wouldn't be as simple as just running it through

0:27:59.600 --> 0:28:04.320
<v Speaker 1>a decode, but because of that pattern, it would become possible. Again,

0:28:04.640 --> 0:28:11.280
<v Speaker 1>Patterns represent restrictions. Restrictions are vulnerabilities, and vulnerabilities can be exploited.

0:28:11.720 --> 0:28:13.760
<v Speaker 1>So you can make a system that, at least on

0:28:13.920 --> 0:28:19.640
<v Speaker 1>casual glance appears to be secure, but in reality it's not. So.

0:28:20.200 --> 0:28:23.080
<v Speaker 1>The NSA reaches out to Crypto, which is really in

0:28:23.119 --> 0:28:26.680
<v Speaker 1>need of expertise in the form of building electronic cryptographic machines,

0:28:27.040 --> 0:28:31.360
<v Speaker 1>and Hageln welcomes the help because otherwise his business is

0:28:31.440 --> 0:28:34.840
<v Speaker 1>going to completely lose out. So Crypto goes on to

0:28:34.880 --> 0:28:37.919
<v Speaker 1>produce a machine called the H four to sixty based

0:28:37.920 --> 0:28:42.440
<v Speaker 1>off the NSA's design. The company actually made two versions

0:28:42.680 --> 0:28:46.440
<v Speaker 1>of the H four to sixty. One was compromised. It

0:28:46.640 --> 0:28:49.840
<v Speaker 1>used the NSA's repeating pattern so that the agency could

0:28:49.880 --> 0:28:52.320
<v Speaker 1>with time and effort, to code any messages that were

0:28:52.320 --> 0:28:56.880
<v Speaker 1>composed on that particular machine. The other one was more secure,

0:28:56.960 --> 0:29:00.160
<v Speaker 1>it didn't repeat the pattern, so the United States was

0:29:00.200 --> 0:29:04.520
<v Speaker 1>still fine with Crypto selling those machines, the good ones

0:29:04.760 --> 0:29:07.720
<v Speaker 1>to countries that were still on the US Best Buddy list.

0:29:08.360 --> 0:29:11.480
<v Speaker 1>Everyone else would get the compromised version. Now. While the

0:29:11.560 --> 0:29:15.360
<v Speaker 1>NSA's assistance meant that Crypto would remain a viable company

0:29:15.600 --> 0:29:18.760
<v Speaker 1>as the world moved away from mechanical systems, it also

0:29:18.800 --> 0:29:21.880
<v Speaker 1>meant that Crypto was a company that was becoming increasingly

0:29:21.920 --> 0:29:27.560
<v Speaker 1>dependent upon American intelligence agencies. Toward the end of the sixties,

0:29:27.960 --> 0:29:30.920
<v Speaker 1>folks in the CIA were starting to get a little

0:29:31.000 --> 0:29:35.240
<v Speaker 1>bit antsy with the company Crypto. It was a valuable

0:29:35.280 --> 0:29:40.080
<v Speaker 1>asset and countries around the world depended upon equipment from Crypto,

0:29:40.160 --> 0:29:43.200
<v Speaker 1>which meant the US had incredible advantages when it came

0:29:43.240 --> 0:29:47.720
<v Speaker 1>to deciphering intelligence. But Hagelin was getting up there in years,

0:29:47.760 --> 0:29:50.440
<v Speaker 1>He was getting into his eighties, and there was no

0:29:50.560 --> 0:29:54.239
<v Speaker 1>guarantee that his successor would be as amenable to the

0:29:54.240 --> 0:29:58.640
<v Speaker 1>intelligence agents as Haglin had been. Initially, it appeared as

0:29:58.640 --> 0:30:00.840
<v Speaker 1>though he was going to hand over control of his

0:30:00.880 --> 0:30:05.640
<v Speaker 1>company to his son, Bo Hageln. The CIA was not

0:30:06.000 --> 0:30:10.120
<v Speaker 1>crazy about that idea. The agency was not convinced that

0:30:10.200 --> 0:30:15.040
<v Speaker 1>Bo Haglan would be as pliable as Boris Hagelin had been,

0:30:15.440 --> 0:30:17.640
<v Speaker 1>and the nature of the company's relationship with the US

0:30:17.720 --> 0:30:21.720
<v Speaker 1>intelligence community had been kept a secret from Bo. So

0:30:21.920 --> 0:30:26.120
<v Speaker 1>Boris Hagelnd's own son did not apparently know about this

0:30:26.480 --> 0:30:32.200
<v Speaker 1>relationship with the NSA and later the CIA. So Boris

0:30:32.240 --> 0:30:34.320
<v Speaker 1>and his son Bo were also not on the best

0:30:34.320 --> 0:30:40.640
<v Speaker 1>of terms. They frequently had pretty massive fights. Bo had

0:30:40.680 --> 0:30:44.400
<v Speaker 1>felt he had been left out of some pretty important

0:30:44.880 --> 0:30:49.200
<v Speaker 1>patents that he had contributed to, and so he was

0:30:49.840 --> 0:30:54.560
<v Speaker 1>not on good speaking terms with his father. So this

0:30:54.760 --> 0:30:59.200
<v Speaker 1>was a complicated issue and the US government wasn't entirely

0:30:59.240 --> 0:31:02.920
<v Speaker 1>sure how it was going to play out. Meanwhile, over

0:31:02.960 --> 0:31:07.000
<v Speaker 1>in Europe, you had intelligence agencies in West Germany because

0:31:07.040 --> 0:31:10.200
<v Speaker 1>you know, after World War Two, Germany was split up

0:31:10.280 --> 0:31:13.360
<v Speaker 1>into West Germany and East Germany. So West Germany and

0:31:13.400 --> 0:31:16.480
<v Speaker 1>an intelligence agency in France were both eager to purchase

0:31:16.520 --> 0:31:21.120
<v Speaker 1>Crypto from Hageland. You know, Hagland's getting very old, and

0:31:21.160 --> 0:31:23.920
<v Speaker 1>so they think, hey, if we buy this company, then

0:31:23.960 --> 0:31:28.560
<v Speaker 1>we can benefit from this technology. They had figured out

0:31:28.600 --> 0:31:32.360
<v Speaker 1>that the United States had some sort of beneficial relationship

0:31:32.480 --> 0:31:35.320
<v Speaker 1>with Crypto. I'm not sure if they knew the full

0:31:35.360 --> 0:31:37.440
<v Speaker 1>extent of it, but they at least knew that there

0:31:37.520 --> 0:31:40.360
<v Speaker 1>was Someboddy Buddy stuff going on there and they wanted

0:31:40.400 --> 0:31:44.280
<v Speaker 1>to get in on that action. Haglan rejected this initial

0:31:44.280 --> 0:31:47.200
<v Speaker 1>offer and told the CIA about it. So then we

0:31:47.240 --> 0:31:51.960
<v Speaker 1>get to nineteen seventy and then two really big things happen. First,

0:31:52.520 --> 0:31:57.280
<v Speaker 1>Bo Haglan Boris's son would die in a car accident,

0:31:58.200 --> 0:32:02.120
<v Speaker 1>and no conspiracy theorist does not appear that this was

0:32:02.960 --> 0:32:07.040
<v Speaker 1>engineered or manufactured in some way. It appears to have

0:32:07.080 --> 0:32:10.400
<v Speaker 1>been just a car accident and Bo dies as a

0:32:10.440 --> 0:32:14.840
<v Speaker 1>result of this. The CIA cooperates with West Germany's Federal

0:32:14.880 --> 0:32:19.320
<v Speaker 1>Intelligence Service also known as bn D. It's called that

0:32:19.360 --> 0:32:23.840
<v Speaker 1>because in German federal Intelligence service is a different, very

0:32:23.920 --> 0:32:26.240
<v Speaker 1>long word that I am not even going to attempt

0:32:26.280 --> 0:32:29.880
<v Speaker 1>to pronounce, and they create an agreement in which these

0:32:29.960 --> 0:32:35.200
<v Speaker 1>two agencies would co own the company. In secret, the

0:32:35.200 --> 0:32:38.680
<v Speaker 1>CIA told West Germany, hey, we'll totally go in z's

0:32:38.760 --> 0:32:40.960
<v Speaker 1>with you on this one, but you got to cut

0:32:41.000 --> 0:32:45.400
<v Speaker 1>France out of the deal, and West Germany said, okay.

0:32:46.800 --> 0:32:52.840
<v Speaker 1>By France, alf Vida zey Hageln would be presented with

0:32:52.920 --> 0:32:55.239
<v Speaker 1>this deal and would agree to the terms, and the

0:32:55.280 --> 0:32:59.840
<v Speaker 1>agencies would rely upon a company in Liechtenstein that was

0:33:00.680 --> 0:33:04.840
<v Speaker 1>called Marxer and Goop at the time. Great name, but

0:33:04.920 --> 0:33:07.440
<v Speaker 1>Marxer and Goop would draw up the agreement in such

0:33:07.440 --> 0:33:10.840
<v Speaker 1>a way that the agency's identities would be protected through

0:33:10.840 --> 0:33:15.240
<v Speaker 1>a series of shell companies and other you know, obfuscation,

0:33:15.840 --> 0:33:19.200
<v Speaker 1>so even if you were to dig into it, you

0:33:19.240 --> 0:33:22.800
<v Speaker 1>would not be able to see that the CIA and

0:33:22.920 --> 0:33:26.520
<v Speaker 1>B and D were co owners of this company. Instead,

0:33:26.560 --> 0:33:29.560
<v Speaker 1>you would get all these this sort of a run around,

0:33:29.640 --> 0:33:33.040
<v Speaker 1>you know, a wild goose chase about the ownership of Crypto.

0:33:33.320 --> 0:33:36.600
<v Speaker 1>It would not appear to be owned by any intelligence agencies. However,

0:33:37.000 --> 0:33:40.000
<v Speaker 1>so hag Glen sold his company for just under six

0:33:40.040 --> 0:33:44.320
<v Speaker 1>million dollars. He would pass away in nineteen eighty three

0:33:44.520 --> 0:33:48.160
<v Speaker 1>after a very long illness, so he kind of leaves

0:33:48.200 --> 0:33:52.160
<v Speaker 1>our story. But meanwhile, the two intelligence agencies now had

0:33:52.200 --> 0:33:55.080
<v Speaker 1>secret control of a company that manufactured products meant to

0:33:55.120 --> 0:33:58.480
<v Speaker 1>make communications secret. I think you can see where this

0:33:58.640 --> 0:34:03.160
<v Speaker 1>is going, right. If your agency is all about uncovering

0:34:03.240 --> 0:34:06.600
<v Speaker 1>secrets and then you get control of a leading company

0:34:07.080 --> 0:34:11.799
<v Speaker 1>that makes stuff that's supposed to create things secretly, you're

0:34:11.840 --> 0:34:13.360
<v Speaker 1>like a kid in a candy store. I mean, it

0:34:14.400 --> 0:34:17.560
<v Speaker 1>was like they were selling locks to everyone in the world,

0:34:17.640 --> 0:34:19.799
<v Speaker 1>but they were holding on to all the skeleton keys

0:34:19.840 --> 0:34:24.439
<v Speaker 1>that would give them access to those locks. It was incredible. Now,

0:34:24.440 --> 0:34:27.759
<v Speaker 1>I should be clear that the list of clients for

0:34:27.920 --> 0:34:32.440
<v Speaker 1>Crypto did not include everybody. Not everyone in the world

0:34:32.840 --> 0:34:36.000
<v Speaker 1>was eager to purchase the products from this company. Two

0:34:36.600 --> 0:34:39.920
<v Speaker 1>potential customers in particular were not on the list. China

0:34:40.280 --> 0:34:44.239
<v Speaker 1>and Russia were both suspicious about Crypto for years. By

0:34:44.280 --> 0:34:48.439
<v Speaker 1>the time the CIA gained partial ownership, so they did

0:34:48.440 --> 0:34:53.399
<v Speaker 1>not purchase those products. They were figured something was up.

0:34:53.640 --> 0:34:57.960
<v Speaker 1>But other countries, including lots of US allies, were Crypto

0:34:58.040 --> 0:35:02.840
<v Speaker 1>customers frequent ones. While these two agencies would share ownership

0:35:02.880 --> 0:35:05.000
<v Speaker 1>of the company for a couple of decades, things were

0:35:05.000 --> 0:35:08.680
<v Speaker 1>not always super smooth between them. The West Germans noted

0:35:08.800 --> 0:35:11.359
<v Speaker 1>in their own history about the project that was shared

0:35:11.400 --> 0:35:15.000
<v Speaker 1>with The Washington Post that the Americans were eager to

0:35:15.080 --> 0:35:20.680
<v Speaker 1>spy on everybody really, enemy or ally alike. The West

0:35:20.680 --> 0:35:24.319
<v Speaker 1>German officials were really they were focusing on countries that

0:35:24.400 --> 0:35:28.440
<v Speaker 1>were not allies, but the Americans wanted to snoop on everybody.

0:35:29.120 --> 0:35:33.520
<v Speaker 1>CIA historians, meanwhile, note that the American officials felt that

0:35:33.600 --> 0:35:37.239
<v Speaker 1>the West Germans were more interested in running Crypto as

0:35:37.239 --> 0:35:40.200
<v Speaker 1>a straightforward business to earn money, and they were looking

0:35:40.239 --> 0:35:43.800
<v Speaker 1>at as a revenue generator, not as a way to

0:35:43.840 --> 0:35:46.840
<v Speaker 1>dip into secrets. So both the CIA and the B

0:35:47.000 --> 0:35:50.120
<v Speaker 1>and D would take in millions of dollars over the

0:35:50.200 --> 0:35:53.239
<v Speaker 1>years as they operated Crypto, and they would pour that

0:35:53.360 --> 0:35:56.480
<v Speaker 1>money into other projects around the world. So if you

0:35:56.560 --> 0:36:01.400
<v Speaker 1>ever wondered how some CIA operations appeared happen under the radar,

0:36:01.760 --> 0:36:05.279
<v Speaker 1>it's not all just you know, dark deals that are

0:36:05.640 --> 0:36:08.800
<v Speaker 1>behind closed doors in DC. Some of that money comes

0:36:08.920 --> 0:36:14.440
<v Speaker 1>straight from CIA backed operations that are appearing to be

0:36:14.640 --> 0:36:18.759
<v Speaker 1>you know, honest businesses. So that's fun. We're going to

0:36:18.800 --> 0:36:22.239
<v Speaker 1>take a break for actual honest businesses. But we'll be

0:36:22.480 --> 0:36:36.120
<v Speaker 1>right back after these messages. So in the CIA history

0:36:36.360 --> 0:36:39.000
<v Speaker 1>for this project, and I have not read the entire

0:36:39.120 --> 0:36:43.040
<v Speaker 1>history because it was not made available. The Post was

0:36:43.080 --> 0:36:47.280
<v Speaker 1>only granted the right to produce excerpts from the report,

0:36:47.360 --> 0:36:51.440
<v Speaker 1>not the entire report. But the agency refers to Crypto

0:36:51.800 --> 0:36:55.480
<v Speaker 1>with a code name. That code name is Minerva, and

0:36:55.560 --> 0:37:00.799
<v Speaker 1>the project of running Crypto in an effort to to

0:37:00.920 --> 0:37:04.680
<v Speaker 1>produce equipment that could be exploited around the world had

0:37:04.840 --> 0:37:07.880
<v Speaker 1>two different code names. The first one was the Saurus

0:37:08.400 --> 0:37:13.800
<v Speaker 1>and the second one was Rubicon. So German intelligence agents

0:37:14.320 --> 0:37:18.560
<v Speaker 1>would later bring in officials from Semens the company Semens

0:37:18.800 --> 0:37:25.120
<v Speaker 1>to serve as advisors, technical advisors and entrepreneurial advisors for Crypto,

0:37:25.560 --> 0:37:29.360
<v Speaker 1>and in return, Siemens would get five percent of cryptos sales.

0:37:30.160 --> 0:37:33.640
<v Speaker 1>The Americans, they brought in Motorola to take some of

0:37:33.680 --> 0:37:38.240
<v Speaker 1>Crypto's products and to tweak them to make them work better.

0:37:38.680 --> 0:37:44.360
<v Speaker 1>Make them more commercially viable. So we've got two intelligence

0:37:44.360 --> 0:37:49.480
<v Speaker 1>agencies and two major companies all working together as part

0:37:49.480 --> 0:37:53.000
<v Speaker 1>of this, and all indications seem to point that at

0:37:53.120 --> 0:37:56.040
<v Speaker 1>least some people in those two big companies knew what

0:37:56.239 --> 0:38:00.600
<v Speaker 1>was up. By the nineteen eighties, more than half of

0:38:00.760 --> 0:38:04.239
<v Speaker 1>all the intelligence gathered by the CIA that came from

0:38:04.239 --> 0:38:08.480
<v Speaker 1>places other than China or Russia were encrypted by crypto machines.

0:38:09.040 --> 0:38:13.319
<v Speaker 1>So when you look at all the information that the

0:38:13.320 --> 0:38:17.440
<v Speaker 1>CIA was bringing in, if it wasn't from Russia and

0:38:17.480 --> 0:38:19.719
<v Speaker 1>if it wasn't from China, more than half of the

0:38:19.800 --> 0:38:22.480
<v Speaker 1>information had passed through a crypto machine, meaning that the

0:38:22.520 --> 0:38:27.040
<v Speaker 1>CIA could decrypt it and read the underlying messages. There

0:38:27.040 --> 0:38:28.839
<v Speaker 1>were some times where they said that they could read

0:38:29.239 --> 0:38:33.600
<v Speaker 1>messages from certain countries with eighty to ninety percent success,

0:38:33.960 --> 0:38:37.600
<v Speaker 1>which is pretty phenomenal in the world of cryptography and

0:38:37.640 --> 0:38:42.600
<v Speaker 1>code breaking. Well, neither Russia nor China would use crypto devices,

0:38:42.920 --> 0:38:46.360
<v Speaker 1>a lot of countries that were dealing with those countries

0:38:46.400 --> 0:38:50.319
<v Speaker 1>with Russia and China did use crypto devices, so the

0:38:50.400 --> 0:38:53.640
<v Speaker 1>CIA was able to learn a lot about operations going

0:38:53.680 --> 0:38:57.520
<v Speaker 1>on in Russia and China indirectly through that means. This

0:38:57.600 --> 0:38:59.800
<v Speaker 1>is also a good time to point out a parallel

0:38:59.840 --> 0:39:04.120
<v Speaker 1>in our daily lives, which is that even if the

0:39:04.320 --> 0:39:09.720
<v Speaker 1>content of our messages is safe, the act of sending

0:39:09.760 --> 0:39:13.640
<v Speaker 1>messages can sometimes provide enough information for people to draw

0:39:13.760 --> 0:39:20.440
<v Speaker 1>some pretty accurate conclusions. It shows us that metadata is

0:39:20.520 --> 0:39:25.719
<v Speaker 1>really an important thing to remember. Metadata is the information

0:39:26.120 --> 0:39:29.680
<v Speaker 1>about information, and sometimes you don't need to know the

0:39:29.800 --> 0:39:35.200
<v Speaker 1>content of something in order to draw some pretty damaging

0:39:35.480 --> 0:39:39.320
<v Speaker 1>or valuable conclusions. I guess it all depends upon your perspective.

0:39:40.000 --> 0:39:42.359
<v Speaker 1>So this is kind of an example of that that

0:39:42.400 --> 0:39:46.000
<v Speaker 1>even though Russia and China weren't using crypto devices, countries

0:39:46.000 --> 0:39:48.120
<v Speaker 1>that were dealing with Russia and China were, and that

0:39:48.160 --> 0:39:50.960
<v Speaker 1>meant the CIA could read at least that side of

0:39:51.040 --> 0:39:55.200
<v Speaker 1>the messages. In nineteen eighty one, Saudi Arabia would become

0:39:55.239 --> 0:39:58.920
<v Speaker 1>the biggest crypto customer and it would play a very

0:39:58.960 --> 0:40:02.040
<v Speaker 1>important role. The crypto technology play a very important role

0:40:02.040 --> 0:40:05.520
<v Speaker 1>in the Middle East. This also leads to a point

0:40:05.520 --> 0:40:09.439
<v Speaker 1>in the Washington Post article where the authors state that

0:40:10.840 --> 0:40:14.319
<v Speaker 1>it's kind of an open question as to how much

0:40:14.440 --> 0:40:19.160
<v Speaker 1>the CIA knew about different operations around the world throughout

0:40:19.160 --> 0:40:23.279
<v Speaker 1>this time and what the agency did or didn't do

0:40:24.040 --> 0:40:27.160
<v Speaker 1>in preparation for those events, like whether or not they

0:40:27.160 --> 0:40:29.440
<v Speaker 1>should have acted in some cases, like if they were

0:40:29.480 --> 0:40:32.560
<v Speaker 1>aware of an assassination attempt, did they do anything to

0:40:32.600 --> 0:40:36.160
<v Speaker 1>prevent that or to let anyone know? And if not,

0:40:36.800 --> 0:40:39.520
<v Speaker 1>was it just because they were worried about compromising the

0:40:39.560 --> 0:40:44.160
<v Speaker 1>fact that they knew about this information. At what point

0:40:44.640 --> 0:40:47.440
<v Speaker 1>does the value go away from knowing information if you

0:40:47.480 --> 0:40:49.960
<v Speaker 1>don't act on that information. These are big questions that

0:40:50.000 --> 0:40:52.400
<v Speaker 1>are not answered in the article, by the way, and

0:40:52.480 --> 0:40:56.480
<v Speaker 1>they bring up a lot of deep ethical problems with

0:40:56.520 --> 0:41:01.080
<v Speaker 1>what was going on. So crypto would also receive a

0:41:01.080 --> 0:41:03.520
<v Speaker 1>lot of direction from the CIA and from B and

0:41:03.600 --> 0:41:10.080
<v Speaker 1>D to actively try and disparage competitors, to essentially run

0:41:10.200 --> 0:41:16.640
<v Speaker 1>marketing campaigns that said, you know, cryptography devices from such

0:41:16.680 --> 0:41:19.759
<v Speaker 1>and such a company are total crap, don't buy them.

0:41:19.960 --> 0:41:23.959
<v Speaker 1>Come to us by our stuff, we are secure. They

0:41:24.239 --> 0:41:29.279
<v Speaker 1>also were encouraged to bribe government officials to adopt crypto tech.

0:41:29.560 --> 0:41:34.080
<v Speaker 1>So there's some pretty awful stories about crypto executives doing

0:41:34.120 --> 0:41:36.920
<v Speaker 1>all sorts of stuff in order to you know, bribe

0:41:37.040 --> 0:41:41.040
<v Speaker 1>governments from all over the world to adopt crypto technology.

0:41:41.680 --> 0:41:49.600
<v Speaker 1>Skeezy skeezee stuff really makes me proud. US President Ronald

0:41:49.600 --> 0:41:54.040
<v Speaker 1>Reagan inadvertently revealed that the US had intercepted and decrypted

0:41:54.080 --> 0:41:58.200
<v Speaker 1>communications out of a Libyan embassy in East Berlin to

0:41:58.320 --> 0:42:02.120
<v Speaker 1>Tripoli and that tiptf Libya that something was up right,

0:42:02.239 --> 0:42:07.400
<v Speaker 1>that America somehow was able to decrypt messages, and considering

0:42:07.520 --> 0:42:11.239
<v Speaker 1>the company they were relying upon for their cryptography, that

0:42:11.360 --> 0:42:16.520
<v Speaker 1>started to raise some doubts about Crypto's authenticity, and not

0:42:16.640 --> 0:42:21.320
<v Speaker 1>just with Libya, other countries took notice too. Employees at Crypto, meanwhile,

0:42:21.440 --> 0:42:25.160
<v Speaker 1>didn't know about the arrangement right. They were working under

0:42:25.200 --> 0:42:31.600
<v Speaker 1>the assumption that they were actually making genuine, reliable cryptography equipment,

0:42:32.000 --> 0:42:35.360
<v Speaker 1>and occasionally an employee might look at something and say, huh,

0:42:35.400 --> 0:42:39.320
<v Speaker 1>this is weird based upon what I know. This algorithm

0:42:39.320 --> 0:42:43.440
<v Speaker 1>we're using or this system we're using has vulnerabilities, their

0:42:43.560 --> 0:42:46.960
<v Speaker 1>problems with it. We should fix those before we ship this,

0:42:47.480 --> 0:42:50.839
<v Speaker 1>because we could make it more secure. They would get

0:42:51.000 --> 0:42:54.000
<v Speaker 1>discouraged from doing that, they would be told not to

0:42:54.040 --> 0:42:58.440
<v Speaker 1>implement solutions. In one case that went much further than that,

0:42:59.520 --> 0:43:05.240
<v Speaker 1>there was an employee named Peter Fritiger who was very

0:43:05.440 --> 0:43:10.400
<v Speaker 1>frustrated with what was going on. He felt that Crypto

0:43:10.560 --> 0:43:16.799
<v Speaker 1>was just being complacent or maybe negligent, and not responding

0:43:16.840 --> 0:43:21.560
<v Speaker 1>to very real concerns that Fritiger had with clients in Damascus.

0:43:22.080 --> 0:43:25.640
<v Speaker 1>So his clients in Damascus were complaining about their stuff.

0:43:25.680 --> 0:43:29.080
<v Speaker 1>So he went to Damascus and he fixed their Crypto equipment.

0:43:29.440 --> 0:43:32.240
<v Speaker 1>In other words, he removed the vulnerabilities that had been

0:43:32.680 --> 0:43:37.600
<v Speaker 1>engineered to go into this stuff. And the Crypto CEO

0:43:37.840 --> 0:43:41.080
<v Speaker 1>at the time would fire Fritiger as a result, because

0:43:41.320 --> 0:43:45.239
<v Speaker 1>Fritiger had messed things up. He had actually made what

0:43:45.320 --> 0:43:48.480
<v Speaker 1>was supposed to be a secure system and actual secure system.

0:43:48.680 --> 0:43:53.279
<v Speaker 1>Of course, he didn't know that that was against the

0:43:53.320 --> 0:43:58.080
<v Speaker 1>goals of the operation itself, and the CIA got very

0:43:58.120 --> 0:44:01.480
<v Speaker 1>mad at the CEO for Crypto at that point, saying

0:44:01.520 --> 0:44:03.759
<v Speaker 1>that he should have found a way to sort of

0:44:03.800 --> 0:44:06.919
<v Speaker 1>bring Friutiture in under the fold to smooth things over,

0:44:07.040 --> 0:44:11.080
<v Speaker 1>rather than fire him because it brought undue scrutiny to

0:44:11.160 --> 0:44:15.600
<v Speaker 1>Crypto and its activities. Crypto also hired an electrical engineer

0:44:15.920 --> 0:44:20.680
<v Speaker 1>named Mindia k. Flish and I'm sure I'm butchering these names,

0:44:20.719 --> 0:44:25.520
<v Speaker 1>and I do apologize that also upset the NSSA, this time,

0:44:25.560 --> 0:44:28.640
<v Speaker 1>not the CIA. But this NSSA because NSA knew about

0:44:28.640 --> 0:44:33.360
<v Speaker 1>this electrical engineer, and they said, she is way too smart,

0:44:33.840 --> 0:44:36.320
<v Speaker 1>she's going to figure out something's going on. You should

0:44:36.360 --> 0:44:40.760
<v Speaker 1>not hire her. But Crypto hired her because was brilliant

0:44:41.040 --> 0:44:45.239
<v Speaker 1>and was seen as a valuable asset. Turns out she

0:44:45.400 --> 0:44:48.360
<v Speaker 1>was brilliant. She still is brilliant, and she kept trying

0:44:48.400 --> 0:44:53.000
<v Speaker 1>to initiate fixes and improvements because she kept finding weaknesses

0:44:53.040 --> 0:44:57.080
<v Speaker 1>and vulnerabilities in the systems, but she was always discouraged

0:44:57.200 --> 0:45:01.600
<v Speaker 1>from actually implementing solutions, and she wondered what was going on,

0:45:02.520 --> 0:45:05.160
<v Speaker 1>but she was a little worried about speaking up because

0:45:05.160 --> 0:45:09.360
<v Speaker 1>she wasn't sure exactly what the extent was. The company

0:45:09.719 --> 0:45:13.680
<v Speaker 1>would actually produce a machine using an algorithm she had

0:45:13.719 --> 0:45:19.440
<v Speaker 1>designed that the NSA could not crack, So the NSA

0:45:19.800 --> 0:45:23.560
<v Speaker 1>reached out to the CIA, and the CIA ordered the

0:45:23.800 --> 0:45:28.360
<v Speaker 1>company Crypto, to stop the manufacturing process, saying, we can't

0:45:28.440 --> 0:45:32.520
<v Speaker 1>produce these machines because we can't crack the code. You

0:45:32.680 --> 0:45:36.480
<v Speaker 1>got to break it. So only fifty or so of

0:45:36.560 --> 0:45:40.040
<v Speaker 1>these machines were actually manufactured. The company wind up selling

0:45:40.040 --> 0:45:44.000
<v Speaker 1>those to banks because the thought was, well, banks have

0:45:44.080 --> 0:45:46.520
<v Speaker 1>a need for security and we don't really need to

0:45:46.560 --> 0:45:51.200
<v Speaker 1>snoop on them. That's not where our concern is. But

0:45:51.719 --> 0:45:54.359
<v Speaker 1>from now on, when you make this device, make it

0:45:54.400 --> 0:45:57.879
<v Speaker 1>with the algorithm that's broken on purpose because we want

0:45:57.880 --> 0:46:03.560
<v Speaker 1>to be able to crack those codes. That's pretty dodgy anyway.

0:46:03.920 --> 0:46:07.719
<v Speaker 1>There was also a mathematics professor from Stockholm whose name

0:46:07.840 --> 0:46:12.720
<v Speaker 1>I would butcher terribly. He actually studied in the United States,

0:46:12.800 --> 0:46:16.680
<v Speaker 1>and his American family, like me, would have trouble saying

0:46:16.719 --> 0:46:21.400
<v Speaker 1>his name, so they called him Henry Henry Vindman. He

0:46:21.520 --> 0:46:25.759
<v Speaker 1>was brought in to craft more sophisticated but vulnerable algorithms,

0:46:25.800 --> 0:46:31.680
<v Speaker 1>so he was actually told about the real relationship between

0:46:31.800 --> 0:46:35.680
<v Speaker 1>the CIA and then B and D and crypto. He

0:46:35.840 --> 0:46:39.520
<v Speaker 1>was given the inside scoop and asked to become part

0:46:39.520 --> 0:46:43.359
<v Speaker 1>of the team. And his purpose was to design algorithms

0:46:43.680 --> 0:46:49.560
<v Speaker 1>that looked really super secure but secretly weren't. So he

0:46:49.800 --> 0:46:53.640
<v Speaker 1>was trying to make stuff that appeared to be more

0:46:53.680 --> 0:46:57.279
<v Speaker 1>on the up and up, but in fact had vulnerabilities

0:46:57.280 --> 0:47:01.720
<v Speaker 1>built into it, and meanwhile to have those vulnerabilities designed

0:47:01.760 --> 0:47:05.400
<v Speaker 1>in such a way that it created plausible deniability. In

0:47:05.440 --> 0:47:08.600
<v Speaker 1>other words, if someone found the vulnerability, you could say, oh,

0:47:08.760 --> 0:47:12.200
<v Speaker 1>that's due to human error or it was an implementation error,

0:47:12.200 --> 0:47:15.040
<v Speaker 1>but it was not put there on purpose, even though

0:47:15.080 --> 0:47:19.840
<v Speaker 1>it toats was. The CIA used Crypto communications to suss

0:47:19.880 --> 0:47:24.160
<v Speaker 1>out where Manuel Noriega was based off communications from the Vatican.

0:47:24.480 --> 0:47:27.319
<v Speaker 1>They intercepted those communications, decoded them, and were able to

0:47:27.360 --> 0:47:31.760
<v Speaker 1>find Noriega as a result. In nineteen ninety two, Iran

0:47:32.200 --> 0:47:37.960
<v Speaker 1>arrested a Crypto salesman named Hans Buehler, and Buehler didn't

0:47:38.000 --> 0:47:41.640
<v Speaker 1>know about the relationship between Crypto and the CIA or

0:47:41.680 --> 0:47:44.160
<v Speaker 1>the B and D. He had no knowledge of any

0:47:44.200 --> 0:47:47.880
<v Speaker 1>of that, so he was literally an innocent salesman who

0:47:48.000 --> 0:47:54.440
<v Speaker 1>thought he was selling legit cryptographic equipment. Iran had figured

0:47:54.440 --> 0:47:57.120
<v Speaker 1>out something was going on. They had been suspicious ever

0:47:57.200 --> 0:48:01.160
<v Speaker 1>since that incident with Libya I had mentioned, and so

0:48:01.480 --> 0:48:07.040
<v Speaker 1>they arrested him and they essentially tortured him for nine months.

0:48:08.640 --> 0:48:13.120
<v Speaker 1>The Iran demanded a one million dollar ransom from Crypto,

0:48:13.400 --> 0:48:15.640
<v Speaker 1>and the company did pay it. The CIA did not

0:48:15.920 --> 0:48:20.120
<v Speaker 1>chip in because the CIA has a policy against paying ransoms.

0:48:20.840 --> 0:48:24.680
<v Speaker 1>We don't negotiate with terrorists, is the way America would

0:48:24.680 --> 0:48:28.080
<v Speaker 1>put it. So this guy suffered for nine months in

0:48:28.080 --> 0:48:32.080
<v Speaker 1>captivity before Crypto would pay the ransom and get him back,

0:48:32.320 --> 0:48:35.600
<v Speaker 1>and he legit didn't know anything. He didn't know that

0:48:35.840 --> 0:48:39.640
<v Speaker 1>the relationship existed, but he certainly suspected it by the

0:48:39.680 --> 0:48:43.239
<v Speaker 1>time he was released, and he was worried about the

0:48:43.320 --> 0:48:46.920
<v Speaker 1>fact that this foreign government seemed to know more about

0:48:46.920 --> 0:48:50.279
<v Speaker 1>the company he was working for than he did. He

0:48:50.360 --> 0:48:53.839
<v Speaker 1>ended up going to the press and talking about his

0:48:53.960 --> 0:48:58.239
<v Speaker 1>experiences and it caused a bit of a stir in Europe.

0:48:58.360 --> 0:49:02.279
<v Speaker 1>The CIA would actually refer to this entire incident with

0:49:02.360 --> 0:49:06.680
<v Speaker 1>a code name. That code name was Hydra, so that's fun.

0:49:07.200 --> 0:49:12.240
<v Speaker 1>Around that same time, Germany was reunified, right the Soviet

0:49:12.280 --> 0:49:16.480
<v Speaker 1>Union fol East Germany and West Germany unified into Germany.

0:49:16.760 --> 0:49:19.840
<v Speaker 1>The Berlin Wall came down, and it was around that

0:49:19.920 --> 0:49:23.160
<v Speaker 1>same time that the B and D felt that Crypto's

0:49:23.239 --> 0:49:27.480
<v Speaker 1>usefulness had pretty much expired, that now it was more

0:49:27.560 --> 0:49:32.640
<v Speaker 1>of a risk that if the full extent of B

0:49:32.719 --> 0:49:36.439
<v Speaker 1>and D's involvement in Crypto's activities were known, that could

0:49:36.480 --> 0:49:39.600
<v Speaker 1>put Germany at risk, and so they ended up selling

0:49:39.640 --> 0:49:43.760
<v Speaker 1>off their interest in Crypto to the CIA for around

0:49:43.880 --> 0:49:49.359
<v Speaker 1>seventeen million dollars. So at that point forward, Crypto operated

0:49:49.480 --> 0:49:56.680
<v Speaker 1>as a CIA backed operation secretly. But yeah, CIA had

0:49:56.680 --> 0:50:01.000
<v Speaker 1>full ownership from around nineteen ninety three until twenty eighteen.

0:50:01.120 --> 0:50:04.120
<v Speaker 1>That's when CIA would liquidate the company and sold it

0:50:04.160 --> 0:50:08.839
<v Speaker 1>off to two other companies. The reason they did that

0:50:09.440 --> 0:50:11.920
<v Speaker 1>is that by the time twenty eighteen rolled around, the

0:50:12.120 --> 0:50:16.080
<v Speaker 1>cryptographic community was very different. It no longer was so

0:50:16.200 --> 0:50:21.680
<v Speaker 1>dependent upon standalone machines, electronic or otherwise. A lot of

0:50:21.960 --> 0:50:26.960
<v Speaker 1>solutions are software based or web based. They're not based

0:50:27.040 --> 0:50:33.279
<v Speaker 1>on physical equipment. So the usefulness of Crypto as a

0:50:33.320 --> 0:50:37.560
<v Speaker 1>company had pretty much gone out the window. It had

0:50:37.560 --> 0:50:42.840
<v Speaker 1>provided the CIA with a ton of information, but they were,

0:50:43.000 --> 0:50:45.359
<v Speaker 1>you know, there's no need to keep it running, so

0:50:45.400 --> 0:50:51.920
<v Speaker 1>they sold it off for parts essentially. And you know,

0:50:52.200 --> 0:50:55.479
<v Speaker 1>part of me says, this is spy stuff. Of course,

0:50:55.480 --> 0:50:57.839
<v Speaker 1>spies are going to be sneaky. That's what spies do.

0:50:58.400 --> 0:51:01.359
<v Speaker 1>Spies operate in a way where they are trying to

0:51:01.480 --> 0:51:04.120
<v Speaker 1>avoid detection while they try to figure out what everyone

0:51:04.120 --> 0:51:07.880
<v Speaker 1>else knows. That is the nature of spying, and everybody

0:51:08.000 --> 0:51:12.040
<v Speaker 1>does it at the same time. There's something really sinister

0:51:12.760 --> 0:51:19.719
<v Speaker 1>about secretly owning a security firm and using it to

0:51:20.920 --> 0:51:23.719
<v Speaker 1>do the opposite of what the security firm says. It's

0:51:23.760 --> 0:51:27.440
<v Speaker 1>doing right. It says it's protecting secrets, but in reality,

0:51:27.960 --> 0:51:30.879
<v Speaker 1>it's leaving those secrets open for people to see. Now,

0:51:31.560 --> 0:51:34.120
<v Speaker 1>I mentioned Huawei at the beginning of this episode, and

0:51:34.160 --> 0:51:36.719
<v Speaker 1>the reason I did that is because, again around the

0:51:36.760 --> 0:51:39.520
<v Speaker 1>same time that this story was breaking, we were hearing

0:51:39.560 --> 0:51:44.359
<v Speaker 1>about how Huawei, the Chinese company telecommunications company, has had

0:51:44.600 --> 0:51:50.000
<v Speaker 1>backdoor access to networks that it has rolled out for

0:51:50.120 --> 0:51:53.840
<v Speaker 1>a decade. So Huawei makes all sorts of telecommunications equipment,

0:51:53.920 --> 0:51:58.120
<v Speaker 1>including components for networks. They are a leading provider for

0:51:58.200 --> 0:52:01.360
<v Speaker 1>five G components, for example, and there's been a concern

0:52:02.280 --> 0:52:05.240
<v Speaker 1>around much of the world, but particularly in the United States,

0:52:05.800 --> 0:52:08.640
<v Speaker 1>that this would mean that Huawei as a company would

0:52:08.680 --> 0:52:12.080
<v Speaker 1>have at least some capability of snooping on communications that

0:52:12.120 --> 0:52:17.279
<v Speaker 1>go across those networks. And since Huawei has some connections

0:52:17.719 --> 0:52:24.400
<v Speaker 1>to the communist government of China, because China requires companies

0:52:24.440 --> 0:52:27.480
<v Speaker 1>that operate in China to have this connection, that that

0:52:27.520 --> 0:52:31.600
<v Speaker 1>would mean that those networks would be used specifically as

0:52:31.800 --> 0:52:35.400
<v Speaker 1>surveillance tools. And in America you can kind of understand

0:52:35.560 --> 0:52:39.640
<v Speaker 1>where they're coming from, because that's what Americans do. Like,

0:52:39.719 --> 0:52:43.400
<v Speaker 1>if you're the one who's spying on everybody, you probably

0:52:43.440 --> 0:52:46.840
<v Speaker 1>are really paranoid about everyone spying on you. It's just

0:52:46.960 --> 0:52:50.800
<v Speaker 1>kind of how it works. Also, again, that report showed

0:52:51.000 --> 0:52:54.279
<v Speaker 1>that for ten years, Huawei actually did have that capability.

0:52:54.320 --> 0:52:56.919
<v Speaker 1>Whether they did anything with it or not is still

0:52:56.920 --> 0:53:00.600
<v Speaker 1>an open question. But with Huawei, the story goes that

0:53:00.640 --> 0:53:04.680
<v Speaker 1>they were building in these backdoor access channels for law

0:53:04.760 --> 0:53:07.840
<v Speaker 1>enforcement officials. You know, law enforcement wants to have that

0:53:07.920 --> 0:53:11.319
<v Speaker 1>kind of access so that if they're conducting investigation, they

0:53:11.320 --> 0:53:16.120
<v Speaker 1>can look into communications going between various suspects so that

0:53:16.200 --> 0:53:21.080
<v Speaker 1>they can better do their investigations. The problem is that

0:53:21.160 --> 0:53:23.520
<v Speaker 1>Huawei was not just building these in for law enforcement,

0:53:23.640 --> 0:53:27.680
<v Speaker 1>but was retaining its own access to those channels. And again,

0:53:27.719 --> 0:53:30.200
<v Speaker 1>whether it was using it or not, I don't know,

0:53:30.680 --> 0:53:33.719
<v Speaker 1>but the story goes that they were actually retaining that ability.

0:53:34.440 --> 0:53:37.520
<v Speaker 1>And this leads me to another point I want to

0:53:37.560 --> 0:53:42.399
<v Speaker 1>make before I conclude, which is that backdoor channels are

0:53:42.440 --> 0:53:47.120
<v Speaker 1>always a terrible idea, always, always, always, always They inherently

0:53:47.200 --> 0:53:50.520
<v Speaker 1>make systems less secure. So if your job is to

0:53:50.520 --> 0:53:54.080
<v Speaker 1>make a secure system, building in a way to bypass

0:53:54.160 --> 0:53:57.760
<v Speaker 1>that security is you might as well not have any security.

0:53:57.800 --> 0:54:01.480
<v Speaker 1>It's a terrible idea. I get it. Why law enforcement

0:54:01.560 --> 0:54:05.120
<v Speaker 1>and intelligence agencies want it because information is valuable and

0:54:05.160 --> 0:54:08.600
<v Speaker 1>getting access to the information could mean the difference between

0:54:08.840 --> 0:54:13.960
<v Speaker 1>life or death in some cases really can. But then

0:54:14.239 --> 0:54:18.839
<v Speaker 1>you know, if you have those backdoor channels, it means

0:54:18.880 --> 0:54:21.840
<v Speaker 1>that you don't have to go through the whole security process,

0:54:21.840 --> 0:54:24.400
<v Speaker 1>and it means that someone else might potentially discover that

0:54:24.840 --> 0:54:28.399
<v Speaker 1>and exploit it. So one, you've got the danger of

0:54:28.920 --> 0:54:33.719
<v Speaker 1>the authorized parties abusing this power. Right, you've got the

0:54:34.320 --> 0:54:38.879
<v Speaker 1>potential for an agency committing overreach like we've heard about

0:54:38.880 --> 0:54:43.000
<v Speaker 1>the NSSAY and how that agency was collecting way more

0:54:43.000 --> 0:54:47.320
<v Speaker 1>information than they should have been able to, including information

0:54:47.440 --> 0:54:51.160
<v Speaker 1>from people that weren't under any direct surveillance, and how

0:54:51.200 --> 0:54:54.360
<v Speaker 1>that can be abused. That's a terrible thing. So you

0:54:54.400 --> 0:54:57.359
<v Speaker 1>don't want that capability. You don't want the ability of

0:54:57.480 --> 0:55:02.200
<v Speaker 1>some agency that had had author backdoor access to abuse

0:55:02.239 --> 0:55:05.480
<v Speaker 1>that power. You also don't want some third party that

0:55:05.640 --> 0:55:09.160
<v Speaker 1>is not authorized at all finding out about that back

0:55:09.239 --> 0:55:12.080
<v Speaker 1>channel and figuring out how to access it, because now

0:55:12.160 --> 0:55:16.400
<v Speaker 1>your secure system has no security. So I guess the

0:55:16.760 --> 0:55:20.640
<v Speaker 1>end message I want to give everybody is protect yourself

0:55:20.680 --> 0:55:23.840
<v Speaker 1>as best you can, which is increasingly difficult when we

0:55:23.880 --> 0:55:28.200
<v Speaker 1>don't know necessarily who is behind the systems that are

0:55:28.200 --> 0:55:32.800
<v Speaker 1>actually making the security we depend upon. Another great example

0:55:32.880 --> 0:55:36.319
<v Speaker 1>is people have pointed out is should we trust the

0:55:37.120 --> 0:55:41.319
<v Speaker 1>security company Kaspersky, which comes from Russia, or is it

0:55:41.360 --> 0:55:44.799
<v Speaker 1>possible that that could be a state backed operation that

0:55:45.080 --> 0:55:50.600
<v Speaker 1>is slowly or quietly sewing in vulnerabilities from people who

0:55:50.640 --> 0:55:55.000
<v Speaker 1>are using its products. I have not seen any specific

0:55:55.040 --> 0:55:58.360
<v Speaker 1>reports on that. I'm just seeing people ask that question.

0:55:58.880 --> 0:56:01.440
<v Speaker 1>But that leads us to start asking questions about everything.

0:56:02.080 --> 0:56:04.719
<v Speaker 1>Probably not a bad idea, but it starts to, you know,

0:56:04.760 --> 0:56:08.360
<v Speaker 1>it starts to create this system where we're not trusting anything,

0:56:09.000 --> 0:56:11.719
<v Speaker 1>and at the end of the day, you either have

0:56:11.880 --> 0:56:15.480
<v Speaker 1>to figure out you've got to trust somebody, or you

0:56:15.520 --> 0:56:19.120
<v Speaker 1>got to just kind of disengage, or I guess you

0:56:19.239 --> 0:56:21.640
<v Speaker 1>just resign yourself that all of your stuff is going

0:56:21.719 --> 0:56:25.840
<v Speaker 1>to be findable and readable by everyone at some point

0:56:25.920 --> 0:56:30.960
<v Speaker 1>or another. Happy Days. I hope you enjoyed that episode

0:56:30.960 --> 0:56:35.520
<v Speaker 1>of tech Stuff When Secrets Aren't Secret. Back from February seventeenth,

0:56:35.560 --> 0:56:40.200
<v Speaker 1>twenty twenty. Just a quick update. Tomorrow we're going to

0:56:40.280 --> 0:56:43.360
<v Speaker 1>have a special episode of a different podcast published in

0:56:43.400 --> 0:56:47.120
<v Speaker 1>the tech Stuff feed is called Technically Speaking, and I

0:56:47.160 --> 0:56:50.160
<v Speaker 1>hope that you enjoy it. I will be back next

0:56:50.200 --> 0:56:52.919
<v Speaker 1>week with all new episodes, and I hope you're all well,

0:56:52.960 --> 0:57:01.840
<v Speaker 1>and I'll talk to you again really soon. Tech Stuff

0:57:01.960 --> 0:57:06.480
<v Speaker 1>is an iHeartRadio production. For more podcasts from iHeartRadio, visit

0:57:06.520 --> 0:57:10.040
<v Speaker 1>the iHeartRadio app, Apple Podcasts, or wherever you listen to

0:57:10.080 --> 0:57:11.040
<v Speaker 1>your favorite shows.