1995-10-01 - Re: NetScape’s dependence upon RSA down for the count!

Header Data

From: Simon Spero <ses@tipper.oit.unc.edu>
To: Don Stephenson <Don.Stephenson@Eng.Sun.COM>
Message Hash: 85c22d95446ba8d1b7fc2a266d386622284e51bfd58b97914eb11cae34c85c6a
Message ID: <Pine.SOL.3.91.951001101443.5437A-100000@chivalry>
Reply To: <9510010614.AA08538@icenine.Eng.Sun.COM>
UTC Datetime: 1995-10-01 17:19:44 UTC
Raw Date: Sun, 1 Oct 95 10:19:44 PDT

Raw message

From: Simon Spero <ses@tipper.oit.unc.edu>
Date: Sun, 1 Oct 95 10:19:44 PDT
To: Don Stephenson <Don.Stephenson@Eng.Sun.COM>
Subject: Re: NetScape's dependence upon RSA down for the count!
In-Reply-To: <9510010614.AA08538@icenine.Eng.Sun.COM>
Message-ID: <Pine.SOL.3.91.951001101443.5437A-100000@chivalry>
MIME-Version: 1.0
Content-Type: text/plain


On Sat, 30 Sep 1995, Don Stephenson wrote:

> I don't think binding hostnames to certificates helps much because 
> both hostnames and IP addresses can be spoofed and DNS servers can be 
> subverted.  The important thing is the binding to the "service" name or 

In this particular case, hostnames do help, because they are information 
imbedded in the url used to access the server. By verifying the hostname 
in the certificate with the hostname in the url, you can state with a 
high degree of confidence that the object retrieved is precisely the 
desired object covered by this url. 

> Well of course, if the secret key of the server (or worse yet, certificate 
> authority) is compromised, all bets are off.  That's true of just about any 
> protocol you can dream up.

I'm not referring to the secret key of _the_ server; I'm referring to the 
secret key of _ANY_ server. In the limiting case, such a key can be 
obtained by buying one from the CA. 

Simon






Thread