From 4f83aaa7cc34a880c7fc2332bcb6cd36b0b01a08 Mon Sep 17 00:00:00 2001 From: Dan Winship Date: Tue, 25 Sep 2001 21:14:09 +0000 Subject: call SSL_read/write, looping on SSL_ERROR_WANT_READ/WRITE. I'm sure * camel-tcp-stream-openssl.c (my_SSL_read, my_SSL_write): call SSL_read/write, looping on SSL_ERROR_WANT_READ/WRITE. I'm sure there's a perfectly good reason that the API works this way. No, really. (stream_read, stream_write): use my_SSL_read and my_SSL_write. Fixes at least ximian 8593, and probably 6024 and maybe 10366, at least for OpenSSL. There may be a parallel NSS bug? svn path=/trunk/; revision=13121 --- camel/ChangeLog | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'camel/ChangeLog') diff --git a/camel/ChangeLog b/camel/ChangeLog index 6a8ad6193d..b98ca0888a 100644 --- a/camel/ChangeLog +++ b/camel/ChangeLog @@ -1,3 +1,13 @@ +2001-09-25 Dan Winship + + * camel-tcp-stream-openssl.c (my_SSL_read, my_SSL_write): call + SSL_read/write, looping on SSL_ERROR_WANT_READ/WRITE. I'm sure + there's a perfectly good reason that the API works this way. No, + really. + (stream_read, stream_write): use my_SSL_read and my_SSL_write. + Fixes at least ximian 8593, and probably 6024 and maybe 10366, + at least for OpenSSL. There may be a parallel NSS bug? + 2001-09-25 * camel-stream-buffer.c (stream_write_all): A "safe write" -- cgit v1.2.3