Opened 6 years ago

Last modified 17 months ago

#6418 new enhancement

Drop support for older versions of the hidden service protocol

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs technical-debt deprecation
Cc: teor Actual Points:
Parent ID: Points:
Reviewer: Sponsor: SponsorR-can

Description

We've supported v3 introduce{1,2} cells since 0.2.1.

We've supported v2 descriptors since 0.2.0.

There is no need for clients and servers to continue supporting older versions of the hidden service protocols; there is probably no need for "hidden service authorities" to exist; and there is probably a bunch of other code here we can discard too.

The one wrinkle to think about is that removing support here _might_ enable an adversary to tell when a client or service has switched to a newer version of Tor. Generally, we don't care about that, but we should still think about it.

Child Tickets

TicketTypeStatusOwnerSummary
#15621enhancementaccepteddgouletKill the pre-version 3 intro protocol code with fire.

Change History (19)

comment:1 Changed 6 years ago by nickm

Keywords: tor-hs added

comment:2 Changed 6 years ago by nickm

Component: Tor Hidden ServicesTor

comment:3 Changed 6 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

comment:4 Changed 5 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.6.x-final

Since dropping server-side support here would make a way to distinguish old vs new servers, it probably makes sense to do this stuff as part of our bigger hidden service revision efforts.

comment:5 Changed 4 years ago by nickm

Keywords: 026-triaged-1 added
Parent ID: #12424

comment:6 Changed 4 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.7.x-final

These are important, but they're almost certainly not going to get done by January.

comment:7 Changed 4 years ago by nickm

Status: newassigned

comment:8 Changed 4 years ago by nickm

Keywords: 027-triaged-1-out added

Marking triaged-out items from first round of 0.2.7 triage.

comment:9 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.???

Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???

comment:10 Changed 3 years ago by teor

Cc: teor added

comment:11 Changed 3 years ago by dgoulet

Keywords: 026-triaged-1 027-triaged-1-out removed
Sponsor: SponsorR
Type: projectenhancement

comment:12 Changed 3 years ago by dgoulet

Milestone: Tor: 0.2.???Tor: 0.2.9.x-final
Parent ID: #12424
Points: small
Severity: Normal
Sponsor: SponsorRSponsorR-can

This will basically be fixed by merging the child ticket to putting this one in 029.

comment:13 Changed 2 years ago by isabela

Points: small1

comment:14 Changed 2 years ago by dgoulet

Milestone: Tor: 0.2.9.x-finalTor: 0.2.???
Points: 1

comment:15 Changed 2 years ago by teor

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

Milestone renamed

comment:16 Changed 22 months 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:17 Changed 17 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:18 Changed 17 months ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:19 Changed 17 months ago by nickm

Keywords: technical-debt deprecation added
Note: See TracTickets for help on using tickets.