[tor-bugs] #23592 [Core Tor/Tor]: Update longclaw's IPv4 address (after it moves)
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Sep 20 05:00:51 UTC 2017
#23592: Update longclaw's IPv4 address (after it moves)
------------------------------+--------------------------------
Reporter: teor | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: Tor: 0.3.2.x-final
Component: Core Tor/Tor | Version: Tor: 0.2.6.2-alpha
Severity: Normal | Keywords: tor-dir-auth
Actual Points: | Parent ID:
Points: 0.5 | Reviewer:
Sponsor: |
------------------------------+--------------------------------
Longclaw will soon move IPv4 addresses. Its current address was added in
0.2.6.2-alpha.
Will it have multiple IPv4 addresses?
(One for the hard-coded address, and one for the consensus?)
How does this impact 0.2.5 clients?
* 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:
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23592>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list