From f5c20627f4660ef25334d4a7103ac2c7a8261bda Mon Sep 17 00:00:00 2001 From: Evan Hunt Date: Thu, 21 May 2015 14:29:22 -0700 Subject: [PATCH] [master] fix tags --- doc/arm/notes.xml | 76 ++++++++++++++++++++++++----------------------- 1 file changed, 39 insertions(+), 37 deletions(-) diff --git a/doc/arm/notes.xml b/doc/arm/notes.xml index e98fdbb159..34951a53f5 100644 --- a/doc/arm/notes.xml +++ b/doc/arm/notes.xml @@ -625,43 +625,45 @@ Several bugs have been fixed in the RPZ implementation: - - Policy zones that did not specifically require recursion - could be treated as if they did; consequently, setting - qname-wait-recurse no; was - sometimes ineffective. This has been corrected. - In most configurations, behavioral changes due to this - fix will not be noticeable. [RT #39229] - - - - - The server could crash if policy zones were updated (e.g. - via rndc reload or an incoming zone - transfer) while RPZ processing was still ongoing for an - active query. [RT #39415] - - - - - On servers with one or more policy zones configured as - slaves, if a policy zone updated during regular operation - (rather than at startup) using a full zone reload, such as - via AXFR, a bug could allow the RPZ summary data to fall out - of sync, potentially leading to an assertion failure in - rpz.c when further incremental updates were made to the - zone, such as via IXFR. [RT #39567] - - - - - The server could match a shorter prefix than what was - available in CLIENT-IP policy triggers, and so, an - unexpected action could be taken. This has been - corrected. [RT #39481] - - - + + + Policy zones that did not specifically require recursion + could be treated as if they did; consequently, setting + qname-wait-recurse no; was + sometimes ineffective. This has been corrected. + In most configurations, behavioral changes due to this + fix will not be noticeable. [RT #39229] + + + + + The server could crash if policy zones were updated (e.g. + via rndc reload or an incoming zone + transfer) while RPZ processing was still ongoing for an + active query. [RT #39415] + + + + + On servers with one or more policy zones configured as + slaves, if a policy zone updated during regular operation + (rather than at startup) using a full zone reload, such as + via AXFR, a bug could allow the RPZ summary data to fall out + of sync, potentially leading to an assertion failure in + rpz.c when further incremental updates were made to the + zone, such as via IXFR. [RT #39567] + + + + + The server could match a shorter prefix than what was + available in CLIENT-IP policy triggers, and so, an + unexpected action could be taken. This has been + corrected. [RT #39481] + + + +