Dr. Stephen Henson wrote: > On Tue, Nov 15, 2011, Tobias Nissen wrote: >> I'm indirectly using OpenSSL through Net::SSLeay¹, which I use >> through AnyEvent::TLS². AnyEvent::TLS provides the means to define >> a custom verification mechanism by setting verify_cb³. Here's an >> example (keys included): >> >> http://paste.scsys.co.uk/159837 >> >> If the custom verification callback decides a peer is bad, it shall >> return 0 and return 1 otherwise. If 0 is returned, this warning is >> produced: >> >> ssl3_get_client_certificate: no certificate returned >> >> It's only a warning which does not seem to impair functionality; no >> warning is printed if 1 is returned. >> >> I've already asked on the AnyEvent mailing list???, but the author >> of AnyEvent::TLS couldn't really nail it down either. Can you help >> me? Why is this warning printed and what could be done to eliminate >> the problem? > > The warning isn't printed by OpenSSL it is an error code. So perhaps > the wrapper is printing the error?
I didn't find it in either of the wrapper modules, but I did in OpenSSL:
tobi@hal:~/src/openssl-1.0.0e$ rgrep "no certificate returned" *
doc/ssleay.txt:Error because no certificate returned.
ssl/ssl_err.c:{ERR_REASON(SSL_R_NO_CERTIFICATE_RETURNED),"no certificate
returned"},
signature.asc
Description: PGP signature
