Gitweb:
http://git.exim.org/exim.git/commitdiff/f90a9fd133ac62eb3fa1e834b3bff16360d23500
Commit: f90a9fd133ac62eb3fa1e834b3bff16360d23500
Parent: 08488c86321f6fcb1da015ebfcc2b6fe3a2832d4
Author: Phil Pennock <pdp@???>
AuthorDate: Fri May 18 19:17:38 2012 -0400
Committer: Phil Pennock <pdp@???>
CommitDate: Fri May 18 19:17:38 2012 -0400
Torture the English language slightly less
---
src/README.UPDATING | 12 +++++++-----
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/src/README.UPDATING b/src/README.UPDATING
index 62d1d27..7ce35df 100644
--- a/src/README.UPDATING
+++ b/src/README.UPDATING
@@ -80,16 +80,18 @@ Exim version 4.80
new option, you can safely force it off before upgrading, to decouple
configuration changes from the binary upgrade while remaining RFC compliant.
- * The GnuTLS support has been mostly rewritten, to use 2.12.x APIs. As part
- of this, these three options are no longer supported:
+ * The GnuTLS support has been mostly rewritten, to use APIs which don't cause
+ deprecation warnings in GnuTLS 2.12.x. As part of this, these three options
+ are no longer supported:
gnutls_require_kx
gnutls_require_mac
gnutls_require_protocols
- Their functionality is entirely subsumed into tls_require_ciphers, which is
- no longer parsed apart by Exim but is instead given to
- gnutls_priority_init(3), which is no longer an Exim list. See:
+ Their functionality is entirely subsumed into tls_require_ciphers. In turn,
+ tls_require_ciphers is no longer an Exim list and is not parsed by Exim, but
+ is instead given to gnutls_priority_init(3), which expects a priority string;
+ this behaviour is much closer to the OpenSSL behaviour. See:
http://www.gnu.org/software/gnutls/manual/html_node/Priority-Strings.html