3097 Commits

Author SHA1 Message Date
teor
1f9f3986d1
Prop 312: Add Ignore Addresses on Inbound Conns
Add an optional change.

Part of 33073.
2020-02-05 22:05:53 +10:00
teor
13e8c8c231
Prop 312: Define an IPv6 sybil block
As suggested by Nick Mathewson and s7r.

Part of 33073.
2020-02-05 22:05:31 +10:00
teor
89e7222f65
Prop 312: Require explicit authority addresses
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.
2020-02-05 22:05:07 +10:00
teor
55d3beb6c2
Prop 312: Make bridge changes clearer
Part of 33073.
2020-02-05 22:05:00 +10:00
teor
e1815226f1
Prop 312: Avoid some address detection state
As suggested by Nick Mathewson.

Part of 33073.
2020-02-05 22:04:47 +10:00
teor
043ac7d7aa
Prop 312: Rewrite authenticated address detection
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.
2020-02-05 22:04:10 +10:00
teor
7269d17c6f
Prop 312: Improve AddressDisableIPv6
Explain why we might need to turn IPv6 address detection off.

Part of 33073.
2020-02-05 22:04:04 +10:00
teor
6e7d4abd1f
Prop 312: Use Authority IPs for the Socket Method
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.
2020-02-05 22:03:50 +10:00
teor
f090a2233c
Prop 312: Explain address resolution using sockets
As suggested by Nick Mathewson.

Part of 33073.
2020-02-05 22:03:33 +10:00
teor
fd4716f1ce
Prop 312: Improve interface address method
Explain why some relays may not have any publicly routable interface
addresses.

Part of 33073.
2020-02-05 22:03:26 +10:00
teor
0159850437
Prop 312: Remove the DirPort method
It's unlikely to be useful for most configurations.

As suggested by Nick Mathewson.

Part of 33073.
2020-02-05 22:03:12 +10:00
teor
f12ddad6bf
Prop 312: Explain how to choose addresses
Explain how we choose between multiple addresses, in a list, and over
time.

Part of 33073.
2020-02-05 22:03:05 +10:00
teor
7a55bf1662
Prop 312: Explain why untrusted addresses are bad
And describe a potential attack that gives a relay the wrong address,
then monitors its traffic.

As suggested by Nick Mathewson.

Part of 33073.
2020-02-05 22:02:52 +10:00
teor
8a9ea6f224
Prop 312: Explain public IPv6 addresses
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.
2020-02-05 22:02:33 +10:00
teor
66d08ba358
Prop 312: Add an early extends section
Add an optional change to support clients extending as soon as
possible, after a relay restarts.

Part of 33073.
2020-02-05 22:02:26 +10:00
teor
534114e2c3
Prop 312: Improve auto IPv6 ORPort section
Add information about binding to IPv4 and IPv6.

Also do a slight reformat.

Part of 33073.
2020-02-05 22:02:22 +10:00
teor
77da452bd6
Prop 312: Fix a heading
Part of 33073.
2020-02-05 22:02:18 +10:00
teor
8902ece4fe
Prop 312: Add info on IPv6 address privacy
And why it shouldn't affect tor relays, at least with the default
settings.

As suggested by s7r.

Part of 33073.
2020-02-05 22:02:03 +10:00
teor
615ebe5fd4
Prop 312: Explain default outbound address better
Part of 33073.
2020-02-05 22:01:57 +10:00
teor
0e20e5a067
Prop 312: Add an alternative IPv6 disable design
And explain why we didn't use the existing ORPort IPv4Only flag to
disable IPv6 address resolution.

Part of 33073.
2020-02-05 22:01:54 +10:00
teor
f1af76a78a
Prop 312: Explain private address handling better
Part of 33073
2020-02-05 22:01:48 +10:00
teor
0cafa9dfba
Prop 312: Reformat references
Part of 33073.
2020-02-05 22:01:45 +10:00
teor
ef7838eab2
Prop 312: Relay Auto IPv6 Addreess - Initial Draft
Related tickets: 33073 (proposal), 5940 (implementation).
2020-02-05 22:01:25 +10:00
teor
5e79a7dd21
Prop 311: Allow for auto-configured IPv6 ORPorts
Part of 24404.
2020-02-05 21:52:58 +10:00
teor
f7fb789de4
Prop 311: Rewrite and re-order tor-spec changes
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.
2020-02-05 21:52:55 +10:00
teor
cdc5a152aa
Prop 311: Reformat references
Part of 24404.
2020-02-05 21:52:52 +10:00
teor
6eee2ca426
Prop 311: Avoid depending on exact extend details
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.
2020-02-05 21:52:49 +10:00
teor
14906a6fd9
Prop 311: Clarify "may not"
Part of 24404.
2020-02-05 21:52:46 +10:00
teor
8e85047b65
Prop 311: Improve Subprotocol Version
* 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.
2020-02-05 21:52:42 +10:00
teor
5c0aa29f81
Prop 311: Improve RelaySendIPv6Extends option name
As suggested by Nick Mathewson.

Part of 24404.
2020-02-05 21:52:39 +10:00
teor
a3e2f6cd61
Prop 311: Improve Extra Reachability Checks
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.
2020-02-05 21:52:36 +10:00
teor
27936d046e
Prop 311: Allow Extends to Prefer IPv4 or IPv6
Add an alternate design, suggested by Nick Mathewson.

Part of 24404.
2020-02-05 21:52:33 +10:00
teor
b6a75a8a14
Prop 311: Add IPv6 ORPort to Extend Conditions
As suggested by Nick Mathewson.

Part of 24404.
2020-02-05 21:52:30 +10:00
teor
9966ad3f3f
Prop 311: Support seamless upgrades
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.
2020-02-05 21:52:27 +10:00
teor
3c19e051a6
Prop 311: Make capitalisation consistent
Part of 24404.
2020-02-05 21:52:15 +10:00
teor
64745746f4
Prop 311: Make bridge mentions consistent
Part of 24404.
2020-02-05 21:52:09 +10:00
teor
7f8a655017
Prop 311: Fix a typo in section 5
Part of 24404.
2020-02-05 21:52:06 +10:00
teor
e5aa0b3411
Prop 311: Include heartbeat logs in monitoring
Some of the statistics may also be available in relay heartbeat logs.

Part of 24404.
2020-02-05 21:52:03 +10:00
teor
f67267bc53
Prop 311: Clarify prop 306 references
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.
2020-02-05 21:52:00 +10:00
teor
d175e08706
Prop 311: Add exception for recent tor changes
Some IPv6 behaviour has changed in recent tor versions, as noted in the
proposal.

Part of 24404.
2020-02-05 21:51:57 +10:00
teor
0348668dec
Prop 311: Explain Directory Authority behaviour
Where it's different from relay behaviour.

Part of ticket 24404.
2020-02-05 21:51:53 +10:00
teor
a65f689482
Prop 311: Use shorter file names for future proposals
And use short proposal names in references.

Part of 24404.
2020-02-05 21:51:22 +10:00
rl1987
1f4ae3d62f Clarify about empty GETCONF request 2020-02-03 16:56:53 +08:00
David Goulet
429dd3ab77 dir-spec: Vote should be refused after upload period
Spec change for ticket #4631.

Signed-off-by: David Goulet <dgoulet@torproject.org>
2020-01-29 16:58:57 -05:00
rl1987
f04179f254 Document that Tor accepts GETCONF with zero or more arguments 2020-01-29 14:59:43 +08:00
teor
d719ac4022
Prop 311: IPv6 ORPort Reachability - Initial Draft
Related tickets: 24404 (proposal), 24403 (implementation).
2020-01-24 16:13:01 +10:00
teor
8f094d7485
prop 309: Fix trailing space 2020-01-22 14:13:37 +10:00
Nick Mathewson
3882ddb3cf Merge remote-tracking branch 'tor-github/pr/101' 2020-01-16 16:46:08 -05:00
teor
e99deb888e
Merge remote-tracking branch 'tor-github/pr/99' 2020-01-16 00:14:40 +10:00
teor
ff165e0f44
Merge remote-tracking branch 'tor-github/pr/102' 2020-01-15 22:50:10 +10:00