From Fedora Project Wiki
(Rewrote the event description to declutter the words) |
|||
| Line 1: | Line 1: | ||
== What == | |||
What is this key signing thing all about? This is an event used to create trust paths for the OpenPGP [https://en.wikipedia.org/wiki/Web_of_Trust 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. | |||
=== Signing up === | |||
<!-- {{admon/warning|The signup deadline has passed|If you still want to participate, bring about 60 slips with your key's fingerprint printed or '''neatly''' written on it.}}--> | |||
== Signing up == | |||
<!-- {{admon/warning|The signup deadline has passed|If you still want to participate, bring about 60 slips with your key's fingerprint printed or '''neatly''' written on it.}} | |||
--> | |||
Please sign up below and make sure your key is available on the public keyserver network or make a note here with a URL to the public key. | |||
== Where == | |||
The key signing event will be held at [[FUDCon:Lawrence_2013|FUDCon Lawrence]] on the campus of Kansas University. | |||
== When == | |||
Saturday, 19 January 2013 | |||
[ | Please see the [[FUDCon:Lawrence_2013#Saturday.2C_January_19|Saturday schedule]] for exact time and location information as this is subject to change. | ||
== How == | |||
Participating in a key signing event is quite easy and signing the keys afterwards is even easier. | |||
== | |||
=== Why shouldn't | === Things to bring to the event: === | ||
* Yourself | |||
* At least one government issued photo ID | |||
* Your key's fingerprint (<code>gpg --fingerprint keyid</code>) 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. | 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. | * 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. | * Someone might drop it or knock it off the table. | ||
* Etc | * Etc | ||
== | === Key signing Procedure === | ||
# Generate a key | # [[Creating_GPG_Keys|Generate a key]] | ||
# All attendees send their public keys to a public keyserver | # 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. | ||
# All attendees posts their fingerprint to this wiki page (see below). The event coordinator will compile everyone's key information. | # All attendees posts their fingerprint to this wiki page (see below). The event coordinator will compile everyone's key information. | ||
# The host prints a list with everyone's fingerprint from the compiled keyrings and distributes copies of the printout at the meeting. | # The host prints a list with everyone's fingerprint from the compiled keyrings and distributes copies of the printout at the meeting. | ||
# 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. | # 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. | ||
# At the meeting the host will distribute the key forms and a hash of that form | # 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. | ||
# After everyone has read his key ID information, have all attendees form a line. | # After everyone has read his key ID information, have all attendees form a line. | ||
# The first person walks down the line having every person check his ID. | # The first person walks down the line having every person check his ID. | ||
| Line 64: | Line 50: | ||
# 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. | # 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. | ||
# 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. | # 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. | ||
# Send the signed keys back to the | # Send the signed keys back to the key-servers. | ||
# Use those keys as often as possible. | # Use those keys as often as possible. | ||
=== Acceptable Identification === | === 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 == | === Uploading your key to a keyserver === | ||
To upload your key, do <code>gpg --keyserver pool.sks-keyservers.net --send-keys 0xYOURKEYID</code> | To upload your key, do <code>gpg --keyserver pool.sks-keyservers.net --send-keys 0xYOURKEYID</code> | ||
== Key List == | == Key List == | ||
| Line 100: | Line 87: | ||
! Name !! FAS Username !! Key ID !! Fingerprint | ! Name !! FAS Username !! Key ID !! Fingerprint | ||
|} | |} | ||
== CAcert Assurance == | |||
There will also be a [[FUDCon:Lawrence_2013_CAcert_Assurance_Event|CAcert Assurance event]]. | |||
Back to [[FUDCon:Lawrence_2013]]. | Back to [[FUDCon:Lawrence_2013]]. | ||
Revision as of 00:54, 22 December 2012
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.
Signing up
Please sign up below and make sure your key is available on the public keyserver network or make a note here with a URL to the public key.
Where
The key signing event will be held at FUDCon Lawrence on the campus of Kansas University.
When
Saturday, 19 January 2013
Please see the Saturday schedule for exact time and location information as this is subject to change.
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
- Generate a key
- 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.
- All attendees posts their fingerprint to this wiki page (see below). The event coordinator will compile everyone's key information.
- The host prints a list with everyone's fingerprint from the compiled keyrings and distributes copies of the printout at the meeting.
- 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.
- 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.
- After everyone has read his key ID information, have all attendees form a line.
- The first person walks down the line having every person check his ID.
- The second person follows immediately behind the first person and so on.
- 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.
- 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.
- 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.
- 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.
- Send the signed keys back to the key-servers.
- 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 |
| 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 |
| Name | FAS Username | Key ID | Fingerprint |
CAcert Assurance
There will also be a CAcert Assurance event.
Back to FUDCon:Lawrence_2013.