From: Phil Pennock Date: Sat, 28 Apr 2012 13:04:09 +0000 (-0700) Subject: describe spool file changes for -tls_peerdn X-Git-Tag: exim-4_80_RC1~52 X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=dec5017e2e41bb85d559e2b35713f1e294cdde8c;p=exim.git describe spool file changes for -tls_peerdn --- diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog index 676aa534c..03f4469af 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 (via SUSE), Patch from Dirk Mueller +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 3ee3035e9..1eb36277e 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 -----------------