-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256,SHA1

Hi,

This message is to inform you of the revocation of my OpenPGP key and
the introduction of my new one. Recently discovered SHA-1 checksum
predictability combined with a very old key made me decide to issue a
new set of keys. The old key will be active until August 1st, 2009.

You've probably received this message because your digital signature is
on my old key, in which case you will find your own key attached with a
signature made by my new key.

It would be great if your signature could make it to my new key as well.
Below you'll find a short and clear guide detailing how to import,
verify, sign and publish my new key.

 
 * Importing the new GnuPG key
To import my new OpenPGP key from my website, open up a terminal and at
the prompt type:

  $ wget -q -O- http://www.freshdot.net/ssmeenk.asc | gpg --import -

Or you can get it from the PGP Public Keyservers. For verification
purposes you might want to update my old public key as well by typing:

  $ gpg --keyserver subkeys.pgp.net --recv-key 20CC6CD2
  $ gpg --keyserver subkeys.pgp.net --recv-key 08CEC94D


 * Verification of fingerprints
Assuming you still have the terminal open, you can now verify that this
new key indeed has a signature made by my old key:

  $ gpg --check-sigs 20CC6CD2

Next you could verify that the fingerprints listed below match those in
your keyring by typing:

  [ OLD KEY ]
  $ gpg --fingerprint 08CEC94D
  pub   1024D/08CEC94D 1999-09-26
  Key fingerprint = 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D
  uid       Sander Smeenk <ssmeenk@freshdot.net>
  uid       Sander Smeenk (BIT) <sanders@bit.nl>
  uid       [jpeg image of size 4832]
  sub   1024g/385A594A 1999-09-26

  [ NEW KEY ]
  $ gpg --fingerprint 20CC6CD2
  pub   4096R/20CC6CD2 2009-06-13
  Key fingerprint = 6D40 1A20 B9AA 87D4 84C7  FBD6 F3A9 9442 20CC 6CD2
  uid       Sander Smeenk <ssmeenk@freshdot.net>
  uid       Sander Smeenk (BIT) <sander@bit.nl>
  sub   4096R/7601AC9E 2009-06-13


 * Signing the new key
Please consider signing my new key and publishing your signature, either
by uploading the key to a public keyserver or by mailing it to me.
Sign my new key with your digital signature by typing:

  $ gpg --sign-key 20CC6CD2

Then, upload and/or email the key to the public keyservers and/or me:

  $ gpg --keyserver subkeys.pgp.net --send-key 20CC6CD2
  $ gpg --armor --export 20CC6CD2 | mail -s 'OpenPGP Signature' ssmeenk@freshdot.net


If anything is unclear, please do not hesitate to contact me.

Thanks in advance,

with regards,
Sander Smeenk.

http://www.freshdot.net/key-transition-2009-06-14.txt
http://www.freshdot.net/ssmeenk.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJKNDf7AAoJEPOplEIgzGzS/N0P/RLaJQ9DB+Z7cijUx+FO0gXS
E5ipfJzZvpn3OQIvIZfA40aissi7OObZi3UQqzI4Kn0d2FOCpgNxFg8cPbp/VMK6
lmQqEGTLVjLGjyVUziCUkODjzWi9j9DfZQ9SsQVIX2lqNXkwLNCwu5EmjoWIX8DN
eag3sEjlMN/bAHeQNMAD4uvXuS/PM9y3Z3uUZ8jWgZfxfDbnQAKiPDNxHvjtX5QZ
I+EQN1Gwz65eHhFPZWRBtewZquK2XiL62qYtBB1rO1XBoWU0sw0MHlbCmKlh0FEi
D6ox39T7k9mivMES99uCUT7s706CJaOapyndtjD8/3cwvwqgIiUhi3bGHhDrjux6
WJIDlz4+QMqsTltb6uKBBzBz5wqzplv38ammsyFKR5f+i7N4hZIW9bZ1hC1xs20Q
xZax56k1X+uWanZ+OuUD+gtuq6Wf/IJfT6xji5njnhaTJoyFQ/4XSMMHjNLOIxPX
8av4SHJVvyo7HkWRYvBSDPXr4Amx3yD2YREDCFg4pecNVCVSbJkwlnX9nS+qrCaQ
LwUJ3yVaXtCMI2x9LTo9lC03oO+1hK4dfJpavMNNMh4oz5moRWNESG0YeV9GXWDo
ZeFhSPjuiA5kgVnabMFrk2EtZBmIdyB6bqfxznPk1i+FKjpWKbMwfsFn/VmvMUGi
+FAh/nat/9/0GBm/D1g1iEYEARECAAYFAko0N/sACgkQ1GN+QQjOyU2b5QCdEHFN
j/KY/Czoysf7xQCQCem2hzoAnj/cYIuDj/ExEIq2BzuSM/X/QYWX
=68aY
-----END PGP SIGNATURE-----