WARS CONFLICT
From Warsaw to Dayton: How Allied Codebreaking Took On Naval Enigma
Alan Turing’s Bombe was a crucial part of a larger effort—built on Polish mathematics, British analysis, American engineering, and the work of women who kept the machines running.
The Allied attack on German naval Enigma was a multinational effort, linking Polish cryptanalysts, Bletchley Park, American engineers, Navy WAVES, and the Battle of the Atlantic.
In February 1942, the German Navy added a fourth rotor to the Enigma system used for U-boat communications. The change sharply reduced Allied access to traffic that had helped reveal submarine positions in the North Atlantic. [4][5]
The setback came in a campaign where U-boats threatened ships carrying troops, fuel, food, and matériel. Enigma was not a cipher the Allies solved once and kept solved. German settings, procedures, and machinery could change, and each change demanded a new response.
Alan Turing was central to that response, especially in work against naval Enigma and in the design of the British Bombe. But the machine’s history runs through Polish mathematics, British analysis, American engineering, captured German materials, and the operators who kept the equipment working around the clock. [2][3][4]
The Polish Foundation
In 1932, Marian Rejewski reconstructed the wiring of the German military Enigma machine using mathematics, intercepted material, and intelligence supplied through France. With Henryk Zygalski and Jerzy Różycki, he helped develop methods for finding the daily settings of a system whose rotor positions and plugboard connections changed. [6]
Their work did not provide a permanent answer to Enigma. It established that the machine could be attacked systematically. Zygalski’s perforated sheets and the Polish electromechanical *bomba* put that insight to practical use. [2][6]
On July 25 and 26, 1939, Polish representatives met British and French cryptanalysts at Pyry, outside Warsaw, and disclosed their reconstruction work, methods, and machine knowledge. [2]
Turing reported to Bletchley Park on September 4, 1939. He built on the Polish foundation in work that included naval Enigma and the specification of a British Bombe. In January 1940, he met evacuated Polish cryptanalysts in France. [2][3]
What the Bombe Did
The Bombe did not read German messages on its own. It was an electromechanical search machine. Analysts gave it a *crib*—a plausible fragment of German plaintext believed to occur at a particular point in an intercepted message—and the machine tested Enigma configurations consistent with that assumption. [1][3]
Cribs could come from routine phrases, weather reports, predictable formats, or close study of German operating habits. Gordon Welchman’s diagonal board made the Turing-Welchman Bombe substantially more effective. [1][3]
A machine result was only the beginning. Staff still had to verify a possible setting, decrypt and translate the message, assess what it meant, and distribute intelligence without making clear how it had been obtained. Captured German machines, key lists, weather codes, and operating documents remained vital. By the summer of 1941, Hut 8 was regularly reading the naval Enigma key known as Dolphin after captures provided essential cipher material. [3]
The Four-Rotor Crisis Reaches Dayton
The four-rotor naval Enigma system introduced in February 1942 interrupted Allied access to U-boat traffic. It also accelerated British and American efforts to build machines able to attack the new system. [4][5]
Turing traveled to the United States in December 1942 to advise on cryptanalytic machinery and examine secure voice communications, as British-American exchanges of cryptanalytic knowledge deepened. [3][8]
In Dayton, Ohio, an NCR engineering team led by Joseph Desch designed and manufactured high-speed four-rotor Bombes for the U.S. Navy. Prototype machines were completed in the spring of 1943. [4][5]
Navy WAVES, women reservists whose work remained secret for decades, wired components and supported testing and maintenance. WAVES later operated Bombes around the clock at Nebraska Avenue in Washington, D.C. [4][5]
The American program expanded Allied capacity; it did not replace British work. Intercept stations had to collect traffic. Analysts had to develop cribs. Machines had to test possibilities. Intelligence staff had to interpret the results, and commanders had to decide how to act on them. When the chain worked, information about U-boat positions could help reroute convoys or concentrate antisubmarine forces. [4]
Colossus Was a Different Machine
The Bombe is sometimes described as an early computer, but its wartime role was narrower: it was a specialized electromechanical machine for searching Enigma settings. It required a human-supplied crib and did not produce a finished intelligence report. [1][3]
Colossus addressed a different German cipher system. It attacked Lorenz teleprinter traffic used for high-level German communications. Tommy Flowers designed and built Colossus at the Post Office Research Station at Dollis Hill for Max Newman’s section; the first operational machine entered service in early February 1944. [7]
Colossus was electronic and programmable in a limited, special-purpose sense. It was not an Enigma machine, and Turing was not directly involved in building it. Keeping those histories separate gives proper credit to Flowers, Newman, and their teams. [3][7]
Intelligence and Alliance
A decrypted message was not a clean answer delivered by a machine. A false crib could waste time, and a genuine result still needed context. A reported U-boat position might be current—or it might describe an order, a sighting, or a plan already overtaken by events. Commanders also had to protect the source.
Codebreaking was an important Allied advantage in the Battle of the Atlantic, alongside naval power, shipping, reconnaissance, and antisubmarine operations. Precise claims about how many lives it saved or how much time it removed from the war remain counterfactual and disputed. [6]
The partnership had consequences beyond the war. The BRUSA agreement, signed on May 17, 1943, formalized U.S.-British signals-intelligence cooperation and helped establish procedures later incorporated into the postwar UKUSA partnership. [8]
Turing’s wartime work belongs to that larger story. His ideas mattered greatly, particularly in the attack on naval Enigma, but their effect depended on an international system of mathematicians, analysts, engineers, operators, captured materials, and military decision-makers. Secrecy delayed public recognition of many of the people involved, including Rejewski, Zygalski, Różycki, Welchman, Desch, Flowers, Newman, the WAVES, and other participants. [3][4][6]
Frequently Asked Questions
Did Alan Turing build Colossus?
No. Turing specified the Bombe and was a leading figure in the attack on naval Enigma, but he was not directly involved in building Colossus. Tommy Flowers designed Colossus for the Lorenz problem for Max Newman’s section. [3][7]
What role did the United States play in breaking naval Enigma?
The United States expanded Allied capacity to attack the four-rotor naval Enigma system. Joseph Desch’s NCR team developed high-speed U.S. Navy Bombes in Dayton, and Navy WAVES helped build, test, maintain, and operate them continuously. [4][5]
How did Polish cryptanalysts contribute?
Marian Rejewski, Henryk Zygalski, and Jerzy Różycki established a prewar mathematical foundation for attacking military Enigma. Their July 1939 disclosure at Pyry gave British and French counterparts their reconstruction work, methods, and experience with the electromechanical *bomba*. [2][6]
TIMELINE
Key moments
Sources
- Turing’s Treatise on the Enigma: A Photographic Copy of a Paper Prepared in GC&CS — U.S. National Archives and Records Administration
- The Pyry Forest Meeting — GCHQ
- Alan Turing — Bletchley Park Trust
- World War 2: U.S. Navy Cryptanalytic Bombe — National Security Agency and National Cryptologic Museum
- WAVES on Top Secret Duty in America’s Heartland — Naval History and Heritage Command
- Zygalski Sheets: Polish Codebreaking and the Role of Reconstruction in the Top Secret Exhibition at the Science Museum — Science Museum Group Journal
- Colossus — The National Museum of Computing
- A Brief History of the UKUSA Agreement — GCHQ
RELATED STORIES