[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #24338 [Core Tor/Tor]: DirAuths that have IPv6 addresses don't include them in their vote on themself



#24338: DirAuths that have IPv6 addresses don't include them in their vote on
themself
-------------------------------+------------------------------------
 Reporter:  tom                |          Owner:  (none)
     Type:  defect             |         Status:  new
 Priority:  Medium             |      Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor       |        Version:
 Severity:  Normal             |     Resolution:
 Keywords:  IPv6, tor-dirauth  |  Actual Points:
Parent ID:  #20916             |         Points:  1
 Reviewer:                     |        Sponsor:  SponsorV-can
-------------------------------+------------------------------------
Changes (by teor):

 * keywords:   => IPv6, tor-dirauth
 * points:   => 1
 * sponsor:   => SponsorV-can
 * parent:   => #20916
 * milestone:   => Tor: 0.3.3.x-final


Comment:

 Authorities should assume their configured IPv6 address is reachable, just
 like they do for IPv4.

 > Also strange: dannenberg votes on ReachableIPv6 but is not itself
 granted ReachableIPv6

 That's not surprising: voting on ReachableIPv6 requires outbound IPv6
 connectivity (like IPv6Exit).
 But receiving ReachableIPv6 requires inbound connectivity to an IPv6
 ORPort. Does it declare one in its descriptor?

 If it does, I'll email the dirauth list to let them know there's a
 misconfiguration, because it could end up with dannenberg not being marked
 Running,

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