Gitweb:
http://git.exim.org/exim.git/commitdiff/dec5017e2e41bb85d559e2b35713f1e294cdde8c
Commit: dec5017e2e41bb85d559e2b35713f1e294cdde8c
Parent: c7396ac5dedeca5d791113782ae72b4bb67692e3
Author: Phil Pennock <pdp@???>
AuthorDate: Sat Apr 28 06:04:09 2012 -0700
Committer: Phil Pennock <pdp@???>
CommitDate: Sat Apr 28 06:04:09 2012 -0700
describe spool file changes for -tls_peerdn
---
doc/doc-txt/ChangeLog | 4 ++++
src/README.UPDATING | 14 ++++++++++++++
2 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 676aa53..03f4469 100644
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -49,6 +49,10 @@ NM/04 Bugzilla 1237 - fix cases where printf format usage no indicated
Bug report from Lars Müller <lars@???> (via SUSE),
Patch from Dirk Mueller <dmueller@???>
+PP/13 tls_peerdn now print-escaped for spool files.
+ Observed some $tls_peerdn in wild which contained \n, which resulted
+ in spool file corruption.
+
Exim version 4.77
-----------------
diff --git a/src/README.UPDATING b/src/README.UPDATING
index 3ee3035..1eb3627 100644
--- a/src/README.UPDATING
+++ b/src/README.UPDATING
@@ -26,6 +26,20 @@ 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.
+
+
Exim version 4.77
-----------------
