On Tue, Sep 6, 2011 at 12:08 AM, Matthew Walster <[email protected]> wrote:
> Ben,
> The rough idea that'll be announced tomorrow is that everyone verifies the
> MD5/SHA1 hashes to make sure you have the right, untampered document.
> At 15:15, everyone meets and we go down the list from #1 to #8 saying
> whether the fingerprint is accurate or not, ticking the box if it is. If so,
> everyone has a peer at his/her ID and ticks that box if they so choose.
> A whole keysigning can be over in less than 5 minutes using this method, and
> thanks to the hashes, you don't have to have everyone reading their
> fingerprints out loud. It was introduced to me at FOSDEM a number of years
> ago and worked rather well.

Yeah, its the Sassaman-Efficient method
(http://www.keysigning.org/methods/sassaman-efficient). You should
probably spend a moment to honour its inventor, who killed himself a
couple of months ago.

However, that's not my issue: my issue is "proof of identity".

a) Who cares? PGP is for email and other online transactions, your
government (or whatever) issued ID is irrelevant.

b) Who is qualified to check such documents?

> Matthew Walster
>
>
> On 6 September 2011 00:00, Ben Laurie <[email protected]> wrote:
>>
>> Who will be verifying the proof of identity?
>>
>> On Mon, Sep 5, 2011 at 4:48 PM, Matthew Walster <[email protected]>
>> wrote:
>> > Just a quick note for those interested in the PGP keysigning.
>> > If you're planning on attending the keysigning, please print off the
>> > signing
>> > list [1] and bring it along to the meeting. This will make signing a lot
>> > easier and quicker on the day. If you haven't submitted a key, but wish
>> > to
>> > participate, please print out a few copies of your key fingerprint [2]
>> > and
>> > bring them along to the signing at the Afternoon Tea slot at 15:15
>> > tomorrow.
>> > Looking forward to seeing most of your there!
>> > Kind regards,
>> >
>> >
>> > Matthew Walster
>> > [1] http://www.uknof.org.uk/uknof20/PGP-signsheet.txt
>> > [2] gpg -K ${yourkeyid}
>> >
>> >
>> >
>
>


Reply via email to