For windows programmers, switching an existing socket from blocking to non-blocking is considered dangerous. Have a look at the "Winsock Programmer's Lame List":
http://tangentsoft.net/wskfaq/articles/lame-list.html
-- kov
I am developing for Win2K,XP,2003 and was hoping to use an IO model
e
Somebody please correct me if I'm wrong, but I believe in that case you'd receive a separate error, SSL_ERROR_ZERO_RETURN. I have, for example, experienced conditions where the end of data transmission occurred precisely on my reading buffer size. So the next SSL_raed() that I attempt results in
Client: OpenSSL 0.9.6k, Windows98
WebServer: IIS 6.0 (Don't know the OS specifics)
My client app is getting this from SSL_get_error() after an SSL_read() returning 0.
errno = ENOENT, which in the Win32 universe means "no such file or directory".
This occurs on the 3rd successive SSL_read() in t
Client: OpenSSL 0.9.6k
Server: Microsoft IIS 5.0
My client is apparently succesfully submitting to an SSL server via POST method, but after reading almost all of the output just fine I'm getting the following error from SSL_read() (which is also returns 0):
"error:0005:lib(0):func(0):bad asn
Perhaps this is a Windoze-specific problem, but I'm not able to set the callback method as an object-method.
Is it impossible?
-- kov
Is there any such thing as a consensus on which branch is preferred? Is there anything hugely new in the 0.9.7 branch that I may want to avoid for a widely distributed application?
TIA,
-- kov
I'm not a Mac programmer, but I'm playing proxy for them. We will need to support Mac down to OS9 and I'd like an idea how they will seed the PRNG. For instance, on Windows there's at least a last resort of RAND_screen(). On the MacOS 10 systems they probably have some sort of /dev/random avail
(Sorry about the last re-sending of Peter's message.)
> In case of a SSL_WANT_READ/WANT_WRITE error, what are you doing
> as a reaction?
>
> You have to select and then repeat exactly the last operation.
>
> So if you do an SSL_write and get SSL_WANT_READ, you select
> and then repeat the SSL_w
In case of a SSL_WANT_READ/WANT_WRITE error, what are you doing
as a reaction?
You have to select and then repeat exactly the last operation.
So if you do an SSL_write and get SSL_WANT_READ, you select
and then repeat the SSL_write operation.
At least this is what I rememember.
OpenSSL 0.9.6c, Windows98, Visual C++6.0.
A funny predicament. I'm creating a socket and setting it in the SSL system via SSL_set_fd() -- I'm not using BIOs. This is a very simple client to download a web-page from a server in a one-off, HTTP/1.0 manner.
I set my socket non-blocking, connect t
10 matches
Mail list logo