"Ralf S. Engelschall" wrote:
> In 90% of all cases where one receives this error this was caused by a cached
> old certificate/key information in the browser. And one can get rid of the
> error by just removing all cached cert/keys in the browsers security dialogs.
> Typical error is that the browser remembers a certificate, one recreates one
> (usually especially the Snake Oil cert) and then one retries it. Then although
> the cert's DN is still the same, the ingredients are not. Then this causes
> exactly the above error. So check your browsers security dialog for
> cached/remembered certs of your server.
I had seen this in a previous message on the list and had removed any
reference to the server I was working on. I didn't think that it could
have been one from a totally different server. Someone else set up
another machine here similarly and it was the certificate for that
_other_ machine that was causing this one to vomit. So of course
removing that certificate and accessing my server then worked fine, and
accessing the other would now fail. I should have tried that earlier,
my bad. Thanks for the help.
Robert
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
