Age | Commit message (Collapse) | Author |
|
Add the standard future statements, so Python 2 will use some
Python 3 features.
Open files as UTF-8. As a consequence of this change, proposals
must be encoded in UTF-8.
Closes ticket 33164.
|
|
Some people don't have their best python in /usr/bin.
Other people only have python in /usr/local/bin, or other places.
|
|
|
|
Part of 24404.
|
|
Part of 33073.
|
|
|
|
As suggested by s7r.
Part of 33073.
|
|
Part of 33073.
|
|
Document tor's current address detection state management, and our
new state management for IPv4 and IPv6 address detection.
As suggested by Nick Mathewson.
Part of 33073.
|
|
As suggested by Nick Mathewson.
Part of 33073.
|
|
Add an optional change.
Part of 33073.
|
|
As suggested by Nick Mathewson and s7r.
Part of 33073.
|
|
Only use explicit IPv4 and IPv6 address literals, configured in Address
or ORPort lines, for directory authority addresses.
As suggested by Nick Mathewson.
Part of 33073.
|
|
Part of 33073.
|
|
As suggested by Nick Mathewson.
Part of 33073.
|
|
All these changes are optional in the proposal:
* Add the NETINFO cell address detection method
(as suggested by Nick Mathewson)
* Defer decisions about ignoring some addresses, or using those
addresses as the lowest priority method
* Simplify the load-balancing design
Part of 33073.
|
|
Explain why we might need to turn IPv6 address detection off.
Part of 33073.
|
|
Add an optional section, where we propose using a directory authority
IPv4 and IPv6 address for socket-based local interface address
detection.
As suggested by Nick Mathewson.
Part of 33073.
|
|
As suggested by Nick Mathewson.
Part of 33073.
|
|
Explain why some relays may not have any publicly routable interface
addresses.
Part of 33073.
|
|
It's unlikely to be useful for most configurations.
As suggested by Nick Mathewson.
Part of 33073.
|
|
Explain how we choose between multiple addresses, in a list, and over
time.
Part of 33073.
|
|
And describe a potential attack that gives a relay the wrong address,
then monitors its traffic.
As suggested by Nick Mathewson.
Part of 33073.
|
|
Since relays put the discovered IPv6 address in their descriptor,
it needs to be publicly routable. (If the relay is on the public
network.)
As suggested by Nick Mathewson.
Also fix inconsistent use of directory authority, directory server,
and directory mirror.
Part of 33073.
|
|
Add an optional change to support clients extending as soon as
possible, after a relay restarts.
Part of 33073.
|
|
Add information about binding to IPv4 and IPv6.
Also do a slight reformat.
Part of 33073.
|
|
Part of 33073.
|
|
And why it shouldn't affect tor relays, at least with the default
settings.
As suggested by s7r.
Part of 33073.
|
|
Part of 33073.
|
|
And explain why we didn't use the existing ORPort IPv4Only flag to
disable IPv6 address resolution.
Part of 33073.
|
|
Part of 33073
|
|
Part of 33073.
|
|
Related tickets: 33073 (proposal), 5940 (implementation).
|
|
Part of 24404.
|
|
We want to allow relays to upgrade to trying both addresses in an
EXTEND2 cell, without requiring a new protocol version.
The spec documents the planned "choose at random" behaviour, but
allows relays to try both IPv4 and IPv6 in future.
Part of 24404.
|
|
Part of 24404.
|
|
We don't want to depend on extends preferring IPv4 or IPv6,
or the exact extend implementation, if we don't have to.
Part of 24404.
|
|
Part of 24404.
|
|
* don't ban useful behaviours, just mention that they might not happen
* don't talk about reachability, other tor instances don't care
* specify random choice between IPv4 and IPv6 (and add a TODO)
As suggested by Nick Mathewson.
Part of 24404.
|
|
As suggested by Nick Mathewson.
Part of 24404.
|
|
And add extra logging when tor would have previously found itself
reachable, but the new checks fail.
As suggested by Nick Mathewson.
Part of 24404.
|
|
Add an alternate design, suggested by Nick Mathewson.
Part of 24404.
|
|
As suggested by Nick Mathewson.
Part of 24404.
|
|
We want to support these two cases:
* upgrade to working IPv6,
* stay on IPv4-only, if a guessed IPv6 address isn't reachable.
Part of 24404.
|
|
Part of 24404.
|
|
Part of 24404.
|
|
Part of 24404.
|
|
Some of the statistics may also be available in relay heartbeat logs.
Part of 24404.
|
|
Improve the explanations of some of the references to proposal 306:
Client Auto IPv6 Connection. And add a section that specifically
mentions modifying that proposal.
Part of 24404.
|
|
Some IPv6 behaviour has changed in recent tor versions, as noted in the
proposal.
Part of 24404.
|