3 ms·
I'd also include that they received the coded message twice showing that it's unlikely it was misheard or misread on either end. That was my initial reaction/th
by rtkwe 11y ago
I'd also include that they received the coded message twice showing that it's unlikely it was misheard or misread on either end. That was my initial reaction/theory, that the code was close to the confirmed order but one side messed up some how. With a second confirmation it seems like the 'NOP' (dummy) code either accidentally matched the LAUNCH code or the correct code was given to (or procured by) the major who transmitted the mid-shift messages.
It's an interesting question of how do you ensure you never accidentally transmit the correct code without the sender knowing the correct code and being able to command a launch single-handedly. Even if the code is really long, generating random NOP codes doesn't give the level of safety I'd like when accidental collisions can end the world.
- mikeash 11y agoMaybe the book was sorted alphabetically, such that the code for LAUNCH MISSILES was listed next to the code for LUNCH TIME or something.
- rtkwe 11y agoMy understanding is that the correct launch authorization code would be locked in a safe until the command post had received a message authorizing them to launch. It's safes and authorization confirmations all the way down as I understand it.
- jjoonathan 11y agoI am sure the system was designed to resist intentional manipulation by intermediates, but what about plain old telephone-game mishaps? If LAUNCH and LUNCH TIME are represented by one-time-pad blobs that are right next to each other on a list, it doesn't matter how many two-person-locks or feet of steel prevent the operator from learning which blob is the LAUNCH blob because an off-by-one mistake is still easy to make as ever.
- rtkwe 11y agoI was saying that the launch codes would only be available if the CP had received their own launch codes and there wouldn't be a list with the launch codes and lunch codes to make that error.
- mikeash 11y agoThe question is whether the codes were sufficiently far apart that you couldn't stumble onto one by accident, or whether they were similar enough that you could generate LAUNCH MISSILES by accident with a typo, even if you never went near the safe and had no idea what your message actually meant.
- iSnow 11y ago>It's an interesting question of how do you ensure you never accidentally transmit the correct code without the sender knowing the correct code Use a good hash function and give only the hash to the sender? Before sending, the sender hashes the codes she has and compares the hash with the "hot" hash.