On Thu, Aug 16, 2001 at 11:24:48AM -0400, Robert Pungello wrote:
> >The error message you are seeing says:
> >* You are on the server side (because it happens in the
> SSL3_GET_CLIENT_HELLO
> > stage; only the server _gets_ the client hello, the client sends it).
> >* Your server has decided that there is no shared cipher in the client
> hello.
> > See "man SSL_CTX_set_cipher_list" or better look up
> > http://www.openssl.org/docs/ssl/SSL_CTX_set_cipher_list.html
> > as new information was added since the release of 0.9.6b.
>
> Thanks for your response Lutz. In the short term, I was simply trying to
> get the alert code (40 in this case) so that I can map the error to one of
> the SSL/TLS alerts (close_notify = 0, unexpected_message = 10, etc.) Any
> suggestions?
Hmm. The error messages and the corresponding alert are hardcoded into
the SSL library, at the locations the problem occurs. There is no table
or whatever from which you could find the alert sent from the error message
you see.
The only idea I could offer would be to use the info_callback to catch
the alert sent to the peer...
info_callback is not yet documented, but you should be able to read
the functionality from the s_server example...
Best regards,
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik Tel. +49 355 69-4129
Universitaetsplatz 3-4, D-03044 Cottbus Fax. +49 355 69-4153
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
