Re:Re:publica 15: Google Promotes Privacy, But Not Too Much
by tomjen3 on Monday May 11, 2015 @07:10AM
(#9523809)
Why not encrypt the routing separately?
Re:Re:publica 15: Google Promotes Privacy, But Not Too Much
by bandrami on Monday May 11, 2015 @07:24AM
(#9523858)
I simplified. They did encrypt the routing separately but it was essentially a known plaintext attack because you could see which ships moved after which transmission.
Re:Re:publica 15: Google Promotes Privacy, But Not Too Much
by marcosdumay on Monday May 11, 2015 @10:13AM
(#9524856)
Remember that those were different times. Computer science itself was born by trying to break that crypto, and modern cryptography wasn't available.
A different key for each vessel would mean several passes through the encryption machine, key tables distributed through several places, and the requirement of specialized workforce where otherwise just typing stuff in a machine would do. And all the errors that come with manually dealing with that, all during a major war.
In WW2, the Allied Navies faced two main naval code strategies: Germany's and Japan's. Roughly, the Japanese Navy sent their routing information in plaintext, while the Kriegsmarin sent it in ciphertext. Because the German routing instructions were encrypted, each node had to be able to decrypt universally. Capture one U-boat, and, well, we all saw the movie.
In contrast, the Japanese navy sent the routing information in the clear, so transceiving stations only had to read the routing information and transmit the ciphertext verbatim: capture a Japanese sub and you can only decode messages sent to that sub. However, because the routing information was visible in all transmissions, a lot of sideband avenues were opened up (you may not know what Yamamoto was sending to the Coral Sea fleet, but you're damn sure interested in the fact that he was talking to them at 2am this morning, particularly since you can then watch what they do.)
Anyways, not directly relevant to the article but a cool example of how far back this question goes.