More crazy policies from Netscape/Verisign

More crazy policies from Netscape/Verisign

Post by Jon Zee » Fri, 24 Nov 1995 04:00:00



The latest news from Netscape (I guess they finally figured out how to send
us email) is:

Quote:> The new feature that will ship in all future versions of Netscape
> Navigator 2.0 verifies not only the digital signature of the
> certificate but also compares the host name in the signed
> certificate to the host name in the URL being accessed.  If these
> strings do not match, the Netscape Navigator displays a dialog
> ...
> you have three options:
> ...
> 3.  Apply for a new digital ID from VeriSign at the cost of $95

One needs to consider this along with Versign's response when we tried to
use *.branch.com.  They said no and only gave us www*.branch.com.  
What this does is*things up for people doing virtual host
activities.  Doing a reverse lookup might make sense, but according to
Netscape's comments this isn't what they are doing and this will break
things like CNAMEs (where www.foo.com is a CNAME for www.bar.com).  
The last things we need are more messages to scare users and more
crazy interactions between Netscape and Verisign.  Caused us 4 days of
downtime and 8 hours of work last time...  At best, it looks like they want
$95 and more of our time this time.  

I can't recommend that anyone buy Netscape's server.

Quote:> This change will be
> implemented in the third beta version of the Netscape Navigator
> 2.0 which is scheduled for release later today (22 November 1995).

Thanks for plenty of notice...

--
   Corporate WWW Development and Hosting & the Branch Mall

(313) 741-4442  http://www.veryComputer.com/;            gopher branch.com

 
 
 

1. Non-Verisign certificates: problem with older Netscape/IE?

Our server, located outside the US, runs Apache. This means we can't get
a Verisign certificate, and will have to rely on another CA. I read a
cryptic reference to the fact that pre-3 versions of Netscape (and IE?)
only recognized Verisign. Would someone be kind enough to tell me what
will happen is a user with one of these older browsers tries to connect
to our site? Will they just see a warning-type dialog and then connect
successfully, or will they be entirely unable to get a secure
connection? Thanks.

2. word perfect for linux

3. Netscape Server & Verisign problem: Error SEC_GetKeyPair

4. USR 128K ISDN Sportster RH7(pulling my hair out)

5. netscape got crazy!!

6. en? versus et?

7. Netscape text goes crazy

8. HELP mksysb or savevg on AIX4.2.1/F50 gives a 888

9. Netscape is crazy!

10. Netscape httpd respawning like crazy?!

11. netscape = going crazy! help!

12. Netscape 2.0 release crashes like crazy

13. MS says Install Linux instead! Crazy, Crazy, Crazy World!