Opened 2 months ago

Last modified 27 hours ago

#26369 new defect

Re-fetch onion service descriptor for isolated request

Reported by: sysrqb Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs, tor-client, 035-roadmap-proposed, tbb-needs
Cc: gk, mahrud, dmr Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When tor receives a new request for connecting to an onion service and this request has different isolation flags/parameters than a previous (recent) request, then tor should re-fetch the service descriptor (if we already have it). Currently, tor notices it already has the descriptor in its cache and it doesn't refetch. This is a nice performance optimization, but if a client is requesting an isolated circuit for an onion service, then we shouldn't leak that we already have the descriptor in our cache.

Instead of only using the onion service name as the map-key, we can add a unique value of the circuit isolation information (hash?).

Child Tickets

Change History (6)

comment:1 Changed 2 months ago by gk

Cc: gk added

comment:2 Changed 6 weeks ago by teor

Component: Core TorCore Tor/Tor
Keywords: tbb-wants 035-proposed tor-hs tor-client added
Milestone: Tor: unspecified

comment:3 Changed 6 weeks ago by arma

Cc: mahrud added

comment:4 Changed 5 weeks ago by nickm

Keywords: 035-roadmap-proposed added; 035-proposed removed

comment:5 Changed 4 weeks ago by teor

Keywords: tbb-needs added; tbb-wants removed

Prefer the more common tbb-needs to tbb-wants.
There doesn't appear to be any difference in how much TBB needs based on the flag.

comment:6 Changed 27 hours ago by dmr

Cc: dmr added
Note: See TracTickets for help on using tickets.