Confederate Dictionary Code
Confederate dictionary codes: secrecy and interoperability depend on the shared reference
Known dictionary + position lookup
Why This Matters
Dictionary codes require both parties to agree on the exact reference and indexing rules. A page, column and word address is meaningful only within that shared edition. This is a practical interoperability lesson as well as a secrecy problem: a public dictionary is not a high-entropy secret key.
Kahn records Jefferson Davis sending Albert S. Johnston a dictionary in March 1862 and explaining the address 146.L.20 as page 146, left column, word 20, for “junction.” He also describes Confederate naval officers obtaining paired dictionaries. The evidence supports the need for matching references; it does not establish the particular Webster edition or the Lee–Johnston edition-mismatch anecdote previously associated with this example.
The matching reference and indexing rules must be shared with the intended recipient. Edition mismatch is a possible interoperability failure, not an episode established by the example above.
Illustrative dictionary coordinates, not a transcription of a historical edition Encoding: Find the word in the dictionary Record: (page number)(position on page) 'ship' = page 674, word 26 → (674)26 'attack' = page 51, word 8 → (51)8 'tomorrow' = page 312, word 3 → (312)3 Security depends on the reference, indexing rules, message patterns and attacker knowledge
Once the source dictionary is identified (which edition, which publisher), the code breaks completely — every page and position can be looked up directly. That is a conditional attack: this exhibit does not document a particular Union recovery of the dictionary used in the example.
The operational failure: An edition mismatch can make a dictionary-coded message unreadable to its intended recipient. Operational cryptography must ensure that all parties can actually communicate.
| Concept from Confederate Dictionary Code | Modern Evolution |
|---|---|
| Shared reference = shared key | Public-key methods help establish keys, but authenticating identities and managing credentials remain necessary |
| Dictionary lookup = decryption | Hash tables: O(1) lookup structures in computer science |
| Edition mismatch = communication failure | Protocol versioning: cryptographic standards must specify exact parameters |
| Exhibit | 26 of 172 |
| Era | Confederate · 1862 |
| Trust | Broken |
| Inventor | Jefferson Davis · Confederate War Department |
| Year | Spring 1862 |
| Key Type | Page and word number from shared dictionary |
| Broken By | Known dictionary + position lookup |
Sources and Reading
David Kahn, The Codebreakers: The Comprehensive History of Secret Communication from Ancient Times to the Internet, revised edition (1996), Chapter 7, “Crises of the Union,” for Davis’s 146.L.20 example and Confederate naval dictionary arrangements. The diagram uses invented entries.