Cracking Enigma in 2021 - Computerphile
Video Statistics and Information
Channel: Computerphile
Views: 787,747
Rating: 4.8946471 out of 5
Keywords: computers, computerphile, computer, science, Enigma, Turing, Mike Pound, University of Nottingham, Cipher, Cracking, Crypto, Cryptography, Alan Turing, Bletchley Park
Id: RzWB5jL5RX0
Channel Id: undefined
Length: 21min 20sec (1280 seconds)
Published: Mon Apr 12 2021
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.
I loved this. If the video is too long for you, spoiler alert - he cracks it. The video is really about why it is not as trivial to crack as one might think. Definitely worth watching the whole journey. He explains in great detail how surprisingly complex enigma encryption is and why his solution even has a chance.
Always felt the plugboard was substantially less secure than the raw numbers would suggest, and I'd say this video also shows this.
If we went with letter frequency tables rather than IoC, and we had the rotor settings, we'd be able to determine with quite a lot of confidence when we had the correct plugboard for the most common letters (t and e in English, e and n in German). They're frequent enough that there's a good chance of seeing them just from the unplugged cypher text letters.
With a known plaintext, as Bletchley park had, it's even easier. A Bombe simply tried different combinations until it reached a contradiction, and could backtrack, eliminating whole swathes of possibilities.
I could listen to Dr Mike Pound for an hour
It's sensationalized, but if you haven't seen Imitation Game, definitely check it out! It was very cool in the movie to watch Turing's computer run, trying to decrypt the Enigma messages.
Does anyone know of any other old timey encryption methods that can be easily cracked by a hobbyist today?
10 years ago I would have enjoyed this style of video a lot better. Now I want the conclusion at the start, and the video explaining it. Having to watch the whole thing or poke the timeline at random is ridiculous these days.
How hard is it to multithread work in Java? I was looking at his code, and the longest part of the search, the rotor search, is an embarrassingly-parallel problem, but still being done in a single-threaded way.