Cracking the Code: The Enigma Story | Chaos Lever

[00:00:00.09]
Ned: You know what I do like? Quality guacamole.

[00:00:06.29]
Chris: Yeah, I like reverse proxying into virtual machines as well.

[00:00:12.02]
Ned: Who doesn't? It's such an effective platform. And open source. Look at that. We're on the same wavelength here. There's nothing more the delicious than open source guacamole.

[00:00:26.29]
Chris: That should be a T-shirt, a deeply, deeply confusing T-shirt.

[00:00:42.01]
Ned: Hello, Alleged Human, and welcome to the Chaos Lever podcast. My name is Ned, and I'm definitely not a robot. I'm a real human person who wears T-shirts sometimes and also walks around and loves tortilla chips. I don't know. It got away from me. T-shirts, that's the point, Chris. With me is Chris, who's also here and also not wearing a T-shirt. We are terrible at this.

[00:01:08.07]
Chris: It's the middle of winter.

[00:01:11.14]
Ned: Excuse is excuse. I'm wearing a short sleeve, at least.

[00:01:14.22]
Chris: That's because you're a crazy person and it's slightly warmer than it should be in your dungeon.

[00:01:19.28]
Ned: That is true. My baseboard heat is wildly effective. I mean, it dries out my entire sinus area, but I'm warm.

[00:01:30.15]
Chris: It keeps you and the mold that it grows very toasty.

[00:01:37.14]
Ned: Oh, now I have to go look for mold. After the episode, of course, because we have very important things to talk about, don't we?

[00:01:47.07]
Chris: We do.

[00:01:50.17]
Ned: We are- Cheese. Cheese?

[00:01:54.15]
Chris: I mean, I'm not opposed. We could just spend 45 minutes listing off various types of cheese.

[00:02:02.07]
Ned: I don't know if I could do that for 45 straight minutes.

[00:02:06.18]
Chris: No, I only know four cheeses.

[00:02:08.29]
Ned: So we just run through those four cheeses again and again?

[00:02:12.26]
Chris: That could work.

[00:02:14.22]
Ned: We'll start with Chedder.

[00:02:16.19]
Chris: It could be one of those anti-humor things.

[00:02:19.08]
Ned: Yes. Is that one of those things where if we did it long enough, it would become funny again?

[00:02:27.02]
Chris: I think that's the idea, but more than More likely, if we did it long enough, people would just go home.

[00:02:35.03]
Ned: Where are they now?

[00:02:36.27]
Chris: I don't know. I'm not the podcast listening audience police.

[00:02:42.16]
Ned: We don't keep tabs on you. Or do we?

[00:02:45.26]
Chris: Not all of you.

[00:02:49.22]
Ned: That's important. Okay, so what are we actually going to talk about today? As if you didn't already know, you looked at the title Wonderful Listener.

[00:02:59.11]
Chris: We're going to talk about the history of cryptography part, and I can't believe I'm saying this, three.

[00:03:07.25]
Ned: Three of a thousand? Yes.

[00:03:10.16]
Chris: Three of is a good way to put it because my God, You chose this for yourself.

[00:03:18.03]
Ned: It's true.

[00:03:19.04]
Chris: It's true. And if people remember, I actually thought I was going to do all this in one episode, which was hilariously wrong.

[00:03:27.23]
Ned: You're adorable.

[00:03:30.12]
Chris: So anyway, a quick recap. In part one, we went back to the beginning of time, basically, if not further, which admittedly might have been a mistake. However, did the Big Bang have a secret code in it? You'll have to listen to find out. I can't tell you the episode number because Ned doesn't let me talk about that episode numbers anymore. In any event, the Big Bang may or may not have had secret codes. The ancient Egyptians definitely did. So did the Greeks as well as the Romans. So did a bunch of people in the Middle Ages, all of them building new and exciting codes on top of the codes that came before them. Simultaneous to the codes getting more sophisticated, the code breakers got more sophisticated. In part two, we continued this historical trend, focusing more this time on the Napoleonic Wars, specifically the adventures or misadventures in Spain, and how an English codebreaker more or less turned the tide of that part of the war, allowing the Duke of Wellington to win a decisive battle at a place called Salamanca.

[00:04:43.01]
Ned: And thus have a delicious dish named after him. I'm going with that being true. Also a small lizard.

[00:04:51.13]
Chris: So a couple of fun facts about that story. First one that I learned, when the Duke of Wellington won the Battle of Salamanca, he wasn't the Duke of Wellington yet. In 1812, he was only the Earl of Wellington, which does not have nearly the same ring to it.

[00:05:08.27]
Ned: It does not.

[00:05:10.20]
Chris: He was promoted, I guess, to Duke in 1814, which I guess- Is that what they call it when your title gets enhanced? Elevated?

[00:05:26.06]
Ned: We'll workshop it. It's fine.

[00:05:27.11]
Chris: Yeah, I don't know. This is some seriously dumb rich people shit that I don't have time for.

[00:05:32.15]
Ned: Fair.

[00:05:33.13]
Chris: Anyway. Also, after the war concluded, Wellington went ahead and just forgot all about his code-breaking superstar, George Scovel. That George Scovel was for a time running the risk of being destitute. Oh. He wrote a letter to Wellington asking him for help. Wellington never replied. Another member of Wellington's staff eventually came to the rescue, giving Scovel a decently paying if dead-end job as the head of a military school. Wellington, for his part, for the rest of his political career, claimed that it was in fact the whole staff working together that cracked the codes, never mentioning Scoville by name. Class act all the way. Wow. Yeah. I read a whole ass book about this. I was only going to use it for one chapter, and I got angry and read the whole thing. And yeah, I'm still mad about I love that.

[00:06:31.10]
Ned: I love that you anger-read a whole book.

[00:06:38.04]
Chris: We finished part two talking about the Civil War. That's the one in America. And how Basically, the same kinds of codes had been used there, only with a clever tool that was pocketable and allowed the decodes and encodes to happen faster. That was it for part two.

[00:06:57.21]
Ned: Yeah, and if people watched the YouTube video, I took the time to put visuals in it, and I feel like you're probably going to make me do that again.

[00:07:08.25]
Chris: We have a YouTube?

[00:07:11.16]
Ned: Yes. For those who don't know, these episodes are also published on YouTube, and you can see our very beautiful faces talk about things. But in the particular case of that episode, you also got to see graphics of what that pocketable device looked like. That was good. I did a good thing.

[00:07:33.16]
Chris: Based on this new information, yeah, I'm going to make you do that again.

[00:07:38.07]
Ned: Excellent.

[00:07:40.21]
Chris: One more aside, it was pointed out to me that in episodes one and two, what I've been talking about has not actually been encryption, per se. Now, it is picking apart vocabulary, but I think it bears digging into. What we've been talking about is codes and in ciphering.

[00:08:02.18]
Ned: Okay.

[00:08:04.22]
Chris: A cipher transforms readable text into unreadable text using some an algorithm. This is usually done on a letter-by-letter or word-by-word basis with some other complications thrown in. For example, if you sent a text message to a friend that said, I'll meet you at 1, 2, 3, 4 right before noon 5, 6, 7, 8. This is a very simple cipher. You have created a dictionary of place names and calendar dates. The two of you know those can be substituted in so that anybody eavesdropping would be clueless as to where or when you were talking about.

[00:08:48.25]
Ned: Sure.

[00:08:49.16]
Chris: This is a definition of encypherment. The more complicated versions of this substitute every single letter, like the Caesar cipher that we talked about in part one, or the more complex Vignère cipher we talked about in part two. Now, one thing that's important about a cipher, utilizing these codes and codebooks, is that you don't have to encypher every single word. Like the example that I just used. And oftentimes, people wouldn't bother doing that. Encoding and decoding or deciphering and deciphering the full message would take a lot longer. In a lot of these cases, this was at the time with pen and paper. So there was no reason to do 100% decipherment in people's minds. You only decipher the text that is important or sensitive or what have you. So Here's a real-life example taken directly from French communications in the Spain campaign of 1811. This is the Vigneer cipher I was talking about in episode 2.

[00:09:55.02]
Ned: Okay.

[00:09:56.11]
Chris: I am making hast to pass on the content It means 2, 25, 13, 8, 9, 38, 19. I could go on. There's a lot of numbers.

[00:10:07.19]
Ned: Okay.

[00:10:08.19]
Chris: Then it goes back into clear text. Who has ordered me to open communications with you?

[00:10:15.15]
Ned: Okay. I see what you mean.

[00:10:17.29]
Chris: There's a lot of the message that you can read, but there are pieces of it that are encyphered. Idea being that this is the secret part that you don't want people to know. Now, in the In the case of this particular example, this is an example of why this is not a great idea. Because what you get when you have some things in ciphered and some things in plain text is a huge amount of context clues. Code breakers can use that context clue to try to infer what the coded part of the message means. In this case, all the numbers that were listed out broke down to were individual letters that spelled out the name of the person that was in charge of this particular army, Essie le Maréchal, Duc de Ragus. There's my French accent. You're all welcome.

[00:11:11.14]
Ned: Well done.

[00:11:12.28]
Chris: This was super dumb because number one, they used his full title. All of those letters, all of that is something that is going to be repeated in these messages. Every time you refer to him, you can't just call him because that would be insulting. But what it does is gives the code breakers an opportunity to latch on to something that comes up over and over and over again and seems like it might be a name.

[00:11:41.19]
Ned: Right.

[00:11:44.15]
Chris: Also, this is something that is totally pointless to encrypt in the first place. The message is going from one army to another. Who do you think they're talking about? A lot of the time, this is the thing that a lot allowed codes to be broken was the sloppiness of the people writing the code.

[00:12:05.20]
Ned: If you decide that you're going to decipher only part of the message, then it's on you to decide what portions of that message is sensitive and which portions you can leave in clear text, but that leaves a lot of room for error.

[00:12:19.20]
Chris: Exactly. I want you to keep those terms in mind. I want you to think about context, repeatability, and the errors that are made by people that are sick and tired of encoding messages. Okay. Because that's going to be important when we talk about the meat of this episode. In order to get to the meat of this episode, I'm going to fast forward in time. I'm basically going to skip World War one. Now, I don't necessarily want to, but it doesn't make sense because honestly, it's a lot more of the same. Codes were still done by hand, if they were done at all. There's a lot of fun stories about Russia. Russia's many major losses came from their penchant for giving up on coding messages and just sending orders to the army in the clear.

[00:13:10.10]
Ned: Bad idea.

[00:13:11.16]
Chris: Also, fun story, the French, at a certain point, tried to help Russia by giving them basically the Vignère codebooks to use. This would have greatly enhanced the encryption capabilities of the Russian army. Unfortunately, the people in charge of the Russian army, corrupt and self-interested as they were, He simply went ahead and just sold those codebooks over to the Germans. You can't make this stuff up, kids.

[00:13:37.27]
Ned: Amazing.

[00:13:40.07]
Chris: So, yeah, on to World War II. All right. End of the thing everybody wanted to hear about in the first place and has been waiting very patiently.

[00:13:50.20]
Ned: So patiently.

[00:13:52.14]
Chris: The Enigma machine.

[00:13:54.18]
Ned: Oh, I thought we were going to talk about cheese.

[00:13:58.04]
Chris: Chetter. Yes. Okay, let's start simple. Ned, you're simple. What do you know about the Enigma machine?

[00:14:13.11]
Ned: It was magic. What I know about the Enigma machine is that it had place for three cylinders that would go in it, and it had five cylinders to choose from. It It basically was like a typewriter, except when you pressed the key, the three cylinders would turn the letter that you pressed into some other letter based off of the pattern. Then when you press the next key, the drums would do the same thing. The same letter would never come out as itself on the other side, and it would rotate through the combinations each time. An L might translate to A, and then it might translate to T next. It wasn't consistent in that regard. Am I close?

[00:15:03.16]
Chris: You're hitting a lot of good points.

[00:15:06.12]
Ned: Yes, I win. Give me the prize.

[00:15:09.10]
Chris: Let's go back in time, though. Before World War II started, did you know that the Enigma machine was not actually a state secret.

[00:15:18.16]
Ned: No.

[00:15:19.14]
Chris: I assume it was. It started its life as a commercially available product.

[00:15:23.17]
Ned: Oh, okay.

[00:15:25.22]
Chris: It was on the market for a decade or more before the rise of the Third Reich. That is an important thing because that is one main reason that a lot of people, worldwide, had one to play with when the war started looming.

[00:15:41.09]
Ned: Oh, okay.

[00:15:41.25]
Chris: The Enigma machine was designed by a German after World War I, who recognized that pen and paper ciphers were just not cutting it in the modern world. You remember above all those complications and how long it took to code and then decode a message?

[00:15:59.05]
Ned: Yeah.

[00:16:00.23]
Chris: Speed is a factor. That was the problem that the enigma was built to solve. You are correct in its basic structure. It was basically a typewriter that you used to write the message. However, there's a lot of complexity with electronics. It had three rotors, not drums. They're called rotors. Each one of which had 26 settings, so 26 numbers, one for each letter of the alphabet. Now, each one of these rotors was wired from one side to the other in a random pattern. So remember, we're doing this all numerically for now. Slot one could be connected to slot five, slot two could be connected to slot 24, et cetera. Each rotor was was named. You would have a rotor number one, rotor number two, rotor number three. Every single rotor number one that was created was wired randomly, but wired in exactly the same way. Every kit went out with three rotors in the beginning, They were randomly wired, but they were consistent from machine to machine. When you use the Enigma machine, you would put the three rotors in in whatever order you wanted. Then you would push them up into whatever number you wanted to start with, and then you would just start typing.

[00:17:20.05]
Chris: The other thing that you said, the rotors are called that for a reason. They rotate. An The circle circuit, when you hit a key, will go from the key into this mechanism with all the rotors in it. So it'll get scrambled one time through the first rotor, another time through the second rotor, another time through the third rotor. Then it hits a reflector and goes backwards again. So it's been scrambled six times. And then it lights up whichever key the cipher text is going to be. Now, once you let go of that key, you've typed a single key and you let go, the first rotor rotates one step. So every time you type a letter, the first rotor or the fast rotor rotates every single type key. Every single 26th key, the rotor next to it clicks one time.

[00:18:22.05]
Ned: Okay.

[00:18:22.29]
Chris: And every time the middle one goes 26 keys, the rotor next to that rotates.

[00:18:29.21]
Ned: Okay. Okay.

[00:18:30.13]
Chris: This is really useful for especially long messages because the key and the alphabet effectively keeps changing, even if it's 10 or 12,000 letters long. And the most important part about all of this is it's done electronically. It's not done by hand with pen and paper. The complexity that we're talking about here is physically possible. You can do it without an enigma machine. It would take you a year to write a shopping list.

[00:19:03.17]
Ned: Right.

[00:19:04.18]
Chris: This was the great innovation of the machine. All you had to do was make sure that you, as the sender, and the person you sent the message to as the receiver, knew the order of the rotors and where to start. Then what would happen is, I say I'm sending the message to you. I set up the rotors and I set them all the Let's just pick some things. Today, the rotor order for January first is 312, and the rotors will be started at positions 22, 5, and 16. You and I know that. Nobody else knows that. Even though the machine is commercially available, they would have to do trial and error on that message to find those rotor settings in order to decode the message. Imagine how long that would take.

[00:20:06.05]
Ned: Like a pretty long amount of time because it would be three factorial times 26 factorial or 26 times 24 times 25. It's a big number. Yes. Number of combinations.

[00:20:23.05]
Chris: That set of combinations is exactly why the Germans were so confident that their messages were not breakable. Now, to be fair, when Germany actually did get on the war footing, they did make the machines even more complicated than that. They went from three rotors to five, like you said. They also added a plug board in the beginning of the machine that was not commercially available that further scrambled the messages. That added even more complexity. We don't have time to go into exactly all of this stuff, how it works and and what the different permutations look like, because there were more than one Enigma machine over time as they got more complicated. But I think you get the idea. If people do want to see what it looks like, though, the Enigma machine Museum is online, and they have a lot of very cool graphics. Just for fun, let's take a look at what a message that was enigmared based on the settings I used above would look like. I've got this fun table that I've been building as we've gone forward. Remember, the rotor settings is what's key. On day one, we have the rotor settings that we talked about above.

[00:21:42.13]
Chris: Day two, we have an agreement that they're going to completely change. So again, even if you break the message from day one, day two, you have to start all over again.

[00:21:52.13]
Ned: Right.

[00:21:53.15]
Chris: So if you look at these messages, an enigma message encoded on day one, an enigma message coded on day two, they look completely different. There is absolutely no commonality to the human eye, or I should say the non-mathematically inclined eye.

[00:22:12.23]
Ned: Yeah.

[00:22:15.17]
Chris: Now, a real enigma message was also obfuscated in another way. What they did was they made every word five letters long and completely discarded all punctuation and all formatting. The idea here was to hide any potential differences between big and small words like or, if, the, et cetera, in order to further hinder code breakers. Also, you don't want gigantic names, right? I simplified the example that I'm showing you, or I should say Ned is showing you on the screen for readability. You're welcome. But I think you get the idea. We will have a link to an actual enigma message in the show notes if you want to see what a telegram of an enigma message look like.

[00:23:01.02]
Ned: Okay. It sounds very, very hard to crack because all the things that you would use as clues before are just not present in this message for It's not a good plan.

[00:23:15.09]
Chris: Correct. The Germans did know that brute forcing it was possible, which is one of the reasons they added the additional complications. But they did not believe that it was practical. And in In fact, they had such an, especially the German army, had such an inordinate amount of confidence in this that they sent everything by Enigma. Now, when you talk about code breakers, the more material you give them, the better, right? Yeah. And also, like I said, the machine was public. People knew the Germans were using an enigma, so they did have a head start there. One of the biggest problems with the machine is exactly what you said, and I'm shocked that you knew this. If you typed a letter on the enigma with all the complications, no matter what, it wouldn't come up as itself. A W could be represented by any letter of the the alphabet, except for W. And that right there is a flaw.

[00:24:24.14]
Ned: Yes.

[00:24:26.23]
Chris: What the code breakers were able to do was to start compiling compiling a bunch of these types of flaws. This is not the only one. This is the easiest one to explain. You were able to do this and disqualify things from needing to be Root Forced. This was actually Alan Turing's great innovation was recognizing, once you recognize that a code brute force attempt failed, you figure out why. You can disqualify a huge swath of other ways of trying to disqualify it. So you wouldn't have to go, rotor setting number one, rotor setting number two, rotor setting number three, because the disqualifications would disqualify 10 to 20 at a time. So you could design a machine like this, which was one of the Bamba machine is what it was called, and also the Colossus machine, which was a different codebreaker, but the same idea and honestly deserves its own episode that Ned will write.

[00:25:28.22]
Ned: Sure.

[00:25:30.18]
Chris: That's exactly what these machines did. They took a message, they ran it through the machine that knew, run it through, figure out what was wrong with it, disqualify all these other different potential rotor combinations and go through that list until you find the one that works. Once you find the one that works, you know that every single message sent that day uses the same rotor combinations. So let's just say the first message of the day takes three hours to break. How long do you think the second message of the day is going to take to break?

[00:26:10.17]
Ned: As long as it takes to transcribe it, honestly.

[00:26:13.22]
Chris: Exactly. And with the amount of messages that were being sent back and forth, this is how the Allies built such an intelligence advantage. And it should be noted that the Germans had their own code-breaking expertise and stuff going on as well. They were breaking codes, too, but they were breaking them slower, the old fashioned way. So this was a major, major advantage for the Allies. In addition to the technical flaws that were identified in the Enigma, the code breakers also relied on the laziness and overconfidence of the Germans.

[00:26:55.07]
Ned: I was going to bring this up, but I wanted to see what you had to say about it.

[00:27:00.15]
Chris: So short story long, using the Enigma properly was a pain in the ass. I don't know if that's come across with my descriptions of this machine.

[00:27:13.22]
Ned: There's a lot to it. Yeah.

[00:27:15.18]
Chris: Oftentimes, code makers would take shortcuts. Now, tell me you haven't heard this story before. Security teams breathing down your back, but you just want to get this message out so you can go home and play Xbox. Additionally, messages would often start out written super formally and in the exact same way. The two from set up that you would expect on a Christmas present, along with some honorific sign off. Think back to the beginning of this episode, not unlike the mistakes the French made when they filled out the full title for all their royal will governors.

[00:28:01.02]
Ned: Right. So you could assume at the end of a lot of messages would be something like Heil Hitler or something along those lines. That was the way that you would end every message.

[00:28:14.05]
Chris: Exactly right. Oh, also, fun fact, the machines that were used to break these codes were called bombs, B-O-M-B-E. And nobody knows what that means, but it doesn't mean anything. It's actually because the Polish team that started all of this in the early '30s, they named it after an ice cream treat that they had a lot.

[00:28:38.08]
Ned: That's amazing.

[00:28:40.04]
Chris: When Bleschley Park picked up the program and started running with it, they kept the name.

[00:28:46.22]
Ned: It's a good name.

[00:28:47.21]
Chris: That's not a bad name at all. All of this stuff goes into that trial and error, eliminating false positives, making sure that you can get down to the message as fast as possible. When all was said and done, even with all the other complications, five rotors, plug board, all of that stuff, by the end of the war, the first message of the day would be decoded in as little as 20 minutes.

[00:29:11.07]
Ned: Holy schnikes. Yeah. That's fast.

[00:29:14.28]
Chris: And just like in the Napoleonic Wars, the code breakers had an incredible effect on the war effort. A lot of estimates have their contributions shortening the war by something like two to four years. In order to keep the state's secrets, everyone at Burtchley Park basically took a 30-year vow of silence, meaning that most of them never got the credit they deserved. That goes doubly true for the Polish teams that started this initiative years before the war even began. I mean, raise your hand if you even knew that this initiative was started by a team of Polish cryptographers.

[00:29:57.06]
Ned: Nope, can't say that I did.

[00:29:59.28]
Chris: So if anyone is interested in this and wants to know more, I highly recommend yet another book. This podcast is making me very popular at the library. A book called Codebreaker's victory. History: How the Allied Cryptographers Wone World War II. This is a very detailed history. It goes into how these machines work, but you do not need a math degree to understand it.

[00:30:27.23]
Ned: You want a slightly less serious but also a very interesting book that's a slight historical fiction? The Rose Code by Kate Quinn is also an excellent read. That's where I found out about some of the things that I know, that it wouldn't translate to its own letter when you're using the machine, or the fact that the Germans, because they were using the encoding for everything, they would do things like send the weather report every day. The weather report was basically the same most days. Made it very easy to start breaking that code. They didn't use the same exact encoding that more important higher priority messages did, but it still contributed to the problem. There's another book that I'm totally blanking on the name of, but I will include in the list. It was written about AI broadly, but it gets into a lot of this and talks about some of the decisions that the and the Americans had to make about playing dumb, about how much of the code they had actually broken. Because if Germany figured out that the codes were no longer useful, they would change their plans. It was all leading up to D-day.

[00:31:46.29]
Ned: And so they had to pretend sometimes and even sacrifice ships, even though they had the information that would have prevented their destruction to keep the fact that the codes were broken as secret. It's an amazing story.

[00:32:04.20]
Chris: It really is. Another good example of that, and I'll just go really quickly through it. One of the most famous broken codes of the war was actually way earlier. It was the Zimmerman telegram. Remember this one?

[00:32:17.24]
Ned: It's familiar, but go ahead.

[00:32:20.03]
Chris: Zimmerman was a, I think he was a console, I can't remember now, from Germany to Mexico. His basic His basic gambit to the Mexican government was, We will help you with an incursion into the United States in order to keep the US out of the European War. That was encoded via Enigma and broken almost immediately Immediately. And the British were like, oh, crap. How? What? Long story short, again, they basically created a fake intel incident in Mexico so that they could claim that it was personnel on the ground in the embassy that leaked the message and not the fact that they got it from the Enigma machine and the codes being broken.

[00:33:12.29]
Ned: But they could still act on the information.

[00:33:16.05]
Chris: Exactly. And that was one of the main things that pulled America into the European theater.

[00:33:27.10]
Ned: Amazing.

[00:33:28.12]
Chris: I know. So my first episode of the New Year, and I went long immediately.

[00:33:38.16]
Ned: Shocking.

[00:33:39.20]
Chris: The amount of stuff that I had to cut out of this was staggering. This could be a whole season.

[00:33:45.01]
Ned: It really could.

[00:33:45.29]
Chris: But anyway, I will stop here for now, I promise. And at this point, we're going to bid a due to ciphers as we have talked about them and start looking at encryption as we understand it today. Because in 1945, Claude Shannon of Bell Labs wrote a paper, actually it was a series of papers, called a Mathematical Theory of Communication. This paper was so forward-looking that it wasn't even allowed to be published until 1949. In the words of Bell Labs themselves, it, essentially, spawned the digital age. This spawned spawning. Okay, I regret that wording already, but I'm going with it. This spawning, one of the big pieces of it was modern cryptography.

[00:34:43.21]
Ned: All right. Well, we'll look forward to that when you get around to it. Hey, thanks for listening or something. I guess you found it worthwhile enough if you made it all the way to the end. So congratulations to you, friend. You accomplished something today. Now you can go sit on a couch, fire an enigma machine, and type in the weather to a friend. You've earned it. You can find more about the show by visiting our LinkedIn page. Just search Chaos Lever or go to our website, chaoslever. Com, where you'll find show notes, blog posts, and general Tom Foulery We'll be back next week to see what fresh hell is upon us. Ha ta for now. With the extreme British slant of this particular episode, Ha ta for now feels very on the nose.

[00:35:40.20]
Chris: Feels very on the tea and crumpets? I got nothing, man. I'm so tired.