From: teor <teor2345@gmail.com>
Date: Thu, 23 Apr 2015 13:51:59 +0000 (+1000)
Subject: Correct "longest possible policy" comment in router policy
X-Git-Tag: tor-0.2.7.1-alpha~38^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=9a34caa4e7867c90e8d5280d84fce9cf264c1c38;p=thirdparty%2Ftor.git

Correct "longest possible policy" comment in router policy

The "longest possible policy" comment in
router_parse_addr_policy_item_from_string() used an example policy
that was actually shorter than the maximum length.

This comment was amended, and expanded to count the maximum number of
characters.

Comment change only.
---

diff --git a/src/or/routerparse.c b/src/or/routerparse.c
index b9a36a3eb1..d2eca62491 100644
--- a/src/or/routerparse.c
+++ b/src/or/routerparse.c
@@ -3361,7 +3361,9 @@ router_parse_addr_policy_item_from_string,(const char *s, int assume_action))
 {
   directory_token_t *tok = NULL;
   const char *cp, *eos;
-  /* Longest possible policy is "accept ffff:ffff:..255/ffff:...255:0-65535".
+  /* Longest possible policy is
+   * "accept6 ffff:ffff:..255/ffff:...255:10000-65535",
+   * which contains 2 max-length IPv6 addresses, plus 21 characters.
    * But note that there can be an arbitrary amount of space between the
    * accept and the address:mask/port element. */
   char line[TOR_ADDR_BUF_LEN*2 + 32];