FYI
I have seldom done low-level OpenSSL programming, but have implemented
many server based programs. The server application that does an 'accept'
on a socket is responsible for the communications on the socket, including
any timeouts or recognition of stale communication. Therefore the socket
c
I just updated my Win64 server app from OpenSSL 1.0.0k to 1.01e, and I
noticed that although it was configured to use the
SSLv23_Server_method(), it no longer accepts SSLv3 connections from
clients as it did using 1.0.0k. It does accept TLSv1 connections this
way however.
If I change it to use SSL
Hi Jason,
I am afraid you will have to deal with the TCP timeout on your own.
Here is a quick and short answer :
http://stackoverflow.com/questions/11835203/openssl-ssl-connect-blocks-forever-how-to-set-timeout
Most important : http://www.openssl.org/docs/ssl/SSL_get_error.html
I am sure your
I organize the speakers for the SF Bay Area Large-Scale Production Engineering
meetup (http://www.meetup.com/SF-Bay-Area-Large-Scale-Production-Engineering/ ;
take a look at the "PAST" tab to see the kinds of events we've had).
For our event on Thursday October 17, 2013, I'm looking for speakers o
solved. libcurl (which I used for soap server) linked openssl version from
the system, not from project
--
View this message in context:
http://openssl.6102.n7.nabble.com/CentOS-5-openssl1-0-1e-SSL-accept-error-in-SSLv2-v3-read-client-hello-A-tp46479p46545.html
Sent from the OpenSSL - User mai
