{"id":4857,"date":"2015-05-06T00:41:32","date_gmt":"2015-05-06T04:41:32","guid":{"rendered":"http:\/\/www.kaspersky.co.in\/blog\/?p=4857"},"modified":"2019-11-22T15:39:12","modified_gmt":"2019-11-22T10:09:12","slug":"world-war-ii-information-security-navajo-vpn","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.in\/blog\/world-war-ii-information-security-navajo-vpn\/4857\/","title":{"rendered":"World War II information security: Navajo VPN"},"content":{"rendered":"
\n
\n

World War II revolutionized many technologies, including those that shaped the modern InfoSec industry. Back then, methods and machines utilizing modern cryptography principles were often coupled with \u2018amateur\u2019 ciphering methods.<\/p>\n

Curiously, later ciphering methods\u00a0proved to be extremely\u00a0reliable. For instance, here is the story in which the Navajo language was used by the US Marine Corps<\/a> on the Pacific Theater of Operations.<\/p>\n

During battle, the Marine Corps had to coordinate operations between ground units, airborne divisions, and artillery support squads. All communications were broadcasted over the radio and were easily intercepted by the adversary.<\/p>\n

The Marine Corps had to establish a method of conversing that wouldn\u2019t reveal tactical information to the enemy. To put it in modern day terms, when connecting over an unprotected public Wi-Fi link in a caf\u00e9 or on the street<\/a>, your personal information is put at risk of being hacked. The solution would be the like of VPN you could use<\/a> to safeguard your data.<\/p>\n

Bearing in mind the issue of security, it was crucial to maintain a high speed of interaction as well, since we are talking about the tactical actions on the battleground and not about the delivery of strategic orders from the high command. That\u2019s why ciphering machines and one-time pads<\/a>, which were used as the main means of data protection back then, were too slow and inefficient.<\/p>\n

Using an exotic language in order to protect communication was not an altogether new idea: the first successful use was registered during World War I when American troops used the Chokto language during operations in Europe.<\/p>\n

However, American counterintelligence was aware that, following this success story, many German \u2018ethnology researchers\u2019 visited the U.S. to study Native American languages. It is safe to presume that they shared the knowledge they acquired with their troops in the Eastern hemisphere.<\/p>\n

If it wasn\u2019t for Philip Johnston<\/a>, a retired officer from Los Angeles, command could have never re-used this idea. He grew up by the Navajo territory and had been fascinated by their culture and language since childhood. In his teen years, he even served as an interpreter for a Navajo delegation during a summit in Washington, D.C.<\/p>\n

By the time WW2 started, he was too old for the call-up, but when reflecting on\u00a0his WW1 experience, Philip generated\u00a0an idea for\u00a0securing battleground communication worthy enough to offer to command.<\/p>\n

He had to apply a considerable effort to convince command that using the Navajo language was a great idea<\/a>. Initially, his idea stemmed from the complexity and isolation of the Navajo language, which, besides the Navajo themselves, was spoken by only 30 people in America. Even representative speakers of kindred languages could not comprehend the Navajo language due to its overly complex grammar.<\/p>\n

However, after he was allowed to form a group of 29 Native Americans to initiate the education process, through collected effort, the idea evolved and in due course, an even better\u00a0method\u00a0of ciphering communication was created.<\/p>\n

\"WW2<\/a><\/p>\n

First, a separate phonic alphabet was created: when communicating over the radio, each Latin letter matched an English word, which had a simple translation to Navajo (e.g. A \u2014 ant, B \u2014 bear, C \u2014 cat, etc.).<\/p>\n

For example, spelling IWO JIMA over the radio would sound as \u201ctin\u201d \u2014 \u201cgloe-ih\u201d \u2014 \u201cne-ash-jah\u201d \u2014 \u201ctkele-cho-gi\u201d \u2014 \u201ctin\u201d \u2014 \u201cna-as-tso-si\u201d \u2014 \u201cwol-la-chee\u201d instead of common English \u201citem\u201d \u2014 \u201cwilliam\u201d \u2014 \u201coboe\u201d \u2014 \u201cjig\u201d \u2014 \u201citem\u201d \u2014 \u201cmike\u201d \u2014 \u201cable\u201d, already familiar to the Japanese intelligence.<\/p>\n

Second, a glossary was made for frequently used terms. For example, jet fighters became \u201chumble-bees\u201d, submarines turned into \u201ciron fish\u201d, and colonels were referred to as \u201csilver eagles\u201d. The aim of this approach was two-fold: to speed up the exchange and to unify terms that had no corresponding Navajo translation.<\/p>\n

Lastly, as a final line of defense, during their training Native American marines had to study this ciphering system until they knew it by heart, so that the enemy would never get access to any written materials during operations.<\/p>\n

As a result, the messages conveyed by the Navajo signalers were not even comprehended by their fellow tribesmen, who had not been trained in this adaptation of their language.<\/p>\n

This scheme may seem a bit too complicated on paper, but the first real-life trials proved that Navajo marines could convey messages much\u00a0faster orally than by means of purpose-made ciphering machines. Using the phrase \u2018much faster\u2019 is not an over exaggeration: it took 20 seconds versus 30 minutes for ciphering, relaying and deciphering a short three-line message.<\/p>\n

About 400 Navajos<\/a> served as signalers in the U.S. Marine Corps during the war, and we commend their performance and devotion, especially given the harsh realities of the Pacific Theater of Operation, recounted by numerous testimonies of their fellow soldiers.<\/p>\n

WW2 information #security: #Navajo #VPN<\/p>\n

Tweet<\/a><\/p><\/blockquote>\n

The Japanese intelligence was never able to decipher the Navajo communications, although they were quite aware of the scheme\u2019s existence. One of the Navajo Marines was captured and later told his story about being tortured by the Japanese once they discovered his Navajo origin<\/a>. He was just a soldier and not a signaler, so he did not know the principles of the system.<\/p>\n

The conclusion is applicable to modern day threats: we don\u2019t need absolutely \u2018unhackable\u2019 protection for our data. What we need is protection strong enough<\/a> to prevent an attacker from cracking it within the time they have available.<\/p>\n

When we compare this Navajo scheme to today\u2019s ciphering methods, which employ complex mathematical models and super powerful computing clusters, it seems a bit na\u00efve. Of course, it is vulnerable. But the fact remains- it was not breached during the war, and, as one of the officers once said, \u201cWithout Navajo, we would never win in Iwo Jima\u201d.<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

World War II revolutionized many technologies, including those that shaped the modern InfoSec industry. Back then, methods and machines utilizing modern cryptography principles were often coupled with \u2018amateur\u2019 ciphering methods.<\/p>\n","protected":false},"author":40,"featured_media":4858,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[5],"tags":[569,261,553,1041,43,97,1042,1043],"class_list":{"0":"post-4857","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-news","8":"tag-cryptography","9":"tag-encryption","10":"tag-history","11":"tag-navajo","12":"tag-privacy","13":"tag-security-2","14":"tag-world-war-2","15":"tag-ww2"},"hreflang":[{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/world-war-ii-information-security-navajo-vpn\/4857\/"},{"hreflang":"zh","url":"https:\/\/www.kaspersky.com.cn\/blog\/world-war-ii-information-security-navajo-vpn\/2958\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.in\/blog\/tag\/cryptography\/","name":"cryptography"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/4857","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/users\/40"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/comments?post=4857"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/4857\/revisions"}],"predecessor-version":[{"id":17834,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/4857\/revisions\/17834"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media\/4858"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media?parent=4857"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/categories?post=4857"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/tags?post=4857"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}