Broad Guide to Bootstrapping your own Codebook

Using a few key formulas you can create a functional code book with enormous keys that no computer could possibly brute force.

First let me explain how many possible keys there are in this particular example.

In this example the word list contains 3000 words. Each subsequent column labeled k1-k9 contains another 3000 bits of unique information. Each number of key columns added exponentially increases the total key possibilities.

In this schema the "Key" to encrypt and decrypt is the unique state of each cell in relation to the word list.

3000!^10 represents the amount of possibilities.

That is 2^91312 possible keys which makes aes 2^256 look completely wimpy.

Important Functions To Master To Build your Code Book

• randbetween()

-vlookup()

-ifs()

-concatenate()

All of these formulas can help automate the encode/decode process.

Ways to mitigate Frequency Analysis

-Layer the final ciphertext with other string encryption protocols.

-Increase the amount of key columns so that the encoding formula can pick a random column. This will allow the same word to be encoded multiple ways so that someone analyzing plaintext will hit a wall.

-Generate new keys. New keys can be generated by shuffling the key and wordlist columns. You can use sorting functions to randomize and shuffle the wordlist.

Ideal Operational Security

-Air gap the computers running the encoding/decoding processes

-Share the keyfiles offline

-Rotate keys often

-Destroying old keys

-Use already secured communication channels to add layers.

Final Notes

This is obviously not a convenient way to share a message. It requires dedicated hardware, and disciplined protection of the keyfiles to really be secure.

Regardless of what anyone tells you about the strength of modern encryption ciphers like AES256...do you really think a the most powerful nation in the world would release a unbreakable encryption protocol 15 days after 9/11? I don't think so pal