summaryrefslogtreecommitdiffstats
path: root/CHANGES
diff options
context:
space:
mode:
authorDr. Stephen Henson <steve@openssl.org>2010-01-26 19:47:37 +0000
committerDr. Stephen Henson <steve@openssl.org>2010-01-26 19:47:37 +0000
commitd5e7f2f2c3262c0dbf21363259b0477082c7b98e (patch)
tree0635805e77e1f11e97b7859398501cce0e743e46 /CHANGES
parent1bfdbd8e75a70ca2d59e868f0b8947b661f709fd (diff)
PR: 1949
Submitted by: steve@openssl.org More robust fix and workaround for PR#1949. Don't try to work out if there is any write pending data as this can be unreliable: always flush.
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES8
1 files changed, 8 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index c9329f9f54..d6d863a447 100644
--- a/CHANGES
+++ b/CHANGES
@@ -884,6 +884,14 @@
Changes between 0.9.8l (?) and 0.9.8m (?) [xx XXX xxxx]
+ *) The code that handled flusing of data in SSL/TLS originally used the
+ BIO_CTRL_INFO ctrl to see if any data was pending first. This caused
+ the problem outlined in PR#1949. The fix suggested there however can
+ trigger problems with buggy BIO_CTRL_WPENDING (e.g. some versions
+ of Apache). So instead simplify the code to flush unconditionally.
+ This should be fine since flushing with no data to flush is a no op.
+ [Steve Henson]
+
*) Handle TLS versions 2.0 and later properly and correctly use the
highest version of TLS/SSL supported. Although TLS >= 2.0 is some way
off ancient servers have a habit of sticking around for a while...