Forgot to mention second fix.

[openssl.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 5f4b3d37eaf5092cb893a9bd1ce4ca1157bd3982..fd23e1a26258530ba8c53138d67e184f06f06571 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -12,23 +12,20 @@
          *) applies to 0.9.6a/0.9.6b/0.9.6c and 0.9.7
          +) applies to 0.9.7 only
 
-  *) Initialize static variable in crypto/dsa/dsa_lib.c explicitely to
-     NULL, as at least on Solaris 8 this seems not to be done automatically
-     (in contradiction to the requirements of the C standard).
-     This made problems when used from OpenSSH.
+  +) Initial reduction of linker bloat: the use of some functions, such as
+     PEM causes large amounts of unused functions to be linked in due to
+     poor organisation. For example pem_all.c contains every PEM function
+     which has a knock on effect of linking in large amounts of (unused)
+     ASN1 code. Grouping together similar functions and splitting unrelated
+     functions prevents this.
+     [Steve Henson]
+
+  *) Initialize static variable in crypto/dsa/dsa_lib.c and crypto/dh/dh_lib.c
+     explicitely to NULL, as at least on Solaris 8 this seems not always to be
+     done automatically (in contradiction to the requirements of the C
+     standard). This made problems when used from OpenSSH.
      [Lutz Jaenicke]
 
-  *) In crypto/dh/dh_key.c, change generate_key() (the default
-     implementation of DH_generate_key()) so that a new key is
-     generated each time DH_generate_key() is used on a DH object.
-
-     Previously, DH_generate_key() did not change existing keys
-     -- but ssl/s3_srvr.c always expected it to do so (in effect,
-     SSL_OP_SINGLE_DH_USE was ignored in servers reusing the same SSL
-     object for multiple connections; however, each new SSL object
-     created from an SSL_CTX got its own key).
-     [Bodo Moeller]
-
   *) In OpenSSL 0.9.6a and 0.9.6b, crypto/dh/dh_key.c ignored
      dh->length and always used