Hmm, with a little more investigation ...
I installed a new certificate generated the exact same way into
production and it works fine.
Then I found an opensll message in 443 error log :
[Fri Jul 30 06:00:12 1999] [error] mod_ssl: SSL handshake failed (client
142.53.67.22, server dserver.ic.gc.ca:443) (OpenSSL library error follows)
[Fri Jul 30 06:00:12 1999] [error] OpenSSL: error:14094412:SSL
routines:SSL3_READ_BYTES:sslv3 alert bad certificate [Hint: Subject CN in
certificate not server name!?]
But this only happens when connecting with Netscape 3.X. At first the
message would seem to indicate that there is a problem with the cert, but
subsequent connections with other browsers prove otherwise?
Any ideas?
Jeff
On Thu, 29 Jul 1999, Jeffrey Burgoyne wrote:
>
> Openssl .93a
> modssl 2.3.6
> apache 1.3.6
> Dec Unix 4.01
>
> B
> Hmm, ran into a dousy.
>
> We just upgraded our verisign cert on our development server, and suddenly
> Netscape 3 browsers get a database security error when trying to connect.
> Everything else seems fine. Any ideas?
>
>
>
> Jeff
>
>
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
>
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
