X-Git-Url: https://git.exim.org/users/jgh/exim.git/blobdiff_plain/a7ee59558e5cf70be000dbf421d69fb6c8c171c4..3fb3c68d8b8efb6569dedc2711307826f8cd6973:/src/README.UPDATING?ds=sidebyside

diff --git a/src/README.UPDATING b/src/README.UPDATING
index 3ee3035e9..9e3689d84 100644
--- a/src/README.UPDATING
+++ b/src/README.UPDATING
@@ -26,6 +26,29 @@ The rest of this document contains information about changes in 4.xx releases
 that might affect a running system.
 
 
+Exim version 4.78
+-----------------
+
+ * The value of $tls_peerdn is now print-escaped when written to the spool file
+   in a -tls_peerdn line, and unescaped when read back in.  We received reports
+   of values with embedded newlines, which caused spool file corruption.
+
+   If you have a corrupt spool file and you wish to recover the contents after
+   upgrading, then lock the message, replace the new-lines that should be part
+   of the -tls_peerdn line with the two-character sequence \n and then unlock
+   the message.  No tool has been provided as we believe this is a rare
+   occurence.
+
+ * With OpenSSL 1.0.1+, Exim now supports TLS 1.1 and TLS 1.2.  If built
+   against 1.0.1a then you will get a warning message and the
+   "openssl_options" value will not parse "no_tlsv1_1": the value changes
+   incompatibly between 1.0.1a and 1.0.1b, because the value chosen for 1.0.1a
+   is infelicitous.  We advise avoiding 1.0.1a.
+
+   "openssl_options" gains "no_tlsv1_1", "no_tlsv1_2" and "no_compression".
+
+
+
 Exim version 4.77
 -----------------