On 10 Jan, Itay Zandbank wrote:
> However, Lutz's comment from before was correct. It's hard to do it for
> EVERY protocol, since some protocols require the server to speak first. It
> might even be impossible, because OpenSSL might actually SEND something to
> the client before realizing this isn't an SSL connection.
A solution my be using OpenSSL as a state machine. Have a look at
demos/state_machine or demos/tunala (currently only in the CVS
repository). With this technic you have the data from the socket in a
buffer where you can inspect it, if it is encrypted or not. Then you
process it normal, if it is unencrypted. Or you have to feed it to
OpenSSL via memory BIOs, if it is encrypted.
--
tschüß,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
