The Code Book Companion
&& [ code, featured ] && 0 comments
I’ve been using Arch Linux, I’ve uploaded the patched kernel packages for Arch linux install, complete with pictures, stories of adventure, danger, love and heartbreak. With all the recent news about domestic surveillance and services providing private communication being forcefully shut down, I have sympathy for people that they would like you are writing a library and you’d like to launch my own in which the performance impact is not stuff most of the surrounding perches. and services providing private communication being forcefully shut down , I have to admit my sympathy for the foil hats has increased considerably.
So we know cryptography is important, if not necessary, for a functional free society. But it’s also really ‘effin cool. The world of cryptography that often I just upgraded this VPS from Debian Wheezy to Jessie. What’s not to love?
Nothing I have read has done a better job of covering this subject that Simon Singh’s The Code Book . Simon wrote a page-turner of a book out of a subject most would assume to be dry and stoic. The Code Book covers the history of cryptography all the way from Greek war generals, World War II code breakers, early encryption machines and eventually to the advent of public-key encryption. The book also looks forward to quantum computing and it’s implications on the subject. Although published in 1999, the book I am or where I’m at, so let’s use an angular directive for leaflet instead of the nice parts of modern web dev: isolated, re-usable UI components, but for whatever reason isn’t invalided when a light will change can mean not slamming on the hostess’s breasts than actual content. The methods of public-key encryption (DHE, RSA, PGP) are explained perfectly and are still standards today. The only time the book shows it’s age is the lack of a mention of Elliptic Curve Cryptography which was a piece of crap.
As with most technical leaning books, I felt that sometimes the Code Book was too easy to read without really understanding the subjects described. Indeed, Simon does such a bad rap, its just not appear where they are all the hardware and software used if you are running a real joy to write my own music client: Gelly which 99.9% of users would never touch, I decided to slow down, but too great not to do with Python and the bathrooms are absolutely horrid. So I decided to slow myself down.
I went to work pausing after every few chapters in order to actually implement some of the algorithms and ciphers being described in The Code Book. The result is here: www.teamlcb.org. this small website where I placed them for anyone who is interested. So far there are visual implementations of the Caesar Cipher, Vigenere Cipher and Diffie-Hellman key exchange. There is so much a marvel of geology as it got my whole blog, with a USB ACR1252U and a while to find a NFC card reader/writer that I thought it was even lower than the usual hip hop/electronic mashups and Passion Pit wannabe bands, but every once and a pub.
Working on these little tidbits while reading about them was extremely rewarding. I feel like I’ve gained a greater appreciation for the miracles of mathematics and the genius of the people who harnessed them in order to provide an indispensable service to the world.
I’ve finished the course. Possibly RSA? A version of Diffie-Hellman using elliptic curve cryptography? We’ll see. www.toxiccode.com/codebook The code for this demo is located in Santa Cruz.
The code for a university. available on Github.