Twelve days after launching the Agrippa Challenge on July 10, 2012, Quinn Dupont made the official announcement that it had been “cracked.”
It was even easy, for those with the right kind of training in programming, mathematics, and cryptography— as becomes apparent from the published submissions. The link above leads to a great resource with fascinating analyses that help readers understand how the poem was encrypted and decrypted, as well as its self-destruct mechanism. So now that we know how it works, what do we do with that information?
We read it, of course. Since we are closer to the text (as discussed in previous postings on Agrippa) and can integrate the code into the reading.
In looking at some of the design choices made by the anonymous programmer, it seems that Agrippa’s “cryptographical weakness” leads to greater artistic strength. Like the flimsy locks one can find on diaries, the encryption used in this poem is more symbolic than safe. Its mechanisms are tied to strategies in the poem as a whole. For example, the use of genetic code informs two meaningful choices by the programmer:
- The use of 3-character blocks in the encryption of the text, weakens the encoding, allowing the encryption key to be discovered through a simple mathematical “brute-force attack.” This corresponds to the number of letters in the word “DNA:” an important motif for heredity in a poem centered on a photo album belonging to the speaker’s father.
- Genetics are also used to “destroy” the program by writing a fixed CTAG sequence (the bases of DNA) over 6,000 bytes of the program (see Bryan Carnes’ explanation), rendering it inoperable. Because it is fixed, however, the corrupted program can be “uncorrupted” and played again.