Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2012-10-31T14:17:48Zhttps://gitlab.torproject.org/legacy/trac/-/issues/7268microdesc error2012-10-31T14:17:48ZTracmicrodesc errorError in messagelog.
Oct 31 17:20:47.025 [Warning] microdesc_free(): Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1
occurs time to time.
**Trac**:
**Username**: fedosisError in messagelog.
Oct 31 17:20:47.025 [Warning] microdesc_free(): Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1
occurs time to time.
**Trac**:
**Username**: fedosishttps://gitlab.torproject.org/legacy/trac/-/issues/7254Orbot WARNs DNSPort and TransPort public address specified2020-06-13T01:40:54ZcypherpunksOrbot WARNs DNSPort and TransPort public address specified"WARN You specified and public address for DNSPort (and TransPort). Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason."
I don't have a good reason an..."WARN You specified and public address for DNSPort (and TransPort). Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason."
I don't have a good reason and want to fix this. There are 4 WARN messages, 1 DNSPort, another TransPort, another DNSPort and another Transport. They repeat as the Orbot log updates itself.
Orbot version 0.2.3.23-rc-1.0.11-RC6 on Samsung EXhibit II running CyanogenMod version 9-20120826_UNOFFICIAL-aancora-tmo
Hopefully I'm posting correctly in the correct place.Nathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/7192parsing exit policy summary drops last character2020-06-13T14:24:04ZRoger Dingledineparsing exit policy summary drops last characterTor: 0.2.3.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/7190tor client ignores ClientRejectInternalAddresses when considering short exit ...2020-06-13T14:24:02ZRoger Dingledinetor client ignores ClientRejectInternalAddresses when considering short exit policiesErik Kline found that when setting up an internal Tor network using 0.2.3, even if the exit relays support exiting to an 'internal' IP address, the client preemptively refuses to do so.
Here's the patch he provides:
```
diff -rupN tmp/t...Erik Kline found that when setting up an internal Tor network using 0.2.3, even if the exit relays support exiting to an 'internal' IP address, the client preemptively refuses to do so.
Here's the patch he provides:
```
diff -rupN tmp/tor-0.2.3.20-rc/src/or/policies.c tor-0.2.3.20-rc/src/or/policies.c
--- tmp/tor-0.2.3.20-rc/src/or/policies.c 2012-08-04 22:24:35.000000000 -0700
+++ tor-0.2.3.20-rc/src/or/policies.c 2012-09-11 10:28:19.000000000 -0700
@@ -1428,13 +1428,13 @@ compare_tor_addr_to_short_policy(const t
int found_match = 0;
int accept;
(void)addr;
-
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) ||
+ if (addr && ((tor_addr_is_internal(addr, 0)
+ && get_options()->ClientRejectInternalAddresses) ||
tor_addr_is_loopback(addr)))
return ADDR_POLICY_REJECTED;
```Tor: 0.2.3.x-final