summaryrefslogtreecommitdiffstats
path: root/CHANGES
diff options
context:
space:
mode:
authorDr. Stephen Henson <steve@openssl.org>2009-12-08 19:06:26 +0000
committerDr. Stephen Henson <steve@openssl.org>2009-12-08 19:06:26 +0000
commit82e610e2cfbbb5fd29c09785b6909a91e606f347 (patch)
tree9cbcb713797c3aea336aeb4f86088f91cc7c5a38 /CHANGES
parent5430200b8b9528861ec9759623107f407ba8c38f (diff)
Send no_renegotiation alert as required by spec.
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES11
1 files changed, 11 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index d3596e6b05..24be6c51bc 100644
--- a/CHANGES
+++ b/CHANGES
@@ -863,6 +863,17 @@
Changes between 0.9.8l (?) and 0.9.8m (?) [xx XXX xxxx]
+ *) If client attempts to renegotiate and doesn't support RI respond with
+ a no_renegotiation alert as required by draft-ietf-tls-renegotiation.
+ Some renegotiating TLS clients will continue a connection gracefully
+ when they receive the alert. Unfortunately OpenSSL mishandled
+ this alert and would hang waiting for a server hello which it will never
+ receive. Now we treat a received no_renegotiation alert as a fatal
+ error. This is because applications requesting a renegotiation might well
+ expect it to succeed and would have no code in place to handle the server
+ denying it so the only safe thing to do is to terminate the connection.
+ [Steve Henson]
+
*) Add ctrl macro SSL_get_secure_renegotiation_support() which returns 1 if
peer supports secure renegotiation and 0 otherwise. Print out peer
renegotiation support in s_client/s_server.