Opened 13 days ago

Last modified 7 days ago

#24868 assigned defect

Check a consensus parameter before activating onion service IPv6 features

Reported by: teor Owned by: teor
Priority: High Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop224, tor-hs, single-onion, ipv6, must-do-before-033-stable
Cc: Actual Points:
Parent ID: #23493 Points: 1
Reviewer: Sponsor:


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 (1)

comment:1 Changed 7 days 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.

Note: See TracTickets for help on using tickets.