[v9_12] update README and notes

diff --git a/README b/README
index e49810c916ca9257cbdfee18c6c13a2b09a2e982..0b10096ed5e195fda78b105d37e21aa8cb984924 100644 (file)
--- a/README
+++ b/README
@@ -124,6 +124,10 @@ include:
     default without a configure option.
   * The obsolete isc-hmac-fixup command has been removed.
 
+BIND 9.12.1
+
+BIND 9.12.1 is a maintenance release.
+
 Building BIND
 
 BIND requires a UNIX or Linux system with an ANSI C compiler, basic POSIX

diff --git a/README.md b/README.md
index 5c6005c7f49cd2520bd189cc0779346a40a9a342..6f31c3b0c3d7847ec51a19e0d482e0c64e55a560 100644 (file)
--- a/README.md
+++ b/README.md
@@ -136,6 +136,10 @@ include:
   by default without a configure option.
 * The obsolete `isc-hmac-fixup` command has been removed.
 
+#### BIND 9.12.1
+
+BIND 9.12.1 is a maintenance release.
+
 ### <a name="build"/> Building BIND
 
 BIND requires a UNIX or Linux system with an ANSI C compiler, basic POSIX

diff --git a/doc/arm/notes.xml b/doc/arm/notes.xml
index bc41cbbf5c3617e3b2cb5f484cac04071ed61c9b..e95c53b4204d1ceb2543735d494b1c4bd92904a4 100644 (file)
--- a/doc/arm/notes.xml
+++ b/doc/arm/notes.xml
@@ -37,22 +37,13 @@
 
   <section xml:id="relnotes_security"><info><title>Security Fixes</title></info>
     <itemizedlist>
-      <listitem>
-       <para>
-         Addresses could be referenced after being freed during resolver
-         processing, causing an assertion failure. The chances of this
-         happening were remote, but the introduction of a delay in
-         resolution increased them. This bug is disclosed in
-         CVE-2017-3145. [RT #46839]
-       </para>
-      </listitem>
       <listitem>
        <para>
          update-policy rules that otherwise ignore the name field now
          require that it be set to "." to ensure that any type list
-         present is properly interpreted.  If the name field was omitted
-         from the rule declaration and a type list was present it wouldn't
-         be interpreted as expected.
+         present is properly interpreted.  Previously, if the name field
+         was omitted from the rule declaration but a type list was
+         present, it wouldn't be interpreted as expected.
        </para>
       </listitem>
     </itemizedlist>
@@ -81,11 +72,9 @@
       </listitem>
       <listitem>
        <para>
-         Attempting to validate improperly unsigned CNAME responses
-         from secure zones could cause a validator loop. This caused
-         a delay in returning SERVFAIL and also increased the chances
-         of encountering the crash bug described in CVE-2017-3145.
-         [RT #46839]
+         <command>named</command> could crash when acting as a slave for a
+         catalog zone if zone contained a master definition without an IP
+         address. [RT #45999]
        </para>
       </listitem>
     </itemizedlist>