I have had to revoke my PGP key since I forgot the passphrase – mea culpa. Not that I have had too much use for it in the near past, but really, my Social Security Card, and passport haven’t seen the light of the day in more than a year now. My passphrase had 5 phrases/words in it, and though I can remember the last four, no amount of thinking in the shower, going to sleep while telling my mind to recall it from the subconscious and reveal it in a dream, and trying to recreate the instant when I thought up the passphrase is helping me. When I created the passphrase I had taken special care to make sure that I can recall it if I remembered at least one of three things, and yet, though I have the last four phrases/words I can’t for the life of me remember the first. I am sure it will come to me one day when I am lounging in my beach chair in a remote beach with a book on my chest.
So, friends, my keys have been revoked, using the instructions I wrote myself when I created the revocation certificate. The Key ID is 1878779A. Previously, the key with the Key ID 702814C0 had also been revoked. Searching the MIT PGP KeyServer confirms the revocation. Strangely though, the Veridis Keyserver doesn’t seem to know about the first revocation.
Anyway, the following is the revoke certificate:
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: A revocation certificate should follow iI4EIBECAE4FAkKUqn1HHQBSZXZvY2F0aW9uIGNlcnRpZmljYXRlIGNyZWF0ZWQg YXQgdGhlIHRpbWUgb2YgY3JlYXRpb24uIE1heSAyNSwgMjAwNS4ACgkQPEhXdhh4 d5rUDQCeMdyDBHIh4rGGnFrsw6yWi99Db5EAni81qyTuNVBZu5OwE7bOcvuO0psb =3bl3 -----END PGP PUBLIC KEY BLOCK-----
The only reason it took me so long to revoke this key-pair is that I had encrypted the revocation certificate with a symmetric key cipher, and thought I had forgotten the password for that too. I know, how smart. I had encrypted the revocation certificate using Gringotts – a very neat little encryption/decryption application. Then when I tried to decrypt it a while ago, the dang file wouldn’t get decrypted. So I feared the worst, and thought maybe I had forgotten the password for that too. Being unable to revoke keys is a lifelong sign of stupidity – much worse than a tattoo, I hear. Fortunately I just found out that Gringotts was broken and it was not my fault. So I tried with an up-to-date Gringotts, and voila! – I could decrypt my revoke certificate.
I will create a new key pair shortly – I have to get it all perfect from the get-go this time.
Update: New Key ID: BB0B8176
New key is below:
—–BEGIN PGP PUBLIC KEY BLOCK—–
Version: SKS 1.0.9
—–END PGP PUBLIC KEY BLOCK—–