-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I have decided to create a new OpenPGP key and migrate from my old key
due to the old key expiring in a year. I have used a pristine OS on an
offline host to create the new Signing Master key, and the signing and
encrypting subkeys. My primary email address is the only one
associated with my new keys right now.
This message has been signed by both the old and new key so that you
may verify that I am in control of both of them.
Messages encrypted to my old key will still be accepted, but no new
signatures will be issued from it. I will be going over my public
keyring and issuing new key signatures to replace old ones after
performing verification on each key to ensure it is still valid.
For reference, my old key is:
pub 3072R/A84A7140 2009-09-21 [expires: 2013-09-20]
Key fingerprint = F617 AC77 6E86 5830 08B8 BB96 E7A4 C6CF A84A 7140
uid Stefan Marsiske
sub 3072R/B3348C90 2009-09-21 [expires: 2013-09-20]
And the new keys are:
pub 8192R/CA0557EF 2012-06-17
Key fingerprint = FD52 DABD 5224 7F9C 63C6 3C12 FC97 D29F CA05 57EF
uid Stefan Marsiske
sub 4096R/79D8E883 2012-09-06 [expires: 2017-09-05]
sub 4096R/128BAA40 2012-09-06 [expires: 2017-09-05]
You may obtain the new key either from a public key server:
gpg --keyserver pgp.mit.edu --recv-key 0xFC97D29FCA0557EF
Or by downloading it from my website:
wget -q -O- https://www.ctrlc.hu/~stef/ca0557ef.pgp | gpg --import -
My new key has been signed by the old to indicate that I am authorizing
this change. If you would like to verify the signature:
gpg --check-sigs 0xFC97D29FCA0557EF
If you have previously signed my key, I would appreciate your signature on
my new key -- after, of course, you are confidant that I am actually in
control of the new key. Note that, as stated above, not all of the UIDs
present on the old key exist on the new key. If you have previously
signed only UIDs that have not been transferred, please feel free to email
the address on the key to verify that I am also in control of that
address. My reply will be signed by both my old and new keys.
You can sign the new key by issuing:
gpg --sign-key 0xFC97D29FCA0557EF
And finally, making this signature public by sending it to a key server:
gpg --keyserver pgp.mit.edu --send-key 0xFC97D29FCA0557EF
After doing this, I would be grateful for an email notice that you have
signed my key, but you do not have to notify me if you do not want to.
That is all. Please do not hesitate to email me with any concerns.
-- Stefan Marsiske
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCgAGBQJQitmLAAoJENjR+BoSi6pAWVUQAK7oxrbY4HUNI/sxM2b0Gf7P
ow3A/snj5xUiUvhvfWTmXt2gD9pksuoEZkRsu26Qa8ttzRZCnFGbad4tXNASY8w/
XIl7bJXoGg3vA/V+kUobMgVIlRdyrscBKjjEmr6Aa0QedZSWnik0sHR2X2h4z5WE
JrTIrlUpgeDwDwuZUUbYbReKzznEiAO+ZNIOo7SphjI5JNUZ2qyrN45Samc28LAv
k4PBN8xY8O6NsI273TY1AZ2Os8Psv55GsTKgl7n375h2wDIdCCuoZG06d8CpWAZp
SQzrJdawRoEf878MVB9u3pz8XPyBgX6nIUpTxZJQ6ty9STo+hJLU3TidumtsvLwV
06Nkb1XvpTfQ9i9HRsQOcksF4MbDiuDMvPiq7oT30YYCU2Jka0c2F5tz6SgfyRfy
u1FkG6P1ADKAFht9r5s7tTomQwU5jiCeV4ydjceEfXOTu214O0o11oePhe0n6EMT
oV7jHzke4dvFPaF7nWjNuBW9vQYWlDQavrHLmAgQucNlLZGapuDyDSNucQ1KLlyH
l8qlD8lnlk+zH62JOYyS9N7+idFE+YjIA7Z8fD8W/72JmeFqlHUWd7cEdat6Y8SY
AfVKGuiPTsM9qCsXbZQWchqQ6+VYh0qJKYXf/ood9azykVXltqkBW+eaNbhgujVQ
RUxjgnvBi1D3VVcqsw7K
=/V6H
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQGcBAEBCgAGBQJQitpQAAoJEOekxs+oSnFAfrIL+QH/KiaI3AwtRFbjH5LZJgeR
zUcQJVwmC/tUyzBl7o8ABP0NChlF4Su5eRXihzbPTaVYdF32iVoKswGLUR/eq6iE
QRs1D6J7GcwfdelSQ8zRpFGw7MiTOtcVOmMB1EedGlR1SqdDtqqbZO+y3j6q8XcQ
2Ifgta7aYBnuarsy4/M6AvNXt3S3CR791QNmoLaGRz5LhDUzyQuxAqT+qPlK/6Cl
ioX2bwrodZfmf8m+ixuiPGx3MIG3ksd26WpecMPg+O+L7K3d5KlhOE2iQHAkGAA5
SLcLAupMmhtcLrtdK2/p1feAalUFYtFkM96rQHtaMOxfLaMNPgXMEvIBSCynkGjt
7scLw45z6HMj7rJjWIZY1KQjyTcZS4xIf8nWgDqanb8t6ETx4nSFVzGDl/RLroyx
XUZqpZmsXWL90ryNY7JUQfpWdMjtJsyznvj/6tcs4rkLrpbi6T/8tQUszvdGlY3D
dVh8f8k5+MRSQiv9sNWYcGDHtC/51V4/RRqYFbzjRg==
=qKYL
-----END PGP SIGNATURE-----