> The problem is that you send 'ssl on', then immediately switch to SSL
> mode,
>and then send the first part of the SSL handshake. When the server goes to
>receive the data, it receives 'ssl on\n' and recognizes the
>'ssl on' and turns on SSL mode. But that chunk of the SSL handshake has
>
> Okay, interesting development. If I put a sleep(5); on the C client
> before I issue SSL_connect (but after I BIO_write "ssl on\n"),
> everything works fine. Otherwise both client and server deadlock on
> read/recv.
Makes perfect sense. The problem is that the server has already receive
Okay, interesting development. If I put a sleep(5); on the C client
before I issue SSL_connect (but after I BIO_write "ssl on\n"),
everything works fine. Otherwise both client and server deadlock on
read/recv.
Ray Russell Reese III wrote:
>There seems to be a problem with the client however. I s
I think you can try s_client program, in apps directory.
Using it, you can write "ssl on" after SSL negotiation and see what happens.
If it works, you can use it to build your program. It has all you need.
__
OpenSSL Project
