I've seen a ton of people ask this question, but I have not once seen a definitive
answer
nor really any suggestions on the behavior.
Starting s_server with:
./ssleay s_server -cert server.pem -CApath ./demoCA -CAfile cacert.pem -verify 1 -www
SSL_accept:before SSL initalisation
SSL_accept:SSLv3 read client hello A
SSL_accept:SSLv3 write server hello A
SSL_accept:SSLv3 write certificate A
SSL_accept:SSLv3 write certificate request A
SSL_accept:SSLv3 write server done A
SSL_accept:SSLv3 flush data
SSL_accept:failed in SSLv3 read client certificate A
6875:error:140780E1:SSL routines:SSL23_READ:ssl handshake failure:s23_lib.c:190:
And then trying to connect with IE produces the usual empty available client
certificate
box for me.
I really would like to help fix this problem, but it seems rather pointless since you
couldn't legally use my changes. :) Perhaps someday, my changes will make it into
the codebase, only that they won't be under my name or with any mention of me, since
it makes life easier for everyone that way.
BUT PLEASE -- someone help tackle this client certificate issue, it is very
frustrating.
Like maybe a FAQ or a small client app that can successfully request a client
certificate
and get one back from Netscape and MSIE.
--Chris
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
