Hi,
SSL_pending() returns the number of bytes in the SSL buffer that have been
decrypted by not requested by SSL_read(). This will occur when there is a
mismatch between the number of bytes requested by SSL_read() and the block
size used to encrypt/decrypt the data.
SSL_ERROR_WANT_READ (and
You can use Anonymous Diffie-Hellman cipher, which is excluded from the
default cipher list. But beware ... this will not stop a man-in-the-middle
attack. You should look at the set cipher functions in the manual pages.
G.
-Original Message-
From: Petr Knez [mailto:[EMAIL PROTECTED]]
]]
Sent: 10 July 2001 21:04
To: '[EMAIL PROTECTED]'
Subject: Re: Return code from SSL_write
On Tue, Jul 10, 2001 at 03:55:24PM +0100, Shaw, George wrote:
I'm encountering a problem with SSL_write when writing a large amount of
data (about 1Mb) using non-blocking sockets.
For smaller amounts of data
Hi,
I'm encountering a problem with SSL_write when writing a large amount of
data (about 1Mb) using non-blocking sockets.
For smaller amounts of data (about 1kb), the return code (bytes written)
what you would expect.
For the larger amount of data, the return code is -1. When checking
]
_
- Original Message -
From: "Shaw, George" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, April 19, 2001 6:12 AM
Subject: RE: Closing SSL connections
Thanks again Greg,
I did a little more testing. As you indicated in your earlier mail, if
Hi,
As an addendum to my other thread on closing SSL connections safely in an
HTTP environment, most of my testing there was done between my own client
and server.
Now I start testing with IIS, and the IIS server looks like it closes the
SSL connection "illegally", as my client gets
Hi,
I'm working with an HTTP application, and according to the RFC when sending
the HTTP response it is permissible to signal the end of the response by
closing the socket (rather than using the Content-Length header).
When implementing the HTTP client using SSL, SSL_read will return
/SSL_set_shutdown.html#) for some hints of
what to do.
_
Greg Stark
Ethentica, Inc.
[EMAIL PROTECTED]
_
- Original Message -
From: "Shaw, George" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, April 18, 200
What version of SSL is the client using using? I've had this problem
before, and there are other mails in the archive which describe this error,
when a "broken" server cannot perform SSL version negotiation properly, i.e
if your client is using SSL version 23. Hardcoding the version to 2 or 3
