Re: [tor-bugs] #29570 [Core Tor/Tor]: Enforce mutually exclusive logic for IPv6 ORPort flags

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#29570: Enforce mutually exclusive logic for IPv6 ORPort flags
-------------------------------------------+-------------------------------
 Reporter:  s7r                            |          Owner:  (none)
     Type:  defect                         |         Status:  new
 Priority:  Medium                         |      Milestone:  Tor:
                                           |  unspecified
Component:  Core Tor/Tor                   |        Version:  Tor:
                                           |  unspecified
 Severity:  Normal                         |     Resolution:
 Keywords:  tor-relay, ipv6, reachability  |  Actual Points:
Parent ID:                                 |         Points:
 Reviewer:                                 |        Sponsor:
-------------------------------------------+-------------------------------

Comment (by AVee):

 I'm not sure there is a bug here. As per
 https://lists.torproject.org/pipermail/tor-
 relays/2019-February/016994.html it seems this setup is actually working.

 I fully agree that IPv6 is intended to provide end to end connectivity,
 but in practice there are a number of ways (and reasons) for network
 traffic to move from IPv4 to IPv6 and vice-versa. This setup is one of
 just them. While this case runs counter to what IPv6 intends to achieve,
 it does work... Moreover, a relay in an IPv6 only network that is through
 router tricks still reachable on a IPv4 address seems a sensible case to
 me.

 The assumption here seems to be that IPv4 and IPv6 are strictly separate
 worlds, but they are not. Therefore I'd be inclined to say pretty much
 anything advertised could be valid because pretty much anything can be
 made to work at network level and it's impossible for Tor to know about
 that. Isn't that why connectivity testing is done?

 I'm not sufficiently into the internals of Tor to know if anything there
 may prevent any of this from working. But in that case I might even argue
 that's actually a bug.

 (A warning like 'You are advertising IPv''X'' but not listening there'
 would still be useful for troubleshooting.)

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29570#comment:4>
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