1996-03-06 - Re: PGP 3.0/4.0

Header Data

From: David Lesher <wb8foz@nrk.com>
To: nelson@santafe.edu (Nelson Minar)
Message Hash: 10a65cd0675ebd3335af3089a171d7faad33cd91dbcd9e690acdcba135b321d6
Message ID: <199603061313.IAA07336@nrk.com>
Reply To: <199603060755.AAA00215@nelson.santafe.edu>
UTC Datetime: 1996-03-06 13:41:41 UTC
Raw Date: Wed, 6 Mar 1996 21:41:41 +0800

Raw message

From: David Lesher <wb8foz@nrk.com>
Date: Wed, 6 Mar 1996 21:41:41 +0800
To: nelson@santafe.edu (Nelson Minar)
Subject: Re: PGP 3.0/4.0
In-Reply-To: <199603060755.AAA00215@nelson.santafe.edu>
Message-ID: <199603061313.IAA07336@nrk.com>
MIME-Version: 1.0
Content-Type: text/plain


> 
> >the last time I put together a 6,000 key ring on a 386 it took three
> >days & several Mb.
> 
> The MIT PGP keyserver now has new non-PGP based code to manage it's
> keyring of 20,000+ keys. Not sure if you can get the code, or how easy
> it'd be to adapt to a deployed usage, but presumably it's much more
> efficient.

How about code that goes out & fetches keys upon demand, al-la DNS?

[1st pass thinking is there are too many holes in such a method, even
if MIT's server could handle the real-time load...]



-- 
A host is a host from coast to coast.................wb8foz@nrk.com
& no one will talk to a host that's close........[v].(301) 56-LINUX
Unless the host (that isn't close).........................pob 1433
is busy, hung or dead....................................20915-1433





Thread