Opened 3 years ago

Closed 10 months ago

#19664 closed enhancement (wontfix)

IPv6-only Tor2web should use a 3-hop path on unreachable or failed intro or rend

Reported by: teor Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs, tor2web
Cc: Actual Points:
Parent ID: #26367 Points: 1
Reviewer: Sponsor:

Description (last modified by teor)

Just like single onion services, tor2web should use a 3-hop path if the intro or rend point is unreachable (using ReachableAddresses), or retry a 3-hop path if the connection fails.

This is more robust than placing requirements on hidden service intro point selection.

Was:
IPv6-only Tor2web: Hidden services should choose an IPv6-capable intro point
This enables IPv6-only Tor2web instances, at the cost of putting slightly more load on dual-stack relays.

(If 25% of relays are dual-stack, the chance that no relays out of 6 will be dual-stack is about 10%. So this is only a small increase in load.)

Child Tickets

Change History (7)

comment:1 Changed 3 years ago by dgoulet

Keywords: prop224 removed
Priority: MediumLow

As we don't plan to implement Tor2Web in prop224, I'm removing the keyword and tor-hs will be good enough to find back this ticket if we ever want it in v3 protocol (prop224).

comment:2 Changed 3 years ago by teor

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

Milestone renamed

comment:3 Changed 3 years ago by teor

Description: modified (diff)
Summary: IPv6-only Tor2web: Hidden services should choose an IPv6-capable intro pointIPv6-only Tor2web should use a 3-hop path on unreachable or failed intro or rend
Type: defectenhancement

It's better to fix this by using 3-hop paths.

Last edited 3 years ago by teor (previous) (diff)

comment:4 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:5 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:6 Changed 11 months ago by teor

Parent ID: #26367

This ticket can close as "wontfix" when we merge #26367.

comment:7 Changed 10 months ago by nickm

Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.