updating a bit for ACNA2014
|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|We will have a PGP Key Signing at the !ApacheCon North America 2014 conference. It will happen Tuesday night, after the Welcome Reception, at 7.30pm. We'll be in Galleria 2, one of the session rooms.||We will have a PGP Key Signing at the !ApacheCon North America 2014 conference. It will happen Wednesday evening 5:30-6:30pm in the Platte River room.|
We will have a PGP Key Signing at the ApacheCon North America 2014 conference. It will happen Wednesday evening 5:30-6:30pm in the Platte River room.
Note that this event is usually hosted by Sander Temme, but as he cannot be at the conference this year, it is hosted by David Nalley this time. The procedure will remain the same, so as this wiki page except for this difference.
A GPG keyring with all the public keys on the key list will be posted at http://people.apache.org/~ke4qqq/2014NAKeyring/ once keys are collected.
Remember: you can always sign keys individually throughout the conference. Feel free to ask around: if you meet other people from your project in person, they often will be willing to sign keys. Some people print up simple business cards or small slips of paper with their name, email, and PGP key fingerprints to pass out.
What is a PGP Key Signing?
This is an opportunity for committers and general attendees to sign each other's PGP or GPG keys and grow our Web Of Trust.
We will try to have time both for newbies and experienced folks. Remember too that you can sign other folk's keys at any time, not just during official events. Note that we should probably save any 'how do we encourage Apache's web-of-trust' discussions or the like for another time, so we can ensure the signing party goes quickly. Oh, a picture of the somewhat-current web-of-trust within Apache folks (well, at least those who have put stuff in KEYS files) is kept at http://www.apache.org/~henkp/trust/apache.html
Committers should see https://svn.apache.org/repos/private/committers/docs/pgp-key-signing.txt for details.
Some background on what a keysigning party is:
http://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html (how to sign using GPG)
http://www.faqs.org/faqs/pgp-faq/ (general PGP info)
http://wiki.apache.org/incubator/SigningReleases (how we sign Apache releases)
This year, a lot of folks may have new keys because they have been told that longer keys and hashes are better. Refer to the following URL: http://www.apache.org/dev/key-transition.html for information about this transition.
Should you wish to participate, here are the instructions:
E-mail your key to David at firstname.lastname@example.org as soon as possible, but definitely before 3pm Tuesday, April 8th because after that time I'm going to compile the list. To get your key in emailable form use (PGP works similarly):
$ gpg --armor --export KEY_ID > mykey-$USER.asc Then just copy and paste the contents of mykey.asc in an e-mail to me. The key list, and a PGP (or GnuPG) keyring export will be available for your convenience at the following URL:
The PGP Keysigning Event
- Everybody gets a print-out of the key list. I will make those and have them available.
- The key entries on the printout are numbered. All participants line up in the order of their keys.
- The list will also be on the projection screen (assuming we get a projector, and get it to work in a timely fashion). You verify that your entry on the printout is correct: that the key ID, fingerprint and name + e-mail information match what you submitted. You also verify that your entry on the printout is the same as your entry on the screen.
- I will call out the name of each participant, in order. When your name is called, tell all participants loudly whether your information as verified in step 3 is correct. Stand up and wave your arms if you want to, it's very important that the other participants see and hear you assert that this key is yours.
- As participants positively verify their information, check whether their entry on the screen matches their entry on your printout. If so, you can place a check mark in the first of the two boxes at the right of your printout. Why do we do this? To make sure we all have the same list, and that the list is correct. You are verifying that I didn't make any mistakes compiling the list, or that I didn't nefariously doctor anyone's key.
- Once everyone's key data has been verified, the fun part starts. Everybody gets up, and forms a line in the order in which you appear on the list. Once the line is formed, we'll double it: the first person in the line walks past the line until he or she ends up next to the last person, and everyone follows until we have a double line, half as long. Then, everyone makes a quarter turn so that they face the person next to them rather than the back of the person in front.
Now, everyone in the line is going to identify every other participant. Start with the person standing (conveniently) right in front of you, then move one person to the right and repeat until you have met everyone in line. The line will fold upon itself in caterpillar fashion: once you reach the end just turn around and start going to the other side (the next person you "meet" will be your neighbor). As you make positive identification of a person, you place a check mark on their line in the second box at the right of your printout. How do you identify people? That is up to you. Some folks check each other's passport or driver's license, but that means you trust the government to provide positive identification. And who trusts the government anymore these days? Some folks just know each other, or, if they haven't met before the conference, have gotten to know each other well enough to assert that they know who they are. It's really up to you, and if you can't identify the other person to your liking, don't place that checkbox and don't sign their key.
- After everyone has met everyone else, you should have a list with a bunch of checkmarks in the right columns. Put this list in your pocket. Back in your hotel room, pull out the list, and sign the keys that you gave two checkmarks. Then, upload the signed key to the following two keyservers:
What you should bring:
- Yourself. Obviously.
- A cookie from your lunch box
- A pen. Bring two, so you can give one to your neighbor in line who forgot to bring one.
- Something to identify yourself with. Your face, your voice, unique pheromone pattern, etc. The better you can convince your fellow participants that it's really you, the more signatures you will get.
- No computer.
No computer? No. We're not running the PGP (or GnuPG) program at the Keysigning Event, and we're not actually signing keys at the event. You're standing in line, juggling paper, pen and your beverage of choice... no way you can manipulate a computer while that's going on. And you want to be paying attention too, especially during the key verification phase. So, no Slashdotting either. Don't worry, it'll be OK. We all spend too much time with our computers anyway.
This ends the PGP Keysigning event.
The Actual Signing of Keys
Notice anything conspicuously absent from the Keysigning Event? Right, no keys are actually signed at the event. The event is purely meant to verify participants identities and to connect persons to keys. After the event, you sit at your computer, with your list of fingerprints, and sign the keys of everyone on the list whose identities you verified. Then, mail the signed keys back to their owners. You could upload a signed key to your favorite keyserver and hope the owner finds it, but mailing it directly back to them is much more straightforward. And it may prompt the other person to return the favor.
One final note: everyone has their own criteria for signing keys. Some people are fairly lax, and will sign anyone's key that they've met, or even just exchanged regular emails with. Other folks will only sign keys when they can prove your identity, or will use your key to send you a couple of messages over a period of time to verify that you use it. So don't be offended if someone doesn't sign your key immediately after the event.