PGP Key Signing
Once again, we will be holding a PGP Key signing party at the 68th IETF meeting in Prague. We have been scheduled to meet at 1620 on the evening of Wednesday, March 21 in the Roma/Vienna/Madrid room. Note that we have a very tight time-slot between the last afternoon and the plenary, so please be on time. The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, March 21. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail; send it to me as plain text. The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 1500 on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf68/ietf68.pgp http://grand.central.org/dl/ietf-pgp/ietf68/ietf68.pgp ftp://grand.central.org/pub/ietf-pgp/ietf68/ietf68.pgp o At 1620, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
PGP Key Signing
Once again, we will be holding a PGP Key signing party at the 73rd IETF meeting in Minneapolis. We have been scheduled to meet at 1820 on the evening of Tuesday, Nov 18, in the Duluth room. *** NOTE DAY CHANGE *** Our scheduled time slot on Tuesday evening is a departure from previous IETF meetings, when we have held key signing sessions on Wednesdays. Changes in the IETF meeting agenda to hold both plenary sessions on Wednesday evening have reduced the length of the pre-plenary break and make it impractical to hold a key-signing session on Wednesday. Our scheduled slot is 40 minutes on Tuesday evening, between the end of the last meeting session on Tuesday and the start of the social event. We should be done in plenty of time for participants to attend the social event or find dinner elsewhere. The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Tuesday, Nov 18, 2008. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail; send it to me as plain text. The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 1700 on Tuesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf73/ietf73.pgp http://grand.central.org/dl/ietf-pgp/ietf73/ietf73.pgp ftp://grand.central.org/pub/ietf-pgp/ietf73/ietf73.pgp o At 1820, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some people opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgment: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
PGP Key Signing Session
Once again, we will be holding a PGP Key signing party at the 66th IETF meeting in Montreal. We have been scheduled to meet at 1610 in the afternoon on Wednesday, July 12 in room 513B. ** * PLEASE NOTE THE TIME CHANGE * ** * With the new meeting schedule, our traditional 10pm slot after the* * Wednesday evening plenary no longer makes sense -- everyone wants to * * get to dinner as soon as the plenary is over, and no one wants to come* * back afterward. Therefore, we have moved the key-signing session to * * the extended break just _before_ the Wednesday-evening plenary. * ** * This change does tighten the time schedule somewhat. We have only* * 50 minutes between the last afternoon session and the plenary, so please * * be on time. We will start promptly at 1620, which should provide ample * * time to get between sessions. In addition, I will be unable to include * * key not received before the noon deadline, due to the time required to* * produce and publish keyrings and printouts. * ** The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, July 12. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail; send it to me as plain text. The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 1500 on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf66/ietf66.pgp http://grand.central.org/dl/ietf-pgp/ietf66/ietf66.pgp ftp://grand.central.org/pub/ietf-pgp/ietf66/ietf66.pgp o At 1620, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
PGP Key Signing Party
Once again, we will be holding a PGP Key signing party at the IETF meeting in Washington. We have been scheduled to meet at 10:30pm on the evening of Wednesday, November 10, 2004 in the 'Hemisphere' room (Note that if the plenary runs over, we will start approximately five minutes *after* the plenary session ends). The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, between 50 and 100 should be plenty. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, November 10, 2004. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail. Send it to me as plain text, and do NOT base-64 encode things. (My process is not quite as automated as Ted's, so I'll probably be able to notice and fix any problems, but it's better not to take chances). The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 9pm on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf60.pgp http://grand.central.org/dl/ietf-pgp/ietf60.pgp ftp://grand.central.org/pub/ietf-pgp/ietf60.pgp o At 10:30pm, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce
69th IETF - PGP Key Signing
Once again, we will be holding a PGP Key signing party at the 69th IETF meeting in Chicago. We have been scheduled to meet at 1620 on the evening of Wednesday, July 25 in Salon 2. Note that we have a very tight time-slot between the last afternoon and the plenary, so please be on time. The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, July 25. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail; send it to me as plain text. The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 1500 on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf69/ietf69.pgp http://grand.central.org/dl/ietf-pgp/ietf69/ietf69.pgp ftp://grand.central.org/pub/ietf-pgp/ietf69/ietf69.pgp o At 1620, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
70th IETF - PGP Key Signing
Once again, we will be holding a PGP Key signing party at the 70th IETF meeting in Vancouver. We have been scheduled to meet at 1620 on the evening of Wednesday, December 5 in the Oak room. Note that we have a very tight time-slot between the last afternoon session and the plenary, so please be on time. The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, December 5. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail; send it to me as plain text. The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 1500 on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf70/ietf70.pgp http://grand.central.org/dl/ietf-pgp/ietf70/ietf70.pgp ftp://grand.central.org/pub/ietf-pgp/ietf70/ietf70.pgp o At 1620, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
71st IETF - PGP Key Signing
Once again, we will be holding a PGP Key signing party at the 71st IETF meeting in Philadelphia. We have been scheduled to meet at 1620 in the afternoon of Wednesday, March 12 in Salon I. Note that we have a very tight time-slot between the last afternoon session and the plenary, so please be on time. The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, March 12. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail; send it to me as plain text. The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 1500 on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf71/ietf71.pgp http://grand.central.org/dl/ietf-pgp/ietf71/ietf71.pgp ftp://grand.central.org/pub/ietf-pgp/ietf71/ietf71.pgp o At 1620, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
72nd IETF - PGP Key Signing
Once again, we will be holding a PGP Key signing party at the 72nd IETF meeting in Dublin. We have been scheduled to meet at 16:10 on the evening of Wednesday, Jul 30 in the Conservatory. Note that we have a very tight time-slot between the last afternoon session and the plenary, so please be on time. In addition to the normal key-signing (details below), it has been suggested that this event would be a good venue for people to gain points in the certification systems operated by CAcert and Thawte. So, if you are a Thawte Notary or CAcert Assurer, please consider joining us. Those wishing to participate should note that both systems require that you be registered with the system and present one or more identity documents, of which the Assurer/Notary must retain copies. We will not have a photocopier available during the session, so participants should make several copies of their documents in advance. The hotel business center is located on the 2nd floor of the main hotel; ask at the hotel reception desk for details. For more information on CAcert and Thawte, see http://www.cacert.org/ and http://www.thawte.com/secure-email/web-of-trust-wot/index.html The procedure we will use for the PGP key signing is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, Jul 30. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail; send it to me as plain text. The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 14:00 on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf72/ietf72.pgp http://grand.central.org/dl/ietf-pgp/ietf72/ietf72.pgp ftp://grand.central.org/pub/ietf-pgp/ietf72/ietf72.pgp o At 16:10, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
74th IETF - PGP Key Signing
Once again, we will be holding a PGP Key signing party at the 74th IETF meeting in San Francisco. We have been scheduled to meet at 1820 on the evening of Tuesday, March 24 in Franciscan A. *** NOTE DAY CHANGE *** Our scheduled time slot on Tuesday evening is a departure from previous IETF meetings, when we have held key signing sessions on Wednesdays. Changes in the IETF meeting agenda have reduced the length of the break before the Wednesday plenary and make it impractical to hold a key-signing session during that time. Our scheduled slot is 40 minutes on Tuesday evening, between the end of the last meeting session and the start of the social event. We should be done in plenty of time for participants to attend the social event or find dinner elsewhere. The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint my_usern...@hostname") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to by noon on Tuesday, March 24. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail; send it to me as plain text. The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 1500 on Tuesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf74/ietf74.pgp http://grand.central.org/dl/ietf-pgp/ietf74/ietf74.pgp ftp://grand.central.org/pub/ietf-pgp/ietf74/ietf74.pgp o At 1820, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some people opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgment: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
80th IETF - PGP Key Signing
Once again, we will be holding a PGP Key signing party at the 80th IETF meeting in Prague. We have been scheduled to meet at 1815 on the evening of Tuesday, March 29 in the Barcelona/Berlin rooms. Note that we have a very tight time-slot between the last afternoon session and the IETF social event, so please be on time. The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint my_username@hostname") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to by noon on Tuesday, March 29. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail; send it to me as plain text. The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 1600 on Tuesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf80/ietf80.pgp http://grand.central.org/dl/ietf-pgp/ietf80/ietf80.pgp ftp://grand.central.org/pub/ietf-pgp/ietf80/ietf80.pgp o At 1815, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some people opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgment: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
PGP Key Signing at IETF63
Once again, we will be holding a PGP Key signing party at the IETF-63 meeting in Paris. We have been scheduled to meet at 1930 on the evening of Wednesday, August 3 in room 322M. As usual, if the plenary runs over, we will start approximately five minutes *after* the plenary session ends. Please note the unusual time, due to the change in the meeting schedule for this week. Note that even though the printed agendas say 2200, we will meet at approximately 1930, as indicated here and in the online agenda. In the unlikely event the agenda should conclude early, we will begin the key-signing approximately five minutes after the plenary, in order to allow people to take advantage of the extra time for dinner or evening social events. The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, August 3(*). Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail. Send it to me as plain text, and do NOT base-64 encode things. (My process is not quite as automated as Ted's, so I'll probably be able to notice and fix any problems, but it's better not to take chances). The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 1700 on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf63/ietf63.pgp http://grand.central.org/dl/ietf-pgp/ietf63/ietf63.pgp ftp://grand.central.org/pub/ietf-pgp/ietf63/ietf63.pgp o At 1930, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. (*) Normally I'm pretty lax about the "noon" deadline, accepting things as late as during the plenary. However, in order to keep things running on time with the unusual schedule of this week's meeting, I intend to prepare the photocopied fingerprint lists before the plenary session. So, I'll be applying the deadline more strictly than usual. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
64th IETF - PGP Key Signing
Once again, we will be holding a PGP Key signing party at the IETF-64 meeting in Vancouver. We have been scheduled to meet at 10:00 PM on the evening of Wednesday, November 9 in the Thompson room (Note that if the plenary runs over, we will start approximately two hours *after* the plenary session ends, to allow time to eat before the session). The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, November 9. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail. Send it to me as plain text, and do NOT base-64 encode things. (My process is not quite as automated as Ted's, so I'll probably be able to notice and fix any problems, but it's better not to take chances). The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By noon on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf64/ietf64.pgp http://grand.central.org/dl/ietf-pgp/ietf64/ietf64.pgp ftp://grand.central.org/pub/ietf-pgp/ietf64/ietf64.pgp o At 10:00 PM, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
65th IETF - PGP Key Signing
Once again, we will be holding a PGP Key signing party at the IETF-65 meeting in Dallas. We have been scheduled to meet at 10:00 PM on the evening of Wednesday, March 22 in the Miro room. The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, March 22. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail. Send it to me as plain text, and do NOT base-64 encode things. (My process is not quite as automated as Ted's, so I'll probably be able to notice and fix any problems, but it's better not to take chances). The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 7:00 PM on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf65/ietf65.pgp http://grand.central.org/dl/ietf-pgp/ietf65/ietf65.pgp ftp://grand.central.org/pub/ietf-pgp/ietf65/ietf65.pgp o At 10:00 PM, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
PGP key signing party at IETF 62
Once again, we will be holding a PGP Key signing party at the IETF meeting in Washington. We have been scheduled to meet at 10:30pm on the evening of Wednesday, March 9, 2005 in the 'Carver' room (Note that if the plenary runs over, we will start approximately five minutes *after* the plenary session ends). The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, around 50 should be more than enough. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, March 9, 2005. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail. Send it to me as plain text, and do NOT base-64 encode things. (My process is not quite as automated as Ted's, so I'll probably be able to notice and fix any problems, but it's better not to take chances). The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 9pm on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf62.pgp http://grand.central.org/dl/ietf-pgp/ietf62.pgp ftp://grand.central.org/pub/ietf-pgp/ietf62.pgp o At 10:30pm, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
60th IETF PGP Key Signing Party for San Diego
Once again, we will be holding a PGP Key signing party at the IETF meeting in San Diego. We have been scheduled to meet at 10:30pm on the evening of Wednesday, August 3, 2004 in the 'Marina 5' room. (Note that if the IETF Business Meeting Plenary runs over, we will start approximately 5 minutes *after* the Wednesday evening Plenary finishes.) The procedure we will use is the following: o People who wish to participate may do so in one of two ways. You may bring slips of paper with your name, e-mail address, key-id, and key fingerprint. (One way of generating this if using gpg is "gpg --list-keys --fingerprint [EMAIL PROTECTED]") You should bring enough for everyone who may attend; given recent attendance patterns, between 20 and 50 should be plenty. (You can generally fit 10-12 strips containing your key fingerprint on a single sheet of paper, and then cut out strips to hand out.) o Alternatively, you may email an ASCII extract of their PGP public key to <[EMAIL PROTECTED]> by noon on Wednesday, August 3, 2004. Please include a subject line of "IETF PGP KEY", and please DO NOT MIME-ENCRYPT your e-mail. Send it to me as plain text, and do NOT base-64 encode things. (My process is not quite as automated as Ted's, so I'll probably be able to notice and fix any problems, but it's better not to take chances). The method of generating the ASCII extract under Unix is: pgp -kxa my_email_address mykey.asc (pgp 2.6.2) pgpk -xa my_email_address > mykey.asc (pgp 5.x) gpg --export -a my_email_address > mykey.asc (gpg) If you're using Windows or Macintosh, hopefully it will be Intuitively Obvious (tm) using the GUI interface how to generate an ASCII armored key that begins "-BEGIN PGP PUBLIC KEY BLOCK-". o By 9pm on Wednesday, you will be able to fetch complete key ring from any of the following locations with all of the keys that were submitted: /afs/grand.central.org/project/ietf-pgp/ietf60.pgp http://grand.central.org/dl/ietf-pgp/ietf60.pgp ftp://grand.central.org/pub/ietf-pgp/ietf60.pgp o At 10:30pm, come prepared with the PGP Key fingerprint of your PGP public key; we will have handouts with all of the key fingerprints of the keys that people have mailed in. o In turn, readers at the front of the room will recite people's keys; as your key fingerprint is read, stand up, and at the end of reading of your PGP key fingerprint, acknowledge that the fingerprint as read was correct. o Later that evening, or perhaps when you get home, you can sign the keys corresponding to the fingerprints which you were able to verify on the handout; note that it is advisable that you only sign keys of people when you have personal knowledge that the person who stood up during the reading of his/her fingerprint really is the person which he/she claimed to be. o Send the signed keys to the owners, and, optionally, to the PGP key servers. Some poeple opt to NOT send the signed keys to the keyservers, but rather choose to send them only to the e-mail address on the key's userid, encrypted for that particular key. This tends to ensures the validity of the e-mail address. Note that you don't have to have a laptop with you; if you don't have any locally trusted computing resources during the key signing party, you can make notes on the handout, and on the strips of papers, and then take these and sign the keys later. Acknowledgement: The bulk of the text of this message was taken from the messages usually sent by Ted Ts'o to announce IETF key signing parties. -- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce
