FUDCon:Lawrence 2013 GPG Key Signing Event

Keyrings

The keyring has been updated and includes the extra people from the event.
Please verify these keys against your notes before signing.

• Keyring
• Keyring Signature
• Keyring Hash (sha256sum)

What

What is this key signing thing all about? This is an event used to create trust paths for the OpenPGP Web of Trust. Events like this help create those trust paths that allow you to trust e-mail messages and files received over the Internet (or by other means). While trust is increased substantially when you receive a message or file from some you have exchanged key signatures with the web allows you to trust others by trusting the path that is created between two keys using others as trust agents. How well you trust those that create that path is up to you but it does help.

Who

Anyone attending FUDCon Lawrence, or who is just passing through the greater Lawrence, KS area, may attend this event. It is open to the public. We ask that you register ahead of time so we'll be prepared and you won't have to be the odd one who doesn't have their key already in the keyring and will have to read their entire key aloud while everyone has to write it down quickly.

Signing up

Please sign up below and make sure your key is available on a public key-server or make a note here with a URL to the public key.

Where

The key signing event will be held at FUDCon Lawrence in 2111 Learned Hall on the campus of the University of Kansas (KU).

When

Saturday, 19 January 2013 from 16:30–17:20

How

Participating in a key signing event is quite easy and signing the keys afterwards is even easier.

Things to bring to the event:

• Yourself
• At least one government issued photo ID
• Your key's fingerprint (gpg --fingerprint keyid) printed or written down
• A writing instrument (pen or pencil)

Things to *not* bring to the event:

• A computer

Why you shouldn't 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 drop it or knock it off the table.
• Etc

Key signing Procedure

1. Generate a key
2. All attendees send their public keys to a public keyserver. 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. 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 key-servers.
15. Use those keys as often as possible.

Acceptable Identification

There are no hard and fast rules of what forms of identification are acceptable to any specific individual. Generally speaking the following forms of identification should be acceptable:

• Passport
• Driver's license
• State identification
• Other forms of photo identification

Uploading your key to a keyserver

To upload your key, do gpg --keyserver pool.sks-keyservers.net --send-keys 0xYOURKEYID

Key List

Name	FAS Username	Key ID	Fingerprint
Eric Christensen	Sparks	0x024BB3D1	097C 82C3 52DF C64A 50C2 E3A3 8076 ABDE 024B B3D1
Nicholas Bebout	nb	0x110810E9	167B 4A54 236B BEAA 37DC CD92 ED14 D5E7 1108 10E9
		0x76186148	047C 67D1 0C5E 362C 2132 A7FC 043E DE20 7618 6148
Zachary Oglesby	zoglesby	0xF20C4707	AC8D 352D 380B B89B A3C2 7F43 DB36 FD89 F20C 4707
Matt Domsch	mdomsch	0x92F0FC09	17A4 17D0 81F5 4B5F DB1C AEF8 21AB EEF7 92F0 FC09
Jared Smith	jsmith	0x210BDF5A	1E46 74AA A394 0EAA 6596 FDF0 7D9D 159F 210B DF5A
Simon Sekidde	sekidde	0x94BC377E	5848 958E 73BA 04D3 7C06 F096 1BA1 2DBF 94BC 377E
Ralph Bean	ralph	0x971095FF	9450 4C3A E11D D197 9200 58AB A90E D7DE 9710 95FF
Andrew Wafaa	- - -	0x3A36312F	7982 F65B 0DD6 B382 8681 E61E 5153 D01B 3A36 312F
Jeff Bastian	jbastian	0x497F4595	52E2 C044 D7DC 9BB4 9C15 3A65 7512 3214 497F 4595
Ryan Rix	User:rrix	0x24c87ae0	260c 1c91 be23 8d4d 8d10 f6b1 67f7 84b9 24c8 7ae0
Kévin Raymond	shaiton	0xA5BCB3A2	3F17 ECD7 8860 FDEE 06D4 4EDD 9736 1B85 A5BC B3A2
Garrett Holmstrom	gholms	0xDF044293	73CF 446C 8F09 A9DB 9D44 A020 9278 34B6 DF04 4293
		0x188C6D38	A915 7737 6560 BA04 505E 7888 6EAC 46AB 188C 6D38
Jeff Ollie	jcollie	0x6D97044E	A8CF 5B72 ABC3 9A17 3FEA 620E 6F86 035A 6D97 044E
Robert Whitinger	robertjw	0x7D47FF3D	F04A D66F 57C3 FEFE 06A0 896C 3050 9249 7D47 FF3D
Clint Savage	herlo	0x8A8F1D53	C563 4FBB E5BB F085 B1BE 70BA 6DD1 926E 8A8F 1D53
Ivan Makfinsky	makfinsky	0xDF705B87	B1EB 2CD3 2849 82BA 0341 5A9E 0018 A602 DF70 5B87
Dan Mashal	vicodan	0xDE341682	2C8A 8515 B06B FEC4 7F3E 13C9 78E6 5569 DE34 1682
Kevin Fenzi	kevin	0x0FFBBB5E	A6EA F625 0EBB F132 A8A9 32AD DE29 827B 34E3 6341
Miloslav Trmac	mitr	B38479DF	C197 6D9E D91A 7459 CBCE 5314 5A33 F660 B384 79DF
Stephen Gallagher	sgallagh	36BAA3A3	34BF DEA2 09B1 EA2E 9FDC 2E53 7A25 5562 36BA A3A3
Aurélien Bompard	abompard	B9BF64AD	03E9 93DA D931 3E51 8FCA 35FF 3158 4CFE B9BF 64AD
Jon Stanley	jstanley	0x1F85118D	84A5 3E8C 66E7 53B3 C029 33B8 7111 2949 1F85 118D
Ricky Elrod	codeblock	0xDAD3DF0E	9739 5A0F BDC8 1D20 A137 CDCC 0027 10B0 DAD3 DF0E

CAcert Assurance

There will also be a CAcert Assurance event.

Back to FUDCon:Lawrence_2013.