Check a consensus parameter before activating onion service IPv6 features

We've implemented #23577 (moved), 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?

changed milestone to %Tor: unspecified

added 033-removed-20180320 033-triage-20180320 component::core tor/tor ipv6 milestone::Tor: unspecified must-do-before-033-stable owner::teor parent::26627 points::1 priority::high prop224 resolution::wontfix severity::normal single-onion status::closed tor-hs type::defect labels

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.

Trac:
Owner: N/A to teor
Status: new to assigned
Keywords: N/A deleted, must-do-before-033-stable added

Marking all tickets reached by current round of 033 triage.

Trac:
Keywords: N/A deleted, 033-triage-20180320 added

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

Trac:
Keywords: N/A deleted, 033-removed-20180320 added

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.

Trac:
Milestone: Tor: 0.3.3.x-final to Tor: unspecified

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 (moved).

Trac:
Parent: #23493 (moved) to #26627 (moved)
Resolution: N/A to wontfix
Status: assigned to closed

closed

changed time estimate to 8h

moved to tpo/core/tor#24868 (closed)