#19642: Add a descriptor line for Single Onion Services -------------------------------------------------+------------------------- Reporter: teor | Owner: dgoulet Type: enhancement | Status: | needs_revision Priority: Medium | Milestone: Tor: | 0.3.0.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: tor-hs, rsos, sos, 030-proposed, | Actual Points: prop224, TorCoreTeam201609 | Parent ID: #17238 | Points: 0.5 Reviewer: | Sponsor: | SponsorR-can -------------------------------------------------+------------------------- Changes (by teor):
* status: needs_information => needs_revision Comment: Whatever we call it, here's what I think it means: The service is a single onion service. It may make direct connections to introduction and rendezvous points. Clients should make 3-hop connections to introduction and rendezvous points, to avoid having their connections blocked by upcoming relay defenses against one-hop hidden service proxies. I am happy to use single-onion-service, as I think it's unlikely we'll implement prop 252-style services (services that extend to an ORPort), and if we do, they will have their own link specifier type and semantics, distinct from single onion services as now implemented. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19642#comment:17> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs