Keysigning Party @ LinuxTag 2005

Kultiges Zusammensitzen und gemeinsames Murmeln magischer Zahlen.

Gert Döring, FdI 95

The party will be on Saturday, June 25th, at 14:00.

What is/Why keysigning?

How

The party will be conducted using Len Sassaman's Efficient Group Key Signing Method:

• If you intent to participate please send a mail with nothing but your KeyID (or KeyIDs) in the body to ksp-lt2k5@palfrader.org by Saturday, June 18th, 2005.
  

  Subject does not matter. If you have more than one key put each KeyID into a line of its own. Make sure your key can be found on hkp://subkeys.pgp.net/.

  If your key is not listed at http://cvs.noreply.org/svn/ksp/trunk/2005-lt/keys/ within three or four days, please contact me personally.

  This deadline has now passed. If you haven't submitted your key yet, it's too late.

  If you still want to participate, please follow the points listed below, like everybody else (i.e. grab the file, check the checksum and bring the printout with you). This is so that you can sign other people's keys.

  In addition print your key information on small paperslips and bring enough for everyone (say 150 or so).

• By Monday, June 20st, you will be able to fetch both the complete keyring with all the keys that were submitted along with a text file (ksp-lt2k5.txt) giving the fingerprint of each key on the ring.
• At home, verify that the fingerprint of your key in ksp-lt2k5.txt is correct. Also compute the MD5 hash of ksp-lt2k5.txt. One way to do this is with md5sum invoked as follows:

  % md5sum ksp-lt2k5.txt

  or

  gpg --print-md md5 ksp-lt2k5.txt

  Just to be sure that you have no problems with the download, here is the MD5 hash as we have calculated it:

  MD5 = 06 43 20 E0 CC 22 6C .. .. .. .. .. .. .. .. ..

  Note that this is just a hint - you must do the check yourself.

  We will also read the SHA1 hash, so you should calculate that too (sha1sum or gpg --print-md sha1).

• At the LinuxTag, come with the hash you computed and a hardcopy of ksp-lt2k5.txt.
• A reader at the front of the room will recite the MD5 hash of ksp-lt2k5.txt. Verify that the hash recited matches what you computed. This guarantees that all participants are working from the same list of keys.
• In turn, each participant will stand and acknowledge that the fingerprint of his or her key listed is correct. Mark the key verified on your hardcopy. Since we already ensured that everybody has the same copy a simple statement like "yes, this information is correct" is sufficient.
• The next step is to verify each participant's identity by checking her passport or similar form of ID.
• Later that evening, or perhaps when you get home, you can sign the keys which you were able to verify hardcopy. After you signed a key send it to its owner together with your signature.

• ksp-lt2k5.txt - List of participants
• ksp-lt2k5.asc - participating keys
• ksp-lt2k5-full.asc - participating keys with all the signatures they already have (5 Megabytes)
• ksp-lt2k5-full.asc - participating keys with all the signatures they already have, bzip2 compressed (3 Megabytes)

Summary: What to bring with you

• A printout of ksp-lt2k5.txt; check that your fingerprint is correct.
• The MD5 Hash you made of ksp-lt2k5.txt so that we can ensure we are all working with the same copy.
• Some form of government issued ID (passport or similar).

Relevant Information and Sources for More Information

Keyservers

The only keyserver rotation you should use is subkeys.pgp.net, or random.sks.keyserver.penguin.de if you insist. Any of the servers in this rotations is fine.

Please, please, pretty please with a cherry on top, do not use other rotations, like keyserver.net or wwwkeys.pgp.net: They all mangle keys in various ways, including but not limited to dropping subkeys, moving binding sigs around between subkeys, duplicating user ids, modifying signature subpackets (dropping non-hashed data), calculating KeyIDs wrong (for v4 RSA keys), rejecting keys with attribute UIDs (such as photo ids), or don't sync with the rest of the network.

Please use subkeys.pgp.net.

caff

CA Fire and Forget is a script that helps you in keysigning. It takes a list of keyids on the command line, fetches them from a keyserver and calls GnuPG so that you can sign it. It then mails each key to all its email addresses - only including the one UID that we send to in each mail, pruned from all but self sigs and sigs done by you.

Download it: caff.

Depends: gnupg (>= 1.3.92), perl, libgnupg-interface-perl, libmime-perl, libmailtools-perl (>= 1.62)

gpgsigs

Uli Martens wrote a small perl script that, given a key ID and ksp-lt2k5.txt tells you which keys (UIDs) you already signed by annotating the UID with (S).

153  [ ] Fingerprint OK        [ ] ID OK
(S)  pub  1024D/52698E9F 2001-11-07 Uli Martens <uli@youam.net>
     Key fingerprint = A48F 8894 37A0 FDE9 60D5  212A 2A58 CEAA 5269 8E9F
(S)  uid     Uli Martens <isax@gmx.de>
( )  uid     Uli Martens <u.martens@youam.com>
(S)  uid     Uli Martens <u.martens@scientific.de>

Download it: gpgsigs.

It requires perl, gnupg (>=1.2.x) and either Locale::Recode (in Debian Package libintl-perl, in testing and unstable) or recode (Debian Package recode).

A word on GnuPG versions

There is a newer GnuPG package at backports.org:

deb http://www.backports.org/debian/ woody gnupg

Keyring analysis