[tor-bugs] #19792 [Core Tor/TorDNSEL]: Exiting through undocumented nodes (IPs not listed)
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Aug 2 04:16:04 UTC 2016
#19792: Exiting through undocumented nodes (IPs not listed)
-------------------------------+-------------------------------
Reporter: cypherpunks | Owner:
Type: defect | Status: closed
Priority: Medium | Milestone:
Component: Core Tor/TorDNSEL | Version: Tor: 0.2.5.12
Severity: Normal | Resolution: not a bug
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------+-------------------------------
Changes (by teor):
* status: new => closed
* resolution: => not a bug
* component: Core Tor/Tor => Core Tor/TorDNSEL
Comment:
It is a supported configuration for an Exit to use a different IP address
for its ORPort/DirPort and exit traffic.
This is likely due to an Exit using the OutboundBindAddress option, or
doing the moral equivalent using iptables, NAT, or a VPN.
From the tor manual page:
OutboundBindAddress IP
Make all outbound connections originate from the IP address
specified. This is only useful when you have multiple network
interfaces, and you want all of Tor's outgoing connections to
use a
single one. This option may be used twice, once with an IPv4
address and once with an IPv6 address. This setting will be
ignored
for connections to the loopback addresses (127.0.0.0/8 and
::1).
Therefore, the source IP of exit traffic is not something we tend to worry
about. (And if the exit has enough consensus weight, we will pick it up
eventually in the exit list.)
https://exonerator.torproject.org/
But if you have evidence that the content of Exit traffic is being
modified or inspected, please write to bad-relays at lists.torproject.org
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19792#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list