This is a discussion on Re: SSLVerifyClient - modssl ; --Apple-Mail-2-11933830 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Indeed, the trouble was with Safari and Keychain. Apparently, having more than one certificate confuses Safari. I am not sure what to do now, except get a different browser. Any advice would ...
-khtml-line-break: after-white-space; ">
--Apple-Mail-2-11933830
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
delsp=yes;
format=flowed
Indeed, the trouble was with Safari and Keychain. Apparently, having
more than one certificate confuses Safari. I am not sure what to do
now, except get a different browser. Any advice would be appreciated.
On Jun 28, 2005, at 11:01 AM, lingwitt@bellsouth.net wrote:
> This can't be the problem, as I specify the CA using
> SSLCACertificatePath using the proper HASH names. I've also tried
> SSLCACertificateFile.
>
> using s_client with SSLVerifyClient optional, it shows that the
> server is correctly identifying which CAs are allowed.
>
> I think the problem is with Safari and Keychain. I shall look
> further into the matter.
>
> On Jun 28, 2005, at 10:27 AM, Paul Puschmann wrote:
>
>> I think that Eckard Wille might be right. So have some experiments
>> with
>> your ca-files and certificates.
>
--Apple-Mail-2-11933830
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=US-ASCII