summaryrefslogtreecommitdiffstats
path: root/CHANGES
diff options
context:
space:
mode:
authorBen Laurie <ben@openssl.org>2009-11-08 14:51:54 +0000
committerBen Laurie <ben@openssl.org>2009-11-08 14:51:54 +0000
commitc2b78c31d631f45cd43c2d04c5ae490b8e9f21ab (patch)
tree1afd09479b364bf9787bc4c55f065360092b97b0 /CHANGES
parenta1dc0336dd482d0ce0e81d7847365de399899d5f (diff)
First cut of renegotiation extension.
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES29
1 files changed, 21 insertions, 8 deletions
diff --git a/CHANGES b/CHANGES
index 73cc1dec30..c45b286f4a 100644
--- a/CHANGES
+++ b/CHANGES
@@ -2,14 +2,17 @@
OpenSSL CHANGES
_______________
- Changes between 0.9.8k and 0.9.8l [xx XXX xxxx]
-
- *) Disable renegotiation completely - this fixes a severe security
- problem at the cost of breaking all renegotiation. Renegotiation
- can be re-enabled by setting
- OPENSSL_ENABLE_UNSAFE_LEGACY_SESSION_RENEGOTATION at
- compile-time. This is really not recommended.
- [Ben Laurie]
+ Changes between 0.9.8l and 0.9.8m [xx XXX xxxx]
+
+ *) Implement
+ https://svn.resiprocate.org/rep/ietf-drafts/ekr/draft-rescorla-tls-renegotiate.txt. Re-enable
+ renegotiation but require the extension as needed. Unfortunately,
+ SSL3_FLAGS_ALLOW_UNSAFE_LEGACY_RENEGOTIATION turns out to be a
+ bad idea. It has been replaced by
+ SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION which can be set with
+ SSL_CTX_set_options(). This is really not recommended unless you
+ know what you are doing.
+ [Eric Rescorla <ekr@networkresonance.com> and Ben Laurie]
*) Fixes to stateless session resumption handling. Use initial_ctx when
issuing and attempting to decrypt tickets in case it has changed during
@@ -95,6 +98,16 @@
*) Add 2.5.4.* OIDs
[Ilya O. <vrghost@gmail.com>]
+ Changes between 0.9.8k and 0.9.8l [5 Nov 2009]
+
+ *) Disable renegotiation completely - this fixes a severe security
+ problem (CVE-2009-3555) at the cost of breaking all
+ renegotiation. Renegotiation can be re-enabled by setting
+ SSL3_FLAGS_ALLOW_UNSAFE_LEGACY_RENEGOTIATION in s3->flags at
+ run-time. This is really not recommended unless you know what
+ you're doing.
+ [Ben Laurie]
+
Changes between 0.9.8j and 0.9.8k [25 Mar 2009]
*) Don't set val to NULL when freeing up structures, it is freed up by