Jump to: navigation, search

Difference between revisions of "OpenPGP Web of Trust/Juno Summit"

m (Juno Summit Key Signing: typo)
 
(72 intermediate revisions by 58 users not shown)
Line 1: Line 1:
 
= Juno Summit Key Signing =
 
= Juno Summit Key Signing =
In an effort to build a secure web of trust, some community members will perform an informal exchange of identification and confirm key fingerprints in the Developer Lounge at the OpenStack Juno Design Summit. Exact place and location is to be defined.
+
In an effort to build a secure web of trust, some community members will perform an informal exchange of identification and confirm key fingerprints at the OpenStack Juno Design Summit on Wednesday the 14th of May starting at 10:35 AM EDT (14:35 UTC) in room B301 of the Georgia World Congress Center (in between Infrastructure topic sessions).
  
If you plan to join us, please bring one or more forms of photo identification, preferably at least a [http://en.wikipedia.org/wiki/Passport passport], and make sure the real name on your key corresponds to the name on your passport. If you want additional tips, see the [[OpenPGP Web of Trust#Key Signing Process|parent article]].
+
'''The sign-up period is now closed and the list of participants' keys has been finalized.''' If you signed up to participate, please retrieve [http://static.openstack.org/juno-ksp.txt juno-ksp.txt] (it consists of details for 65 participants), confirm your key fingerprint and other details within it are accurate, and verify its checksums according to the md5sum and sha1sum utilities match the following:
 +
<pre>
 +
1ed74f9bee7eae90246d080bb1f8e842 (MD5)
 +
c2b3f6b7be5fa94c533e3a45ad4401f23356c84d (SHA-1)
 +
</pre>
  
If you want to bring cards or pieces of paper with your name and key fingerprint then feel free, but if you '''add your information to the table below before the 14th of April 10:00am UTC''', your key will be added to a text file containing all names and fingerprints, and for which we will check together the validity.
+
If your browser has a tendency to convert line endings to MS-DOS or Macintosh text formats transparently, this will change the checksums so you may instead want to retrieve the [http://static.openstack.org/juno-ksp.tar.gz tarred and gzip-compressed version] and unpack it locally.
  
Please enter your name in alphabetical order.
+
Print a copy of the file and the [http://static.openstack.org/checksum.txt checksums] to bring with you to the Summit (also don't forget a pencil or a pen, and one for your friend who will probably forget theirs!) along with one or more forms of photo identification, preferably at least a [http://en.wikipedia.org/wiki/Passport passport], and make sure the real name on your key corresponds to the name on your passport. If you want additional tips, see the [[OpenPGP Web of Trust#Key Signing Process|parent article]]. This activity takes place during the 10:30-11:00 break period so please arrive promptly. We will follow [http://keysigning.org/methods/sassaman-projected The 'Sassaman-Projected' Method] so that we can hopefully get through all participants in the limited time allotted.
  
{| class="wikitable"
+
A similar message has been [http://lists.openstack.org/pipermail/openstack-dev/2014-May/034693.html posted] on the openstack-dev@lists.openstack.org mailing list with the same attachments, signed by RSA key 0x48F9961143495829 (though the pipermail archive mangles the contents and makes it hard to match up the detached signature, so hopefully you're subscribed to that ML already).
|+ people participating in identification exchange
 
! Real Name !! IRC Nick !! Key Fingerprint !! Preferred E-mail Address
 
|-
 
 
 
| Thomas Goirand || zigo || A0B1 A9F3 5089 5613 0E7A  425C D416 AD15 AC6B 43FE || zigo@debian.org
 
|-
 
| Thierry Carrez || ttx || 22A7 9430 50DB 1E67 EC2B  641A 507A F890 25B1 0423 || thierry@openstack.org
 
|-
 
| Sergey Lukjanov || SergeyLukjanov || 71C5 CE23 FE25 A46B 95D2  4BCB 1626 1D61 85DB 0AEC || slukjanov@mirantis.com
 
|-
 
| Dina Belova || DinaBelova || 950D 48B2 3F58 A436 D4D2  A096 57D4 40F6 6E83 8E8B || dbelova@mirantis.com
 
|-
 
| Clint Byrum || SpamapS || F00C 9F2F 4F7E B714 AFAD  1A42 538C 0766 F4BC B38E || clint@fewbar.com
 
 
 
|}
 

Latest revision as of 22:10, 9 May 2014

Juno Summit Key Signing

In an effort to build a secure web of trust, some community members will perform an informal exchange of identification and confirm key fingerprints at the OpenStack Juno Design Summit on Wednesday the 14th of May starting at 10:35 AM EDT (14:35 UTC) in room B301 of the Georgia World Congress Center (in between Infrastructure topic sessions).

The sign-up period is now closed and the list of participants' keys has been finalized. If you signed up to participate, please retrieve juno-ksp.txt (it consists of details for 65 participants), confirm your key fingerprint and other details within it are accurate, and verify its checksums according to the md5sum and sha1sum utilities match the following:

1ed74f9bee7eae90246d080bb1f8e842 (MD5)
c2b3f6b7be5fa94c533e3a45ad4401f23356c84d (SHA-1)

If your browser has a tendency to convert line endings to MS-DOS or Macintosh text formats transparently, this will change the checksums so you may instead want to retrieve the tarred and gzip-compressed version and unpack it locally.

Print a copy of the file and the checksums to bring with you to the Summit (also don't forget a pencil or a pen, and one for your friend who will probably forget theirs!) along with one or more forms of photo identification, preferably at least a passport, and make sure the real name on your key corresponds to the name on your passport. If you want additional tips, see the parent article. This activity takes place during the 10:30-11:00 break period so please arrive promptly. We will follow The 'Sassaman-Projected' Method so that we can hopefully get through all participants in the limited time allotted.

A similar message has been posted on the openstack-dev@lists.openstack.org mailing list with the same attachments, signed by RSA key 0x48F9961143495829 (though the pipermail archive mangles the contents and makes it hard to match up the detached signature, so hopefully you're subscribed to that ML already).