Sebastian Treu:
> > If you set ALLOW_MOVING_WRITE_BUFFER, the restriction is relaxed. The
> > only
> > restriction that remains is that you must present a consistent data
> > stream.
> > For example, if you try to SSL_write "foo" and two bytes are sent,
> > your next
> > SSL_write *must* start wit
On Sat, Dec 12, 2009 at 4:12 PM, David Schwartz wrote:
> Sebastian Treu wrote:
>
>> Well, maybe I miss the point of what man pages wanted to say with:
>>
>> "[...]
>> WARNING
>> When an SSL_write() operation has to be repeated because of
>> SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE
Sebastian Treu wrote:
> Well, maybe I miss the point of what man pages wanted to say with:
>
> "[...]
> WARNING
>When an SSL_write() operation has to be repeated because of
>SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE, it must be repeated
> with
>the same arguments.
> [...
Hi all
Can anybody tell me about the latest version of OpenSSL?
Actually i installed OpenSSL 0.9.8l . can we use it on Windows?
Actually for practice i want to do this on Windows only.
So please tell me the latest version of OpenSSL for windows.
Thanks.
--
View this message in context:
ht
On Sat, Dec 12, 2009 at 7:19 AM, Sebastián Treu
wrote:
> differents arguments. I also noted that SSL_write() is "clever" enough
> to send _any_ length, so segmented writes will be overriding that
> warning (if I undestood what man wanted to say). When I say clever
> enough, I meant that in what I
Hi David,
>> Others things are to instantaneously put that client in a wait list
>> when SSL_write() could not succed, continue with the others, and try
>> with that client again later. But, sometimes we can get a WANT_WRITE
>> or WANT_READ when renegotiating so this does not appears a solution.
