Re: SSLVerifyClient

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

lingwitt@bellsouth.net wrote:
> 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
> <mailto: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.
>>
Please answer BELOW THE QUOTE! Thank you.

Perhaps you could file a bug against Safari (or have a look in their
bug-database (if existent)).

Paul
- --
Linux-User #271918 with the Linux Counter, http://counter.li.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)

iEYEARECAAYFAkLDpLUACgkQqErKtBWD7VQNWQCgu8DI++FBv5 TCkrCDUUE5hrFC
nYAAnAtzNNr3g+ljVeP8jEBpvzgZ4Q4y
=bgbS
-----END PGP SIGNATURE-----

__________________________________________________ ____________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org