cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

1996-03-01 - Re: A brief comparison of email encryption protocols

Header Data

From: Derek Atkins <warlord@MIT.EDU>
To: cme@cybercash.com (Carl Ellison)
Message Hash: f91d744f50de54b345b5b05bab7c18db1b2cccd8d8f2d558335c8a50632ca933
Message ID: <199602292139.QAA18366@toxicwaste.media.mit.edu>
Reply To: <v02140b24ad5bc8a12abb@[204.254.34.231]>
UTC Datetime: 1996-03-01 01:41:48 UTC
Raw Date: Fri, 1 Mar 1996 09:41:48 +0800

Raw message

From: Derek Atkins <warlord@MIT.EDU>
Date: Fri, 1 Mar 1996 09:41:48 +0800
To: cme@cybercash.com (Carl Ellison)
Subject: Re: A brief comparison of email encryption protocols
In-Reply-To: <v02140b24ad5bc8a12abb@[204.254.34.231]>
Message-ID: <199602292139.QAA18366@toxicwaste.media.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain


> is a URL just too big?  My sigs are already several lines long.  E.g.,
> 
> Key: ftp://ftp.clark.net/pub/cme/cme.asc

IMHO, yes.  Consider for a minute: there are currently about 20000 PGP
keys on the public keyservers.  There are about 30000 signatures on
those keys.  The keyrings are already 8MB or more.

Now, consider adding a URL to every signature.  Lets even use your
URL, which is 35 characters long (and lets not even count the NULL or
length byte).  Adding this URL to 30000 signatures would add 1050000
bytes, or just over 1MB.  This is an increase in 12% of the keyrings!

On the other hand, using my method and your "URL" (clark.net) would
add only 10 bytes per sig, or 300k.  This is only a 4% increase.

-derek

Thread