1995-09-23 - Re: The Next Hack

Header Data

From: jsw@neon.netscape.com (Jeff Weinstein)
To: cypherpunks@toad.com
Message Hash: 2d2e64b26ec5109536501511bc40fd7a60648fc1374ff321eac9e080e3519bd1
Message ID: <441s9c$for@tera.mcom.com>
Reply To: <4407p5$on4@tera.mcom.com>
UTC Datetime: 1995-09-23 20:57:18 UTC
Raw Date: Sat, 23 Sep 95 13:57:18 PDT

Raw message

From: jsw@neon.netscape.com (Jeff Weinstein)
Date: Sat, 23 Sep 95 13:57:18 PDT
To: cypherpunks@toad.com
Subject: Re: The Next Hack
In-Reply-To: <4407p5$on4@tera.mcom.com>
Message-ID: <441s9c$for@tera.mcom.com>
MIME-Version: 1.0
Content-Type: text/plain


In article <199509231919.MAA01818@infinity.c2.org>, sameer@c2.org (sameer) writes:
> > 
> >   What exactly is the point of this?  We have:
> 
> 	Is Netscape going to cover the cost of getting the new keys
> that the servers generate signed and certified by Versign? Is netscape
> going to tell its customers that they need to regenerate their
> keys and get new certificates?

  I'm not sure what exactly you mean by "cover the cost".  Our server
customers WILL NOT have to pay verisign for new certificates.  We will
tell all of our customers to generate new keys and get new certificates
ASAP.  We are putting the version number in new certificate requests
so that verisign can reject requests from people who don't have the
new version of the key generator.

  Server operators will also be able to set up their servers to detect
unpatched clients and redirect them to a page that will allow them
to download the patch.

	--Jeff

-- 
Jeff Weinstein - Electronic Munitions Specialist
Netscape Communication Corporation
jsw@netscape.com - http://home.netscape.com/people/jsw
Any opinions expressed above are mine.





Thread