On Mon, Apr 12, 2004 at 05:53:55PM -0400, Charles R. Anderson wrote:

Who wants to do a PGP Keysigning? It would involve advance preparation from everyone who would like to participate. By now I'd imagine most of you have gotten your feet wet with GnuPG :-) If not, see:

http://www.wlug.org/files/pgp-slides/index.html

If there is interest, please let me know in the next couple days so I can organize the procedure and send out instructions.

I'd be game. Who wouldn't want to travel to Worcester with passport in hand? ;) BTW: I ran the 2 keysignings at LISA 03 and had http://www.biglumber.com/ recommended to me as a useful site to organize key signings in the future. I haven't poked around it too much, but it may make life easier. :) -- Randomly Generated Tagline: How do Crays and Alphas handle the POSIX problem? -- Larry Wall in <199709050042.RAA29379@wall.org>

Ok, I'm not sure if this will fill the meeting's entire timeslot, so feel free to come up with another discussion topic. If you want to participate in the PGP Keysigning Party, here's what you need to do. This is based on GPG Keysigning Party HOWTO (http://www.cryptnet.net/fdp/crypto/gpg-party.html) which I highly recommend you read if this is the first time you are using GPG. You'll need to do these ahead of time *before* you arrive at the meeting, preferrably on a secure, local terminal (i.e. not in a computer lab or the public library or remotely from another system, or on a system running an insecure OS). 1. Generate A Key Pair gpg --gen-key (Default values are good. I would use 2048-bit key.) 1.5 Generate a revocation certificate gpg --output revoke.asc --gen-revoke <keyid> (save this revocation certificate offline in multiple places, print it out, put it in your safe, etc.) 2. Send Public Key To Designated (pgp.mit.edu) Keyserver gpg --send-key --keyserver=pgp.mit.edu <keyid> 3. Send Public Key Info To Coordinator Please email me (cra@wpi.edu) the output of: gpg --fingerprint <keyid> 4. Print a paper copy of your Public Key info from Step #3 I'll collate the keys and prepare copies of the public keys for all participants to use as a check list. Example output from Step #3: pub 1024D/49BB5886 2001-04-11 Charles R. Anderson <cra@wpi.edu> Key fingerprint = EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 sub 2048g/B0817A13 2001-04-11 In this case, my <keyid> is 49BB5886, which is the same as the last 8 hex digits of the fingerprint. You can use your email address as <keyid> in the command if you forget your actual key id. So my full key information is: Key ID: 49BB5886 Key Type: DSA Hex Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 Key Size: 1024 bits (The DSA key is always 1024 bits. The ElGamal Encryption key is 2048 bits in my case, but isn't needed for the keysigning party.) 3.2 What participants should bring to the party 1. Themselves - you cannot participate virtually 2. Two forms of positive picture ID - a driver's license and passport are good 3. Key ID, Key Type, Hex Fingerprint and Key Size info (NOTE: please print out your own copy of your key to compare against my copy when you arrive.) 4. A Pen/Pencil 3.3 What Participants Should Not Bring to the Party 1. A Computer