[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9612 [Core Tor/Tor]: Wrong IP used from /etc/hosts
#9612: Wrong IP used from /etc/hosts
--------------------------+----------------------------------
Reporter: massar | Owner:
Type: defect | Status: new
Priority: Low | Milestone: Tor: unspecified
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-relay | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------+----------------------------------
Changes (by arma):
* severity: => Normal
Comment:
The old answer here is "you didn't set your Address line, so what did you
expect?"
I wonder if the new answer should be that we look at the IP address you
used in your ORPort line, if present, and prefer that guess over the "ask
for our hostname, then try to resolve it" heuristic.
(That new answer is newly possible now that ORPorts can have IP addresses
in them too.)
That said, am I right that the {{{ORPort 192.0.2.1:443}}} syntax is bad
news because it (maybe surprisingly) doesn't listen on 0.0.0.0, so e.g. it
won't listen on localhost? If so I would argue that people who are trying
to set their Address line by putting an IP address in the ORPort line are
doing it wrong.
I guess a much simpler first step could be to notice when the operator
puts an IP address in ORPort or DirPort, but *doesn't* set their Address
line, and give them a warning?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9612#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs