Hi,
> so in fact I tried with NS v2.0, 3.0 , MSIE 4.0 5.0, and it works fine with a
> slf signed certificate . The only software which doesn't run with it is NS 4.06
> and latter versions.
> So what is the problem .... is the below solution is the right way ?
I had a similar problem to this last week.
It turns out the Netscape v4.06 or higher, requires that the CN (common
name) of the certificate matches the DNS name of the server. I think this
_is_ part of the standard, it is just that the other browsers don't complain.
So if your URL is: https://secure.mydomain.com/
the CN should be: secure.mydomain.com
The basic openssl.cnf file prompts for this with "Your name" as the example,
and I at first was putting "webmaster" in that field.
Took a bit of tracking down but now all of the browsers we use here accept
the self-signed cert.
Fare Thee Well
Anthony Peacock
CHIME, UCL Medical School
E-Mail: [EMAIL PROTECTED]
WWW: http://www.chime.ucl.ac.uk/~rmhiajp/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
