This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] PGP Key signing Party at RIPE 63
- Previous message (by thread): [dns-wg] Update to DNSSEC Policy and Practice Statement (DPS)
- Next message (by thread): [dns-wg] Agenda WG meetings
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wolfgang Nagele
wnagele at ripe.net
Wed Oct 26 10:55:43 CEST 2011
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicates] Dear colleagues, It has become a sort of tradition to have a PGP key signing party (http://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html) during RIPE meetings. If you would like to take part this time during RIPE 63 in Vienna (http://ripe63.ripe.net), join us on Wednesday, 2 November 2011 at 15:30 (during the coffee break) at the registration desk. The process for the signing will be: 1. Add your public key to the keyring (http://biglumber.com/x/web?keyring=4320). In order for me to be able to print the list, the deadline for this is Wednesday, 2 November 2011 at 12:00. 2. You will be provided with a printout of the keyring. It is important that you verify your own fingerprint on it with a trusted copy of your key fingerprint. 3. After we are all gathered, we will take it in turns to read our own key fingerprint so everyone else can verify it on the printout provided. It is best to check off the fingerprints you have verified on the list. 4. Next we will verify the identity of the key owner by using a legal document (passport, driver's license, etc.). For each identity you have verified you can add another checkmark on the printout. 5. Now the official part of the party is finished and once you get back home you can download the keyring and sign each key that you validated. It is easy to identify those by having two checkmarks on the printout. You should then provide the owner of that key with your signed version and possibly upload it to a key-server. If you have any questions or problems, please feel free to contact me. You may also spread the word through other information channels. Regards, Wolfgang Nagele, RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAk6nyw8ACgkQjO7G63Byy8fhGgCdHzO5k9srWXmEXkFcU0StlRZ/ 4akAoJd9TLQej1mF+lLrPnFjXc5qNijJ =e2DN -----END PGP SIGNATURE-----
- Previous message (by thread): [dns-wg] Update to DNSSEC Policy and Practice Statement (DPS)
- Next message (by thread): [dns-wg] Agenda WG meetings
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]