Allow controllers to post HS descriptors to Tor's cache

changed milestone to %Tor: unspecified

added component::core tor/tor kludge-enabler milestone::Tor: unspecified points::1 priority::low severity::normal status::new tor-control tor-hs tor-spec type::enhancement labels

Trac:
Type: defect to enhancement

This would allow a hidden service's client to receive the service's descriptor through some mechanism other than Tor's hidden service directory system.

What's the intended application? Or is this just a "somebody might want this someday" kind of thing?

Replying to nickm:

What's the intended application? Or is this just a "somebody might want this someday" kind of thing?

I wish I could have this as a backup method of obtaining the descriptors for my remote-access hidden services while travelling this summer.

Trac:
Milestone: Tor: 0.2.3.x-final to Tor: unspecified

Trac:
Keywords: N/A deleted, needs-proposal added

Trac:
Keywords: needs-proposal deleted, needs-proposal tor-hs added

Trac:
Component: Tor Hidden Services to Tor

Trac:
Parent: N/A to #8993 (moved)

Worth looking at during 0.2.7 triage IMO

Trac:
Milestone: Tor: unspecified to Tor: 0.2.7.x-final

Trac:
Status: new to assigned
Owner: rransom to N/A

Marking some tickets as triaged-in for 0.2.7 based on early triage

Trac:
Keywords: needs-proposal tor-hs deleted, needs-proposal, 027-triaged-1-in, tor-hs added

Trac:
Version: N/A to Tor: 0.2.7
Keywords: N/A deleted, SponsorR, SponsorS added
Points: N/A to small

Trac:
Milestone: Tor: 0.2.7.x-final to Tor: 0.2.8.x-final

Bulk-replace SponsorR keyword with SponsorR sponsor field in Tor component.

Trac:
Keywords: SponsorR deleted, N/A added
Sponsor: N/A to SponsorR

Trac:
Keywords: 027-triaged-1-in deleted, N/A added

Trac:
Keywords: SponsorS deleted, N/A added

Trac:
Priority: Medium to Low
Severity: N/A to Normal
Milestone: Tor: 0.2.8.x-final to Tor: 0.2.???