#19919: If ORPort address is publicly routable, use it to guess Address
 Reporter:  teor          |          Owner:
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |        Version:  Tor:
 Severity:  Normal        |     Resolution:
 Keywords:  030-proposed  |  Actual Points:
Parent ID:                |         Points:  1
 Reviewer:                |        Sponsor:

Comment (by teor):

 Replying to [comment:9 s7r]:
 > Correct. We should leave `OutboundBindAddress` for the time being. This
 tor-dev thread confirms adding the algorithm to `OutboundBindAdress` would
 not work for at least this use case:
 > https://lists.torproject.org/pipermail/tor-
 > While applying the algorithm to `Address` as described in this ticket
 would fix it, and plenty more use cases. So, we'll leave
 `OutboundBindAddress` aside currently. I don't know, does
 `OutboundBindAddress == Address` unless configured otherwise?

 No, the outbound address is left unspecified by Tor unless configured
 explicitly by the user. So the OS determines the outbound address, which
 can vary depending on the destination (routing table) on multi-homed

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19919#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
tor-bugs mailing list

Reply via email to