Opened 3 years ago

Closed 2 years ago

#19022 closed defect (wontfix)

Extract intro_nodes status tracking from rend_service_descriptor_t

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs, tor-client
Cc: teor Actual Points:
Parent ID: #19204 Points:
Reviewer: Sponsor: SponsorR-can


To make the rend_service_descriptor_t struct closer to immutatable, we should fix the behavior in validate_intro_point_failure() where we delete entries from desc->intro_nodes that are in the failure cache.

Maybe a good fix is to move the whole status tracking of the intro point fetches into the rend failure cache, rather than having some of the status tracking in each place.

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by arma

Parent ID: #19204

comment:2 Changed 3 years ago by teor

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

Milestone renamed

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

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:5 Changed 2 years ago by dgoulet

Keywords: tor-hs tor-client added
Resolution: wontfix
Status: newclosed

I seriously do not want to touch the legacy HS subsystem too much. Rest assure, prop224 code behaves very differently with different objects for the state.

Please re-open if you think we should really put time into that.

Note: See TracTickets for help on using tickets.