FUDCon:Blacksburg 2012 GPG Key Signing Event

Followup
This section was added after the keysigning and contains some useful followup information.


 * Keyring and fingerprints:
 * key and fingerprint list (keys2.pdf)
 * key and fingerprint list sha256sum
 * keyring to import
 * Photos of the key fingerprints on the board.
 * IDs of keys signed: 110810E9 154FDAF0 57E02D57 D72AD0EF 1999A427 85DACC63 B2420431 62A2258E 0E572FDD 024BB3D1 3A7676E7 210BDF5A 9342BF08 1F85118D 07D2F8B4 89CCAE8B 34E36341 390EBBB9 AA482E46 92F0FC09 E65E4F3D FA6C4994 D1F5C478 DAD3DF0E 8B3D4806 9B649644 5B7CBD2B 94BC377E 1285BE7C 750152F1 CD84EE48 DF044293 188C6D38 2486CFD6 D39BE61C C40F2998 C8391120 EBD267AB 6EF4DA92 B4D3D7B0 835D13A0
 * Signing tools
 * caff is part of the pgp-tools package.
 * pius (PGP Individual UID Signer)
 * The strong set in the PGP web of trust
 * Explanation at Wikipedia.
 * analysis of the strong set in the PGP web of trust
 * wotsap (Web of trust statistics and pathfinder) - take a look at the search page for a bunch of interesting things you can do. Here is a matrix of all the key signings from FUDCon.  (Note: It sometimes takes quite a while for new data to show up in the wotsap.)

Original Page
There will be a GPG Key Signing Event held at FUDCon Blacksburg 2012 on Saturday, January 14th, at 1700 (5pm). There will also be a CAcert Assurance event held at 1600 (4pm), immediately preceding this event.

Please sign up below and make sure your key is available on the public keyserver network or make a note here with the url if it is not.

Notice of change
Nick and I are working through the last minute logistics that goes along with the event. We hadn't planned on this event event being so popular! With this in mind we have decided to change the way we are doing the key verifications. Originally we were planning on each person, individually, standing up and reading their key aloud while everyone else verified the paper copy provided for the event. This procedure is used most often and is the most secure. The problem is we now have forty-four forty-nine keys to be signed! That's going to take a while!

For larger parties the recommended procedure is the "hash-based method". The keys will still be provided to everyone on paper. The file will be digitally signed (and electronic versions of the document will be made available). At the event everyone verifies that *their* key is listed correctly on the paper and then the host will read the hash to everyone so that everyone can verify that their copy is correct and has not been modified. Once this happens and everyone is satisfied that they have the correct list of keys then we check everyone's identification.

If anyone has any concern about this procedure please let us know *now* so we can address this.

key and fingerprint list

key and fingerprint list sha256sum

keyring to import

Things to bring to the event:

 * 1) Yourself
 * 2) At least one government issued photo ID
 * 3) Your key's fingerprint
 * 4) A pen/pencil or whatever you'd like to write with....
 * 5) NO computer (or at least leave it in your bag or something, you don't need to actually sign the keys right then)

Why shouldn't I bring a computer?
There are a variety of reasons, why you don't want to do this. The short answer is it would be insecure, unsafe, and of no benefit. For those not convinced, here are some reasons why it is insecure, unsafe, and of no benefit.
 * If people are carrying their secret keys with them and intend to do the signing at the actual meeting by typing their passphrase into a computer, then they are open to key-logging attacks, shoulder-surfing, etc.
 * Someone might spill $beverage on it.
 * Someone might drop it or knock it off the table.
 * Etc

Keysigning Procedure

 * 1) Generate a key/Remember your pass phrase
 * 2) All attendees send their public keys to a public keyserver. For this party, we'll use keys.bz or keys.christensenplace.us. If for some reason you don't want your key to be in a public keyserver, but still want to participate, please let me know.
 * 3) All attendees posts their fingerprint to this wiki page (see below). The event coordinator will compile everyone's key information.
 * 4) The host prints a list with everyone's fingerprint from the compiled keyrings and distributes copies of the printout at the meeting.
 * 5) Attend the party. Bring along a paper copy of your fingerprint that you obtained from your own keyring. You must also bring along a suitable photo ID. Instruct the attendees at the beginning that they are to make two marks on the listing, one for correct key information and one if the ID check is ok.
 * 6) At the meeting the host will distribute the key forms and a hash of that form (also available from this wiki page).  The host will read the hash key out so that everyone can verify they have the same file.  Everyone will verify that their fingerprint is correct on the form.  Once everyone has verified these two pieces of information we will start with the identifications.
 * 7) After everyone has read his key ID information, have all attendees form a line.
 * 8) The first person walks down the line having every person check his ID.
 * 9) The second person follows immediately behind the first person and so on.
 * 10) If you are satisfied that the person is who they say they are, and that the key on the printout is theirs, you place another check-mark next to their key on your printout.
 * 11) Once the first person cycles back around to the front of the line he has checked all the other IDs and his ID has been checked by all others.
 * 12) After everybody has identified himself or herself the formal part of the meeting is over. You are free to leave or to stay and discuss matters of PGP and privacy (or anything else) with fellow PGP users. If everyone is punctual the formal part of the evening should take less than an hour.
 * 13) After confirming that the key information on the key server matches the printout that you have checked, sign the appropriate keys. Keys can only be signed if they have two check-marks.
 * 14) Send the signed keys back to the keyservers.
 * 15) Use those keys as often as possible.

Acceptable Identification
We are not providing specific guidelines on what IDs are acceptable, or how many are required, however, it is generally expected that each participant will be able to provide some sort of government issued photo identification, such as driver's license, passport, etc., matching the name on their key. It is up to the other participants whether or not they will accept your identification.

Uploading your key to a keyserver
To upload your key, do

(Virginia Tech also operates a keyserver at .)

CAcert Assurance
There will also be a CAcert Assurance event.

Key List
Back to FUDCon:Blacksburg_2012.