Browse Source

[trac999] renamed a test name as suggested in review.

JINMEI Tatuya 14 years ago
parent
commit
21a333f512
2 changed files with 14 additions and 1 deletions
  1. 13 0
      ChangeLog
  2. 1 1
      src/bin/resolver/tests/resolver_config_unittest.cc

+ 13 - 0
ChangeLog

@@ -1,3 +1,16 @@
+261.?	[func]*		jinmei
+	b10-resolver: Introduced ACL on incoming queries.  By default the
+	resolver accepts queries from ::1 and 127.0.0.1 and rejects all
+	others.  The ACL can be configured with bindctl via the
+	"Resolver/query_acl" parameter.  For example, to accept queries
+	from 192.0.2.0/24 (in addition to the default list), do this:
+	> config add Resolver/query_acl
+	> config set Resolver/query_acl[2]/action "ACCEPT"
+	> config set Resolver/query_acl[2]/from "192.0.2.0/24"
+	> config commit
+	(Trac #999, git TBD,
+	also based on other ACL related work done by stephen and vorner)
+
 260.	[func]      stephen
 	Remove comma between message identification and the message
 	text in the new-style logging messages.

+ 1 - 1
src/bin/resolver/tests/resolver_config_unittest.cc

@@ -294,7 +294,7 @@ TEST_F(ResolverConfig, queryACLIPv6) {
                   createClient("2001:db8::1")));
 }
 
-TEST_F(ResolverConfig, compoundQueryACL) {
+TEST_F(ResolverConfig, multiEntryACL) {
     // A bit more complicated one: mixture of IPv4 and IPv6 with 3 rules
     // in total.  We shouldn't have to check so many variations of rules
     // as it should have been tested in the underlying ACL module.  All we