Date: 2016-03-06

For a number of reasons[0], i've recently set up a new OpenPGP key,
and will be transitioning away from my old one.

The old key will continue to be valid for some time, but i prefer all
future correspondence to come to the new one.  I would also like this
new key to be re-integrated into the web of trust.  This message is
signed by both keys to certify the transition.

the old key was:

pub   1024D/0x55C4B7E1919168E0 2002-02-03 [expires: 2016-09-01]
      Key fingerprint = 2DC6 7C32 FF39 963B 5218  3BC9 55C4 B7E1 9191 68E0
      
And the new key is:

pub   4096R/0xCF9DF318081E69DA 2016-03-05 [expires: 2018-03-05]
      Key fingerprint = CF38 3200 9927 3FB2 FC0B  F070 CF9D F318 081E 69DA

To fetch the full key from a public key server, you can simply do:

  gpg --keyserver keys.riseup.net --recv-key 'CF38 3200 9927 3FB2 FC0B  F070 CF9D F318 081E 69DA'

If you already know my old key, you can now verify that the new key is
signed by the old one:

  gpg --check-sigs 'CF38 3200 9927 3FB2 FC0B  F070 CF9D F318 081E 69DA'

If you don't already know my old key, or you just want to be double
extra paranoid, you can check the fingerprint against the one above:

  gpg --fingerprint 'CF38 3200 9927 3FB2 FC0B  F070 CF9D F318 081E 69DA'

If you are satisfied that you've got the right key, and the UIDs match
what you expect, I'd appreciate it if you would sign my key. You can
do that by issuing the following command:

** 
NOTE: if you have previously signed my key but did a local-only
signature (lsign), you will not want to issue the following, instead
you will want to use --lsign-key, and not send the signatures to the
keyserver
**

  gpg --sign-key 'CF38 3200 9927 3FB2 FC0B  F070 CF9D F318 081E 69DA'

I'd like to receive your signatures on my key. You can either send me
an e-mail with the new signatures (if you have a functional MTA on
your system):

  gpg --export 'CF38 3200 9927 3FB2 FC0B  F070 CF9D F318 081E 69DA' | gpg --encrypt -r 'CF38 3200 9927 3FB2 FC0B  F070 CF9D F318 081E 69DA' --armor | mail -s 'OpenPGP Signatures' <thth@c2226.de>


Additionally, I highly recommend that you implement a mechanism to keep your key
material up-to-date so that you obtain the latest revocations, and other updates
in a timely manner. You can do regular key updates by using parcimonie[1] to
refresh your keyring. Parcimonie is a daemon that slowly refreshes your keyring
from a keyserver over Tor. It uses a randomized sleep, and fresh tor circuits
for each key. The purpose is to make it hard for an attacker to correlate the
key updates with your keyring.


I also highly recommend checking out the excellent Riseup GPG best
practices doc, from which I stole most of the text for this transition
message ;-)

https://we.riseup.net/debian/openpgp-best-practices

Please let me know if you have any questions, or problems, and sorry
for the inconvenience.

Thorsten Thielen

0. https://www.debian-administration.org/users/dkg/weblog/48
1. https://gaffer.ptitcanardnoir.org/intrigeri/code/parcimonie/