1996-01-24 - Re: [local] Report on Portland Cpunks meeting

Header Data

From: Alan Olsen <alano@teleport.com>
To: weld@l0pht.com>
Message Hash: 8afa91c974403e0ea17e7e4c80e965dbe9de9b4a4e5b896b03cd6c8f60b07cc0
Message ID: <2.2.32.19960124002635.008c27e8@mail.teleport.com>
Reply To: N/A
UTC Datetime: 1996-01-24 18:28:25 UTC
Raw Date: Thu, 25 Jan 1996 02:28:25 +0800

Raw message

From: Alan Olsen <alano@teleport.com>
Date: Thu, 25 Jan 1996 02:28:25 +0800
To: weld@l0pht.com>
Subject: Re: [local] Report on Portland Cpunks meeting
Message-ID: <2.2.32.19960124002635.008c27e8@mail.teleport.com>
MIME-Version: 1.0
Content-Type: text/plain


At 04:40 PM 1/23/96 -0500, Perry E. Metzger wrote:
>
>Weld Pond writes:
>> This begs the question, "How would you conduct an efficient key signing 
>> given what you have learned?" I am in the process of organizing one and 
>> would like to get input as to the best way that this should take place.  
>
>The IETF key signing parties are the largest in existance -- about 100
>people exchange signatures.
>
>The way you handle it is this:

{key signing stuff deleted for space]

That was the basic format we used.  The only difference was that the keys
were collected before hand and distributed on disk.

The biggest problems were due to unfamiliarity was to what to bring and
procedure from an experience point of view.  (Lack of key fingerprints were
a problem.)

The key signing rules were published, but many people attending did not read
them.  (They were part of an update announcement.  Many people read the top
part, saw nothing had changed and skipped the rest of it...)

Now that we have done it once, it will be alot easier the next time.
Alan Olsen -- alano@teleport.com -- Contract Web Design & Instruction
        `finger -l alano@teleport.com` for PGP 2.6.2 key 
              http://www.teleport.com/~alano/ 
       "Is the operating system half NT or half full?"






Thread