Simon Rawles's public key
My latest public key has the 64-bit ID 8070 09A7 E884 32C3, which refers to a 3072-bit key created in April 2014. This key is also available from key servers and Keybase.
It is summarised by gpg --fingerprint --list-sigs E88432C3 as follows. Email address are omitted.
pub 3072R/E88432C3 2014-04-01 [expires: 2019-01-01] Key fingerprint = 27BB F8A9 8BE5 6405 513B 7325 8070 09A7 E884 32C3 uid Simon Rawles sig 3 E88432C3 2016-10-14 Simon Rawles sig 3 X F35E7F01 2014-04-03 Paul Magrath sig 3 X F35E7F01 2014-04-03 Paul Magrath sig 3 53BE2E4F 2014-04-19 Adam Forsythe-Cheasley (Dreamer of Dreams) sig 3 94C8733A 2014-08-29 Elmar mc.fly Lecher sig 3 A0EB5B06 2014-09-22 Tim Kovacs sig 3 E88432C3 2014-04-01 Simon Rawles sub 3072R/00B6FCCC 2014-04-01 [expires: 2019-01-01] sig E88432C3 2016-10-14 Simon Rawles sub 3072R/CF1A5685 2014-04-01 [expires: 2019-01-01] sig E88432C3 2016-10-14 Simon Rawles
I mostly use my key for signing, and have the subkey CF1A 5685 for this purpose. However, I don't sign every message, only when it makes sense to, for example when I know the recipient uses PGP and would want to verify that the email came from me. For encryption I use 00B6 FCCC.
Please don't use any of my previous keys. In particular, FAF8 F1C4 4F10 E478 has now expired, and I've no easy way to revoke it. Moral: always generate a revocation certificate when you generate a new key and keep it safe!
What can I do with it?
The main uses are as follows. Click on a word for more help with how
to do it with Unix/Linux
- Verifying that something I've sent you or distributed actually comes from me;
- Encrypting messages, files, backups or other keys to ensure that they remain private as they pass through, or are stored on, public servers, services and storage media;
- Arranging signing of your own key, so that those people who trust my identity are consequently able to trust yours.
The Electronic Frontier Foundation has guides to using PGP on Linux, Mac OS X and Windows.