Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"Encrypted" is too strong a word. But the code talkers needed a way to represent English that didn't have a natural Navajo equivalent.

So they developed a vocabulary of 411 Navajo words to stand for common military terms. E.g., BESH-LO, which is Navajo for "iron fish", meant "submarine".

The vocabulary included a phonetic alphabet to represent the 26 English letters. E.g., the three Navajo words MOASI, TLA-GIN, and BA-GOSHI all represent English words beginning with C (cat, coal, cow). So, they could spell out arbitrary English words not in their vocabulary.

It was secure against an enemy that lacked Navajos and probably didn't even know what language was being spoken or if they were intercepting some weird form of audio scrambling. But, if the Japanese had been able to translate the messages to English, the code would probably not have survived cryptanalysis for long.

https://www.cia.gov/stories/story/navajo-code-talkers-and-th...



It's not really secure as such. It's a simple replacement cipher theoretically speaking. An adversary with enough time will easily be able to figure out what each word means by association of known plaintext.

However it sounds like they were mainly used in heavy combat conditions where the enemy didn't have recording equipment for later analysis. So in that scenario specifically (but in that alone) it was pretty secure.


Yes, for the parts that needed to be distinctly translated from English, it was a cipher. However, it IS a language, with it's own grammar and vocabulary. They could have an entire conversation with none of the cipher bits...

If you've ever gone to a foreign country, you know you will have zero idea what anyone is saying for quite a long time. They knew as long as they kept the messages short enough, nobody was going to learn it from immersion.

There are still ancient languages that nobody have deciphered, despite having copious samples to choose from. I don't think it's as simple as you're making it out to be.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: