Thanks for Jagannadha and David for their replies and help with this.
I delved into the server-side of the code yesterday and found the
fault (luckily it's someone elses!).
Basically the server wasn't using select and fd_set/fd_isset
correctly, and was terminating the socket after 32k of recieve
Call ERR_clear_error() before while loop and call
ERR_get_error_line_data in a loop till it returns 0 inside
SSL_ERROR_SYSCALL case. This may give you some idea on what went
wrong.
JB
On 8/11/05, Michael <[EMAIL PROTECTED]> wrote:
> On 8/11/05, David Schwartz <[EMAIL PROTECTED]> wrote:
>
>
>
>
> When I try and write more than 32k I get the following messages...
>
> - Attempting to write 59266 bytes
> - Written 16384 bytes
> - Written 16384 bytes
> - SSL_ERROR_SYSCALL: error::lib(0):func(0):reason(0)
>
> I have SSL_load_error_strings() earlier in my code, but don't get any
> more
On 8/11/05, David Schwartz <[EMAIL PROTECTED]> wrote:
> > My code uses blocking sockets, has the SSL_CTX
> > SSL_MODE_ENABLE_PARTIAL_WRITE option set and loops on the ssl_read but
> > the socket is closed after the first 32k is sent.
> >
> > Why, if a message block size is 16k, does the first 32
> I have a 'problem' that has been reported before, namely that only the
> first 32k of my messages are being sent/read by my openSSL
> client/server.
>
> The original post is here:
> http://marc.theaimsgroup.com/?l=openssl-users&m=101180918225646&w=2.
>
> The solution given was to read the man pa
Hi,
I have a 'problem' that has been reported before, namely that only the
first 32k of my messages are being sent/read by my openSSL
client/server.
The original post is here:
http://marc.theaimsgroup.com/?l=openssl-users&m=101180918225646&w=2.
The solution given was to read the man pages for S
