Opened 4 years ago

Closed 2 years ago

#17849 closed enhancement (fixed)

Warn if single-stack IPv4/IPv6 clients have very restricted guard choices

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6, easy, prop259, tor-guard, isaremoved, tor-03-unspecified-201612
Cc: Actual Points: 0
Parent ID: #17811 Points: 3
Reviewer: Sponsor:

Description (last modified by teor)

Yawning: The futueproof thing would be to warn if the selected protocol limits the number of guards to < N% probably?
Using what a dual stack host can reach as the baseline.

Child Tickets

Change History (13)

comment:1 Changed 4 years ago by teor

Description: modified (diff)

It's worth noting that the code to allow IPv6 guards was introduced in a previous tor version.

comment:2 Changed 4 years ago by teor

We don't currently warn if FascistFirewall is set, even though that restricts guard choices.

If we do implement this, the warning should apply to:

  • IPv6-only clients
  • Clients that set any of the ReachableAddresses options
  • Clients that set any of the ExcludeNodes or Nodes options (???)
  • IPv4-only clients (for future-proofing)

It could be easier to implement this after #9068 is done.

comment:3 Changed 4 years ago by teor

We can use the current proportion of relays on IPv4 ORPort 443 / DirPort 80 as a guide - these relays are accessible from clients with FascistFirewall set.

comment:4 Changed 3 years ago by teor

Keywords: easy added

I think we can defer this, because IPv6 client support is experimental, and requires explicit user action to enable. But I'd happily review a patch for it, or write one if I had the time.

It will be easy to write a patch for this once #17840 is merged.

comment:5 Changed 3 years ago by nickm

Points: medium

comment:6 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final

Throw most 0.2.8 "NEW" tickets into 0.2.9. I expect that many of them will subsequently get triaged out.

comment:7 Changed 3 years ago by nickm

Keywords: prop259 added

These are also prop259-related

comment:8 Changed 3 years ago by mikeperry

Keywords: tor-guard added

comment:9 Changed 3 years ago by isabela

Points: medium3

comment:10 Changed 3 years ago by isabela

Keywords: isaremoved added
Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

comment:11 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:12 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:13 Changed 2 years ago by teor

Actual Points: 0
Milestone: Tor: unspecifiedTor: 0.3.0.x-final
Resolution: fixed
Status: newclosed

This was implemented as part of proposal 217 in #19877.

Note: See TracTickets for help on using tickets.