P. George wrote:
i am trying to get the following little hello-world ssl sample to run on
win32 using winsock2:
http://www.uweb.ucsb.edu/~jramrus/stuff/NetProgs/ssl_server.c
it compiles and runs fine on my os x machine. however, when i take the
same code and drag it over to windows and add a call to WSAStartup()
before the call to socket() and add all the libraries and includes that
are applicable to windows and remove the includes that are only for
*nix, it fails when it gets to SSL_read().
it blocks on accept() as it is supposed to, and when i connect (but do
_not_ yet send any data) i see the connection on the server, but then it
dies on SSL_read(), which is weird, because i haven't sent any actual
data over yet (at that point).
if i call SSL_get_error() on the next line, i get: SSL_ERROR_SYSCALL .
the documentation is kinda vague about what that actually means and what
to do about it.
what am i doing wrong here?
Please show us a stack trace. How did it die?
--
Lev Walkin
[EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
