[tor-bugs] #19760 [Core Tor/Tor]: Update longclaw's hard-coded IPv6 address

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Sep 20 04:57:48 UTC 2017

#19760: Update longclaw's hard-coded IPv6 address
 Reporter:  teor                                 |          Owner:  teor
     Type:  defect                               |         Status:
                                                 |  needs_review
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.3.2.x-final
Component:  Core Tor/Tor                         |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  dir-auth, ipv6, 028-backport,        |  Actual Points:  0.2
  029-backport, 030-backport, 031-backport,      |
  032-backport                                   |
Parent ID:                                       |         Points:  0.1
 Reviewer:                                       |        Sponsor:
                                                 |  SponsorZ
Changes (by teor):

 * status:  assigned => needs_review


 Replying to [comment:13 micah]:
 > I think that the IPv6 address for longclaw should be removed in the
 source code. It was only a temporary address that I setup on teor's
 request for testing and never was meant to be something that stuck.
 Additionally, longclaw will be moving to a new location, so its ipv6
 address will go away then (I'm unsure when it will get a new one)

 See my branch longclaw-ipv6-028, which implements this change. The address
 was added in 0.2.8, so it only needs to be backported that far. We don't
 need to worry about clients here: 0.2.8 and later have plenty of fallback
 directory mirrors on IPv6, which isn't on by default anyway.

 > as well as its ipv4 address.

 Now, that will be more interesting. I assume you mean both the hard-coded
 IPv4 address, and the one in the consensus? Have they changed at all since
 longclaw was added in / / ?

 Here's what clients will do:
 * Clients with a consensus will use whatever address longclaw signs in its
 relay descriptor
 * Clients without a consensus:
   * 0.2.8 and later try multiple authorities without waiting for failures,
 so they will be fine
   * 0.2.4, 0.2.6, and 0.2.7 are no longer supported:
   * for 0.2.5, I will pull out the email that arma and I worked on last
 time we changed directory authority details, and re-post it to tor-project

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19760#comment:16>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

More information about the tor-bugs mailing list