Differences between revisions 4 and 5
Revision 4 as of 2007-11-15 18:18:45
Size: 2009
Editor: 1023chost225
Revision 5 as of 2009-09-20 23:08:55
Size: 2009
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

All About Keys and Key Signing

How to Sign

Thanks to Jean Anderson for this description of the signing process:

The ApacheCon key signing only verifies the fingerprint and id of the person -- everybody gets a hardcopy printout with name, email, and fingerprint. Incidentally, the "key id" is the last 8 digits of the fingerprint.

The electronic signing occurs later. Here are the steps somebody might use to sign my key.

  1. Import Jean's public key from pgp.mit.edu:
    • gpg --keyserver pgp.mit.edu --recv-keys 9958C626

  2. Verify the fingerprint -- does it exactly match the hardcopy from the ApacheCon key signing?

    • gpg --fingerprint jta@apache.org

  3. Sign Jean's key:
    • gpg --sign-key 9958C626

  4. Upload the signed key:
    • gpg send-keys --keyserver pgp.mit.edu 9958C626

Another "style" is to not upload the signed key, but to export it and email it to the signee to upload (KEYID below is the id of the signer):

gpg --armor --export jta.apache.org > 9958C626_signed_by_KEYID

There's also a gpg-sign-keys.sh script available from dragon roe ( https://dragon.roe.ch/bitsnpieces/scripts/gpg/gpg-sign-keys.sh-1.30 ), but it's best to understand what needs to be done before using somebody else's black box.

KeySigning (last edited 2009-09-20 23:08:55 by localhost)