Been playing around with PGP again and stupidly imported my revocation key!
Thankfully, I had not uploaded that revocation to the key server, so using this tip I managed to “undo” the revocation.
And to preserve this knowledge from link rot I’ll paste it here:
It turns out that it is possible (and relatively simple) to delete and re-import the key, provided that it is on a keyserver (and provided that the revocation has not been sent to the keyserver, of course).
This is what I found to work (THEKEYID is the short ID of the key):
Delete the public key as follows (the –expert option allows the public key to be deleted whilst the private key is kept) :
gpg –expert –delete-key THEKEYID
Confirm by pressing:
Fetch the public key again from a keyserver:
gpg –keyserver subkeys.pgp.net –recv-keys THEKEYID
Presumably this could also be done from a local (pre-revocation) backup of the public key, using gpg –import public.key instead of the third command.
Simply deleting the entire key (public and private) from the GPG Keychain Access GUI, and then restoring from a backup, did not work – I don’t know why.
Alternately, you can just as easily use a previously sent copy of your public key (in case you have the file/mail) you can just import it after the deletion from file.
Just useful to have! 🙂
PrivacyChoice Blog | Making privacy easier
Android beats iOS when it comes to privacy disclosure
And when it comes to privacy, this seems like a good blog to follow 🙂 I came accross this site when I looked through the dev page for a Firefox add-on called Better Privacy, which does away with Flash Cookies.
Ghostery™ sees the invisible web – tags, web bugs, pixels and beacons. Ghostery tracks the trackers and gives you a roll-call of the ad networks, behavioral data providers, web publishers, and other companies interested in your activity.
And it looks like a useful product. It works as an add-on on Firefox and might be available of IE as well. In addition to this, a great way to check if you’ve got your privacy settings enabled is to go to http://www.firefox.dom/dnt – and if you prefer it enable the Do Not Track (DNT)setting there’s a link that shows you how.
DNT is a voluntary standard, i.e., if your browser signals DNT, it is a request for the website to not ‘track’ the user. However, it is not a guarantee that the website will refrain from doing so. Advertisers have a horrible track record with privacy concerns of users, so while DNT is a good idea, it may not have much practical value.
There’s an interesting controversy brewing over Roy Fielding’s September 7, 2012, Apache HTTP Server patch which causes the server to ignore the DNT setting on Internet Explorer 10. Fielding is an author of the DNT standard and his view is that DNT should be an informed choice, not a default preference set by a vendor. I figure that since DNT is a voluntary standard, if IE 10 were to have DNT enabled by default, advertisers may choose not to abide by it.
And an excellent article on the topic of tracking.