1996-05-16 - Re: distributed keys

Header Data

From: Simon Spero <ses@tipper.oit.unc.edu>
To: Matt Smith <msmith@rebound.slc.unisys.com>
Message Hash: 34ae30323e67a2547f47c8f304b5d495611b88ee38509013fbae78c70b21ae07
Message ID: <Pine.SOL.3.91.960515103442.4292C-100000@chivalry>
Reply To: <199605151447.OAA17650@rebound.slc.unisys.com>
UTC Datetime: 1996-05-16 05:28:53 UTC
Raw Date: Thu, 16 May 1996 13:28:53 +0800

Raw message

From: Simon Spero <ses@tipper.oit.unc.edu>
Date: Thu, 16 May 1996 13:28:53 +0800
To: Matt Smith <msmith@rebound.slc.unisys.com>
Subject: Re: distributed keys
In-Reply-To: <199605151447.OAA17650@rebound.slc.unisys.com>
Message-ID: <Pine.SOL.3.91.960515103442.4292C-100000@chivalry>
MIME-Version: 1.0
Content-Type: text/plain


On Wed, 15 May 1996, Matt Smith wrote:

> 
> -  Having a certifying node which every other node has the public key to and
>    who has everyone else's public key.  Requests are made of this server.  
>    The trick is making this server secure and forcing the user to devote
>    resources to this endeavour.

This is the usual approach; if you use certificates, the  private 
key for the certification agency doesn't have to be (and shouldn't) be 
accessible online; thus, even if the machine serving the certificates is 
compromised, Mallet won't be able to issue false certificates. 


---
Cause maybe  (maybe)		      | In my mind I'm going to Carolina
you're gonna be the one that saves me | - back in Chapel Hill May 16th.
And after all			      | Email address remains unchanged
You're my firewall -    	      | ........First in Usenet.........





Thread