Opened 3 years ago

Closed 22 months ago

#18178 closed task (wontfix)

Prop#252: Single Onion Services: Extend to ORPort

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: sos
Cc: Actual Points:
Parent ID: Points: large
Reviewer: Sponsor:

Description (last modified by teor)

Top-level ticket for implementing Single Onion Services (SOS) from Proposal 252.

In Proposal 252, the client builds a 3-hop path and then extends to the ORPort of the SOS.

Child Tickets

Change History (8)

comment:1 Changed 3 years ago by teor

Description: modified (diff)

comment:2 Changed 3 years ago by dgoulet

Keywords: sos added
Points: large

comment:3 Changed 3 years ago by isabela

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

tickets market to be removed from milestone 029

comment:4 Changed 2 years ago by teor

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

Milestone renamed

comment:5 Changed 2 years 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:6 Changed 2 years ago by nickm

This can close, right? RSOS does what we want to do here, yeah?

comment:7 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:8 Changed 22 months ago by teor

Resolution: wontfix
Status: newclosed

We don't ever plan on implementing this.

Note: See TracTickets for help on using tickets.