From f40df02f3e26df792b7e364d1b6ea5dab167405c Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Fri, 15 Jul 2011 12:44:51 -0400 Subject: Treat null address as "unknown", not "rejected" in md policy Previously, we had an issue where we'd treat an unknown address as 0, which turned into "0.0.0.0", which looked like a rejected address. This meant in practice that as soon as we started doing comparisons of unknown uint32 addresses to short policies, we'd get 'rejected' right away. Because of the circumstances under which this would be called, it would only happen when we had local DNS cached entries and we were looking to launch new circuits. --- src/or/policies.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'src/or') diff --git a/src/or/policies.c b/src/or/policies.c index 5bd13b501..93cae768e 100644 --- a/src/or/policies.c +++ b/src/or/policies.c @@ -1415,8 +1415,10 @@ compare_tor_addr_to_short_policy(const tor_addr_t *addr, uint16_t port, tor_assert(port != 0); + if (addr && tor_addr_is_null(addr)) + addr = NULL; /* Unspec means 'no address at all,' in this context. */ + if (addr && (tor_addr_is_internal(addr, 0) || - tor_addr_is_null(addr) || tor_addr_is_loopback(addr))) return ADDR_POLICY_REJECTED; -- cgit v1.2.3