IMS_Blog

The first thing which struck me about that solution was the need for a unique id for each div surrounding the encrypted text. Now I don’t have a particular desire to mix cypher and plain text in the same post, and my posts are already surrounded by a div. Of course I could generate unique id’s quite easily but it seemed a bit more elegant to simply pass a reference to the decrypt link and work my way back up the DOM to the appropriate div. So that’s what I did.

The javascript can be found here (I don’t claim it’s at all well written). My bit is the decryptPost function at the very end. It takes one parameter which is a reference to the clicked link (which is sent using the this keyword in the link’s onClick event). It then steps up the DOM until it finds the enclosing div and procedes to attempt to decrypt each paragraph in turn. This has a couple of advantages 1) I don’t have to worry about the general formating applied to blog posts by default (i.e. the fact that those paragraphs exist to start with) 2) It means I can actually encrypt different paragraphs with different keys should I wish and then give out a key for pieces I might want seen whilst still keeping some private.

As well as keeping a local copy of the javascript encrypt/decrypt page I also wrote a greasemonkey script to encrypt a blog post with one click. This also automatically adds a nice key (using the previously mentioned Key Values plugin by Brad Cheate) so that the template has a hook to know to add the decryption link.

Anyway, if you want to try it out the super, never to be revealed to the world, secret key to decrypt the the last post is… testkey

Update: I edited the javascript a bit to accept a space separated list of keys and decrypt whatever it can with each in turn.