Opened 9 months ago

Closed 2 months ago

#24868 closed defect (wontfix)

Check a consensus parameter before activating onion service IPv6 features

Reported by: teor Owned by: teor
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop224, tor-hs, single-onion, ipv6, must-do-before-033-stable, 033-triage-20180320, 033-removed-20180320
Cc: Actual Points:
Parent ID: #26627 Points: 1
Reviewer: Sponsor:

Description

We've implemented #23577, but it looks like none of the other onion service IPv6 code will be ready for 0.3.3.

(We want to do the relay IPv6 code first.)

If we merge this in 0.3.3, then services will be able to distinguish 0.3.2 and 0.3.3 (and later) clients, when the rend point is dual-stack.

Do we want to add a torrc option / consensus parameter for v3 onion service IPv6? Or are we happy with this information leak?

Child Tickets

Change History (5)

comment:1 Changed 8 months ago by teor

Keywords: must-do-before-033-stable added
Owner: set to teor
Status: newassigned

nickm says this is a good idea. I will do it. But I would also be happy to review someone else's code if they want to do it.

comment:2 Changed 6 months ago by nickm

Keywords: 033-triage-20180320 added

Marking all tickets reached by current round of 033 triage.

comment:3 Changed 6 months ago by nickm

Keywords: 033-removed-20180320 added

Mark all not-already-included tickets as pending review for removal from 0.3.3 milestone.

comment:4 Changed 6 months ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: unspecified

These tickets were marked as removed, and nobody has said that they can fix them. Let's remember to look at 033-removed-20180320 as we re-evaluate our triage process, to see whether we're triaging out unnecessarily, and to evaluate whether we're deferring anything unnecessarily. But for now, we can't do these: we need to fix the 033-must stuff now.

comment:5 Changed 2 months ago by teor

Parent ID: #23493#26627
Resolution: wontfix
Status: assignedclosed

We didn't get this feature in 0.3.3, so introducing it now would make clients more fingerprintable.

Instead, we make 0.3.2 clients behave the same as 0.3.3 clients as a side effect of #26627.

Note: See TracTickets for help on using tickets.