Are you using a real certificate or a test certificate. If it is a test
certificate you have to install a Test Certificate Authority which you
may have already done on your windows machines but not on your Mac.
Could that be it.?
Theory is when you know something, but it doesn't work.
Practice is when something works, but you don't know why.
Programmers combine theory and practice:
Nothing works and they don't know why.
--Unknown
- Original Message -
From: Tim Howell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 28, 2004 10:17 AM
Subject: Re: mod_ssl and MacOS browsers...
On Thu, 28 Oct 2004 09:42:53 -0700, Tim Howell
[EMAIL PROTECTED] wrote:
I've just installed a VeriSign 128 bit certificate on a server
running
Apache 2.0.50 with mod_ssl. Connecting to the server over https
works
fine from all of the Windows clients I've tried (Win2K using both IE
6
and Firefox 1.0PR). However, whenever I try to connect from a MacOS
client (using MSIE 5.1, current Safari, or Firefox 1.0PR) I get a
warning that the certificate issuer is unknown.
Any ideas? This is for a system that is (hopefully) going into
production in a couple of days. =) I've searched the list archives
to no avail.
Thanks! =)
--TWH
I think I've solved my own problem. The solution might be useful for
the archives.
I had to download an intermediary CA certificate from the VeriSign
website and install that using the SSLCertificateChainFile option.
--TWH
__
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]
