summaryrefslogtreecommitdiff
path: root/src/README.UPDATING
diff options
context:
space:
mode:
authorJeremy Harris <jgh146exb@wizmail.org>2012-05-05 21:10:19 +0100
committerJeremy Harris <jgh146exb@wizmail.org>2012-05-05 21:10:19 +0100
commit76fbc01d6f1814bdbc2dedb31a405105b38a70f2 (patch)
tree195f9da7e19961a4e9164ab0c5032678f970174c /src/README.UPDATING
parent9fd2d621273cc5d9f38af480ed40bb16521bd86d (diff)
parentef8406816ea0fc82b5d80009b30cb83ad9af6f2f (diff)
Merge branch 'master' of git://git.exim.org/exim
Diffstat (limited to 'src/README.UPDATING')
-rw-r--r--src/README.UPDATING16
1 files changed, 16 insertions, 0 deletions
diff --git a/src/README.UPDATING b/src/README.UPDATING
index 3dff7c094..5b6bea869 100644
--- a/src/README.UPDATING
+++ b/src/README.UPDATING
@@ -47,6 +47,22 @@ Exim version 4.78
"openssl_options" gains "no_tlsv1_1", "no_tlsv1_2" and "no_compression".
+ COMPATIBILITY WARNING: The default value of "openssl_options" is no longer
+ "+dont_insert_empty_fragments". We default to unset. That old default was
+ grandfathered in from before openssl_options became a configuration option.
+ Empty fragments are inserted by default through TLS1.0, to partially defend
+ against certain attacks; TLS1.1+ change the protocol so that this is not
+ needed. The DIEF SSL option was required for some old releases of mail
+ clients which did not gracefully handle the empty fragments, and was
+ initially set in Exim release 4.31 (see ChangeLog, item 37).
+
+ If you still have affected mail-clients, and you see SSL protocol failures
+ with this release of Exim, set:
+ openssl_options = +dont_insert_empty_fragments
+ in the main section of your Exim configuration file. You're trading off
+ security for compatibility. Exim is now defaulting to higher security and
+ rewarding more modern clients.
+
* Ldap lookups returning multi-valued attributes now separate the attributes
with only a comma, not a comma-space sequence. Also, an actual comma within
a returned attribute is doubled. This makes it possible to parse the