by George Brocklehurst (@georgebrock)
Presented at New York Emacs Meetup,
The first useful function PGP provides is encryption: if I have a user's public key, then I can encrypt a document so that only they can decrypt it.
The second useful function PGP provides is signing: I can sign a message or document using my private key, and anyone with my public key can verify the signature.
A verified signature means two things:
Behind the scenes, signatures use encryption:
In other words: what practical uses do encryption and signing have in your every day interactions with computers?
passcommand-line utility provides convenient tools for storing your passwords in PGP encrypted files.
There's a problem with all of this, though: to send someone an encypted message, or verify their signed message, I need to know that I have their public key. Unfortunately, since I don't have their public key yet, I don't have a verifiable way to get their public key from them.
PGP provides a solution to this problem.
To follow these examples, you will need to have
$ gpg2 --gen-key gpg (GnuPG) 2.0.26; Copyright (C) 2013 Free Software Foundation, Inc. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Please select what kind of key you want: (1) RSA and RSA (default) (2) DSA and Elgamal (3) DSA (sign only) (4) RSA (sign only) Your selection?
You probably want to stick with the default here: just hit return
RSA keys may be between 1024 and 4096 bits long. What keysize do you want? (2048)
The key size is a balance between a large, secure key, and small, easily transmitted signatures and encrypted documents. Again, if you don't have a strong preference the default is probably fine.
Please specify how long the key should be valid. 0 = key does not expire
= key expires in n days2y Key expires at Wed Dec 7 23:38:11 2016 EST Is this correct? (y/N) y w = key expires in n weeks m = key expires in n months y = key expires in n years Key is valid for? (0)
In this case, it's useful not to follow the default. If you lose your private key for any reason, the the public key could live forever, inviting people to send you encrypted messages you can never decrypt. If the key expires, this problem will go away on its own in time, and you can always extend the expiry date if you still have the private key.
GnuPG needs to construct a user ID to identify your key. Real name: Testy McTest Email address: email@example.com Comment: You selected this USER-ID: "Testy McTest <firstname.lastname@example.org>" Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
After entering your identifiable information, you will be prompted for a passphrase. You should pick something longer than a password.
After that, you may need to use your computer for a while for GPG to collect enough random data to generate they key. Just move your mouse a lot; it will finish eventually.
The final output you will see contains your key ID:
pub 2048R/12C595E9 2014-12-09 [expires: 2016-12-08] Key fingerprint = 6105 5591 CD4B 6D5A 4142 AC0C D387 8005 12C5 95E9 uid [ultimate] Testy McTest
sub 2048R/CE1346C0 2014-12-09 [expires: 2016-12-08]
In this case the key ID is
12C595E9. We can use that key ID to publish the newly generated public key to a public key server:
$ gpg2 --send-key 12C595E9
Since this is just a demonstration, I won't really be publishing this key.
Before you sign someone's key, you should verify their identity as best you can. Once you're confident you know who you're talking to, you can download their public key. In this case, I want to sign Harry's key:
$ gpg2 --search email@example.com gpg: searching for "firstname.lastname@example.org" from hkp server keys.gnupg.net (1) Harry R. Schwartz <email@example.com> Harry R. Schwartz <firstname.lastname@example.org> 4096 bit RSA key 25AE721B, created: 2014-01-30 Keys 1-1 of 1 for "email@example.com". Enter number(s), N)ext, or Q)uit > 1 gpg: requesting key 25AE721B from hkp server keys.gnupg.net gpg: key 25AE721B: "Harry R. Schwartz <firstname.lastname@example.org>"
Now that I have the key, I can sign it. Using the
--ask-cert-level flag lets me specify the level of certainty I have in signing this key. The first thing I want to do is verify that I have the right key:
$ gpg2 --ask-cert-level --edit-key email@example.com gpg> fpr pub 4096R/25AE721B 2014-01-30 Harry R. Schwartz
Primary key fingerprint: 1B41 8F2C 23DE DD9C 807E A74F 841B 3DAE 25AE 721Bgpg>
At this point I should stop and check that the fingerprint I have in front of me matches the one that Harry gave me when he told me which key is his. When I'm sure they match, I can move on to signing the key.
gpg> sign Really sign all user IDs? (y/N) y
GPG will now prompt you for your passphrase, and sign the keys. Finish the process by saving the signature, and pushing the key you just signed up to a key server:
gpg> save $ gpg2 --send-key 25AE721B