R Ayres wrote:
I have 2 certificates: a self signed server certificate and
a purchased domain specific certificate. When I connect to the
domain with https://mydomain.com it works fine, but if I try to
connect to another port (https://mydomain.com:2020),
the self signed certificate is the one that is recognized,
and I get a warning because the certificate is self generated.
Well, these symptoms could be explained quite easily if you were
running two DIFFERENT servers, one on port 443 with the commercial
certificate and another on port 2020 with the old self-signed one.
You could use the openssl s_client tool to connect to each of the
ports in turn, using the -showcerts option to really SEE which
certificates each server is presenting.
Note: you could be running either two copies of the Apache server
or one copy with Virtual Hosts enabled. If you're using the
Apache stuff, the answers will be in the httpd.conf file in the
conf directory.
But you haven't really told us which server(s) you are using.
If this is on a Wintel box somebody else will have to help you...
--
Charles B (Ben) Cranston
mailto: [EMAIL PROTECTED]
http://www.wam.umd.edu/~zben
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
