Opened 3 years ago

Closed 5 months ago

#23079 closed project (wontfix)

Support 80-bit Onion Model In Perpetuity

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


As has been outlined by various persons on IRC, the email lists, onion services and even clearnet blogs, over the recent years ever since prop224 came to be proposed...

The current 80-bit model of onion addressing needs to be continued in perpetuity[1] as a legacy compatibility mode of onion addressing.

This mode has proven critical to users and communities in onionland that use OnionCat, OnionVPN, and other tools to achieve various communication models and application support, including interoperation with other networks, that is highly relavant to them.

It is expressly understood by this userbase that this legacy, perhaps even parallel, mode of operation will entail tradeoffs to prop224, including potentially enhanced anonymity risks, among other risks, and that code and bug support may be delayed vs prop224, and that those and other tradeoffs and issues are deemed acceptable to the legacy community.

[1] Or at least until a formal bi-directional resolution layer / registry / DHT or other mechanism is developed for prop224 (or any subsequent addressing proposal), for which in part, at least a deterministic 40+80 = resultant 128-bit IPV6 network stack interface compatible mode of operation is available that can supply what OnionCat/OnionVPN do today.

Child Tickets

Change History (7)

comment:1 Changed 3 years ago by cypherpunks


comment:2 Changed 3 years ago by nickm

Milestone: Tor: unspecified
Priority: Very HighMedium
Severity: BlockerNormal

We have no immediate plans to stop legacy hidden services from working. We also do not promise to maintain them forever.

comment:3 Changed 3 years ago by dgoulet

Component: Core TorCore Tor/Tor
Keywords: tor-hs added

As nickm stated, it will be a while before legacy onion service stop working.

But, chances are VERY SLIM to maintain it forever.

comment:4 Changed 3 years ago by cypherpunks

saw this on one of the forums, adding my voice since i use it to get onto the ipv6 net. i wouldn't mind if i had to explicitly enable the v2 client option via torrc, or load it via a compiled module, but would mind if it went away completely, at least until an ipv6 interface can be done with v3. that way, if it's a concern, vanilla users will only see and use the standard v3 client. obviously the v2 hsdir subsystem must still run by default. thanks for your consideration.

comment:5 Changed 14 months ago by Horusheru

Anybody here

comment:6 Changed 14 months ago by teor

Have you seen the instructions for using v3 onion services with OnionCat?

comment:7 Changed 5 months ago by nickm

Resolution: wontfix
Status: newclosed

(As noted, this is not something we plan to do.)

Note: See TracTickets for help on using tickets.