By Bri Hatch.
Summary: Verifying public keys.
Verification is part of any security system. SSH, FTP, POP, and IMAP servers ask for your password before it lets you log into the machine, get your files, or snag your email. NTP can be configured to require keys before it'll let you mess with it's clock. CIFS requires a password or kerberos tickets before granting you access to shares.
Now some of the above examples can be done without a password, true enough. FTP can use the anonymous account. NTP keys are seldom used between end hosts and stratum 2 servers. CIFS guest shares are (overly) common.
PGP falls into the same boat. In order to use PGP safely, you need to verify that the public key you have truly belongs to the individual or organisation you expect. Remember - anyone can create a PGP key with any name/comment/email data that they want. I could create a key with "George W. Bush (Texan) email@example.com" just as easily as he could.
To verify the key, you need to communicate with the actual party in a way that you know it's them. For example:
The important thing is that you have verified that they are in fact the person they claim to be, and that they are the person you are communicating with when you verify the key.
So, having established communication with the person, you need to
exchange the information about your key. There are three crucial
parts of the key, and you can find them in
$ gpg --fingerprint firstname.lastname@example.org pub 1024D/D5D3BDA6 2003-12-14 John Doe (My First PGP Key) <email@example.com> Key fingerprint = 0E43 DC31 C484 431C 5B07 3875 7B2D D3D8 D5D3 BDA6
The important parts are:
It is not likely that you'll be sitting down at your computer when the party to be verified has their key on them. Instead, you're more likely to meet at lunch, or a PGP keysigning party. In these cases, the easiest way to exchange keys is to have printed out your fingerprint information ahead of time on a piece of paper, verify they are whom they claim to be, and exchange paper fingerprints. You should do something, such as sign the paper itself, to be sure you remember that you've verified this key.
Once you have the person's fingerprint, having already been verified with the human himself, you can sign the key at home at your leisure.
So, how do you sign the key? That's next week's topic...
 Ok, perhaps I'd be able to do so sooner than the current US Commander in Chief. They've never been known for their technological savvy. In fact, I think I could handhold my 4 year old daughter through it faster.
 You wouldn't want to verify and sign the key with them there anyway, to avoid them shoulder surfing your password.
Bri Hatch is Chief Hacker at Onsight, Inc and author of Hacking Linux Exposed and Building Linux VPNs. He'll be giving a talk at LinuxFest Northwest (www.linuxnorthwest.org), titled "Practical SSH - Encryption, Tunneling, and Automation." And if anyone wants a ride up from Seattle, drop me a line. Bri can be reached at firstname.lastname@example.org.
Copyright Bri Hatch, 2004
This is the April 14, 2004 issue of the Linux Security: Tips, Tricks, and Hackery newsletter. If you wish to subscribe, visit http://lists.onsight.com/ or send email to Linux_Securityemail@example.com.