> My Issue: > 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. > > My question is this: is this a configuration problem with SSL > or is this a certificate issue? I would really appreciate any > help that anyone might be able to give. I have done some > research online, but did not find a answer.
Assuming you've configured your web server to use your self signed cert on the port 2020 connection, I believe this is a normal response for a browser since the browser does not yet trust your self-signed cert. If you are expecting the other cert to be handling this then that's another issue. However, if you added your CA's cert to the trusted root certificates in your browser's cert store you would be telling your browser that you trust that CA and the browser would no longer pop up the warnings. Of course, all of your visitors would need to do that as well. I'm pretty new to this whole cert thing too, so I may be incorrectly stating something. If so, hopefully the experts in this list will correct me and we'll both learn :) Best, Dann ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
