Prop#252: Single Onion Services: Extend to ORPort

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.

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified points::large priority::medium resolution::wontfix severity::normal sos status::closed type::task labels

Trac:
Description: Top-level ticket for implementing Single Onion Services (SOS) from Proposal #252 (moved).

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

to

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.

Trac:
Reviewer: N/A to N/A
Keywords: N/A deleted, sos added
Points: N/A to large

tickets market to be removed from milestone 029

Trac:
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

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

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

We don't ever plan on implementing this.

Trac:
Status: new to closed
Resolution: N/A to wontfix

closed

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