Solving the pigeon's code
I don't know if you heard, but recently some pigeon's bones were found. These, though, were not just your average remains of a long dead bird. This bird had, attached to one leg, a small red cylinder, which had a small scroll of paper rolled up in it. On that scroll, are sets of five letters. AOAKN HVPKD and on and on. They make no sense. Just a code from the leg of a bird, which died in a chimney many years ago.
It turns out, that bird was the remains of a D Day carrier pigeon, who never made it his destination. As a note, carrier pigeon's were used because of the radio blackout Churchill had ordered. Anyway, that code was British communication and it appears unsolved. In fact, they say it is not solvable without the code book, but they have released it to the public to have a look.
So many elements of this story speak to me. It has history and an unsolved code. A code, which was lost for decades and now might never be solved. Additionally, we have the code, we can see it, read it, imagine what it might say. Did I mention it is an unsolved and maybe unsolvable code.
Several years ago, I was pretty deep into code cracking. It started very simply. I wanted to design a program which would encode and then decode a message using a Caesar cypher. That is perhaps the easiest of ways to encode a message, it is where you shift the characters a certain number of letters. A's become B's and B's become C's and so on. It was simple and it worked and with a little work, even if you did not know the shift amount, you could figure it out. From there I worked on a process so the computer could predict the shift. It used the letter frequency of each letter in normal English writing and then looked at the encoded message and spun the dial until the finger print was the closest. For all but the shortest messages it worked.
This tool held my interstellar until I started to look at more complex cyphers, such as Playfair and Vigenere. So, I adjusted the tool to do these. It was like breaking apart the code, solving it in several different, but simple ways and putting it back together. It would even tell you the passcode that was used to encrypt the message.
But that was years ago and the tool I developed was on a thumb drive I no longer wear. So, I hear about the message and the bird and I start looking. If I can find my thumb drive, maybe, just maybe, my code cracker can solve the message. For twenty four hours I can't seem to find it. Then, last night, I find it. I find the thumb drive. So, today I sit writing my blog, with the drive around my neck, like I used to years ago, imagining what I will do if I solve the code.