I am transitioning GPG keys from my previous 2048-bit RSA key to a new 4096-bit RSA key. I prefer all new correspondance to be encrypted in the new key, and will be making all signatures going forward with the new key. The transition document included below is signed with both keys to validate the transition.

The old key, which I am transitioning away from, is:

pub   2048R/0xF4610DED826B9119 2013-03-31 [expires: 2016-08-23]
      Key fingerprint = 935C EFAB 782A 5EAB 45A2  67F6 F461 0DED 826B 9119

The new key, to which I am transitioning, is:

pub   4096R/0x2275D8A48C8E6314 2016-04-06 [expires: 2018-04-06]
      Key fingerprint = 9EDE B3B1 20E5 2D46 1C7C  5811 2275 D8A4 8C8E 6314

You can fetch the full new key from the SKS keyservers pool using GnuPG by running:

gpg --keyserver hkps://hkps.pool.sks-keyservers.net --recv-key 2275D8A48C8E6314

Note: You’ll need to have the gnupg-curl package installed to fetch keys over HKPS on Debian.

Below is the signed statement, which you can download here:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I am transitioning GPG keys from my previous 2048-bit RSA key to a new
4096-bit RSA key.  I prefer all new correspondance to be encrypted in the new
key, and will be making all signatures going forward with the new key.

This transition document is signed with both keys to validate the
transition.

The old key, which I am transitioning away from, is:

pub   2048R/0xF4610DED826B9119 2013-03-31 [expires: 2016-08-23]
      Key fingerprint = 935C EFAB 782A 5EAB 45A2  67F6 F461 0DED 826B 9119

The new key, to which I am transitioning, is:

pub   4096R/0x2275D8A48C8E6314 2016-04-06 [expires: 2018-04-06]
      Key fingerprint = 9EDE B3B1 20E5 2D46 1C7C  5811 2275 D8A4 8C8E 6314

To fetch the full new key from a public key server using GnuPG, run:

gpg --keyserver hkps://hkps.pool.sks-keyservers.net --recv-key 2275D8A48C8E6314 

If you have already validated my old key, you can then validate that
the new key is signed by my old key:

gpg --check-sigs 2275D8A48C8E6314 

If you then want to sign my new key, a simple and safe way to do that
is by using caff (shipped in Debian as part of the "signing-party"
package) as follows:

caff 2275D8A48C8E6314



Raymond Colebaugh

5-31-2016
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJXT1ZZAAoJEPRhDe2Ca5EZ/pIH/36R+47gZGwv26evtZUEoYp3
Rszw+UgawWXzo1hWZcPhwe+cOkihf4tXr4C21SlvCtnDw5QdqYCZW54etnr1+8VF
5hAjM8vq2CLj4eV2m+DdvIhzIkMtguUZ2pxs5Gi0FHIG1uwUfoGmySpKbkK0ytXe
1vv7LXhaZnHjYK3ReORPt8uHLF2bd8Bgt3KX+yAgfw3OCx9YY/F7iywBt2PIasQG
TVaDh6QzCoH0BLAFzrRKJ5xL+dS/EHYTSZWSngO3ztKElAPO49s8jkMPxxtDXzRY
AniPbke1bhJQg9ZziCzRj0G5uhAWBmpInMnRwG/9CKS6NrbQ5imcEbCYQfu825SJ
AhwEAQEKAAYFAldPVlkACgkQBDYMkUN6/5P+kg//WS0zZ0AGEjAVE/A6iURNn6d+
57K+rs47974pFavJmiecqR6aXwzzI1n5PmOQZXbVOwPzKoaZUCfC7O2MFs3K/9QI
3VzW3N3KmnLF5Uw50uawXHpnnk9gxSTXA2G4lGgWZOoIqjz8JvHH1edLlZwwSFd3
usg7EujpWiQGnBzgk43yzb4p9fsmRs0hl7j6EnQCHtaoOk5uFXfOQrMfPwvc6fSw
6DMb9q0d+QhbHyKaV+NMHEdae+0p9ePfylfWwDlSiUGLBYclE/SbiMPxaokIqben
6wGOlzM3spaLRUS8DCB8k8v6YuDwE4LVEAX3IDHifiHcS/4mFYNHtt0o0vSCfEL1
Fej5rB5txWFJSuufOR/PKbqLYA3q+zZm+rQUXj9+4+RKuXpVNS0S2s8KGXdCuhlE
GLo8jerPk6rqN6tTOqQKpQS1E7ZEwY5yC/Po9EdoKKcEbpyWS7542cZqBh2+0y6N
dFBxfYRDixae9Ksz8EjFqMO6F98Li1He8+eiWrTBpBwbRry2YtBXiLIqPPoozgCB
54n/fbqULlIm9nI5oQ52jukh8e/oOZqTRxw2fwOPnN61ExnSMagAzctsqR9cfR1I
CyJuKj+Nvl2bAfkUbQRbDo9AEIksrPF1D+ytM/6mjXcGoySVirq8dyuAtszbEuPr
osjpPA03ZnsZy8P45XU=
=UHxF
-----END PGP SIGNATURE-----