It is very important that you
capture your public key fingerprint in a human-readable
form. For example, if your key's e-mail address is user@domain.tld,
you can run
% gpg --fingerprint user@domain.tld
The response should be something like
pub 1024D/3970227D 2003-05-12 Sam User <user@domain.tld> Key fingerprint = 83D9 A36B 7DA5 3C2B 8EFD 6ADB B778 07E6 3970 227D sub 2048g/2E465894 2003-05-12
Pretty Good Privacy(tm) Version 6.5.8 (c) 1999 Network Associates Inc. Export of this software may be restricted by the U.S. government. Looking for user ID "user@domain.tld". Type bits keyID Date User ID DSS 769/1024 0xA2F355EC 2005/04/23 *** DEFAULT SIGNING KEY *** Sam User <user@domain.tld> Key fingerprint = 21 52 CD 03 DF C5 16 2F 1C 8B A4 A1 D9 07 B6 B6 A2 F3 55 EC
You need to obtain your fingerprint from a trusted source (i.e., your key ring) and transport it securely to the key-signing party--perhaps in your wallet.
To register for the event, submit your public key to our temporary local key server. Here are your options:
For example, if you use
GPG and your key's e-mail address is user@domain.tld, submit
via
% gpg --keyserver facloan14.fac.cs.cmu.edu --send-keys user@domain.tld
The response should be
gpg: success sending to `facloan14.fac.cs.cmu.edu' (status=200)
If you use a GUI PGP client, the server's hostname is facloan14.fac.cs.cmu.edu,
it speaks the HKP protocol, and it's running on the standard port (11371).
Whichever way you registered your key with us, you can verify that your key made it into the database by entering your e-mail address into this form.
Now you can go back to the main page and read the event guide.