Use bitfields for flags in the "addr" struct

[exim.git] / doc / doc-txt / ChangeLog

diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 8829de38b0c6a87fb0a16d093bcb486233be982f..abc4e9312fb7d5e846caad90ed4f49b6089d160c 100644 (file)
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -126,7 +126,7 @@ JH/18 Prebuild the data-structure for "builtin" macros, for faster startup.
 JH/19 Bug 2141: Use the full-complex API for Berkeley DB rather than the legacy-
       compatible one, to avoid the (poorly documented) possibility of a config
       file in the working directory redirecting the DB files, possibly correpting
-      some existing file.
+      some existing file.  CVE-2017-10140 assigned for BDB.
 
 JH/20 Bug 2147: Do not defer for a verify-with-callout-and-random which is not
       cache-hot.  Previously, although the result was properly cached, the
@@ -144,6 +144,10 @@ JH/23 DKIM: enforce the DNS pubkey record "h" permitted-hashes optional field,
 JH/24 Start using specified-initialisers in C structure init coding.  This is
       a C99 feature (it's 2017, so now considered safe).
 
+JH/25 Use one-bit bitfields for flags in the "addr" data structure.  Previously
+      if was a fixed-sized field and bitmask ops via macros; it is now more
+      extensible.
+
 
 Exim version 4.89
 -----------------