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:
  needs-proposal-or-tor-dev-email                |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by teor):

 * keywords:  tor-relay, ipv6, reachability, needs-proposal => tor-relay,
     ipv6, reachability, needs-proposal-or-tor-dev-email


Comment:

 Replying to [comment:15 s7r]:
 > teor I'm not in any way questioning your opinion and expertise in
 implementing things,

 Thanks, but you're allowed to question my opinions and expertise. I make
 mistakes, and it's better than we pick them up early.

 > but can you please revise the keywords of this ticket and confirm if
 it's really needs-proposal?

 I don't know how Tor should behave when it's configured to advertise an
 address, but there's no corresponding listening address. I think there are
 some good arguments for the current behaviour, and for the behaviour
 you're suggesting. I don't think I have enough information to make a good
 decision here.

 So I want to know what other Tor developers think. Some of them have more
 experience with IPv6 and routing.

 That's why I want someone to email tor-dev@xxxxxxxxxxxxxxxxxxxx with a
 summary of the current behaviour, the issues with that behaviour, and the
 proposed fix.

 If you'd like, you can do that in the proposal format - proposals can be
 short:
 https://gitweb.torproject.org/torspec.git/tree/proposals/282-remove-named-
 from-consensus.txt

 Or you can write a freeform email.

 But we can't make progress on this issue until there is developer
 consensus.

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