Opened 11 months ago

Last modified 3 months ago

#23300 assigned defect

prop224: General client side issues

Reported by: dgoulet Owned by: dgoulet
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs, prop224, 034-triage-20180328, 034-removed-20180328
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor: SponsorR-must

Description

This is a parent ticket for a series of client side issues that have been identified during the review of #17242 and that we felt it would be better to fix in a separate ticket because some include changes to the HS v2 subsystem.

Child Tickets

TicketStatusOwnerSummaryComponent
#3733accepteddgouletTor should abandon rendezvous circuits that cause a client request to time outCore Tor/Tor
#17520newRelax the rend cache failure cleanup timerCore Tor/Tor
#20371newLower HSDir query backoff delayCore Tor/Tor
#23019closedprop224: Validate received onion addresses on the client sideCore Tor/Tor
#23130closedprop224: Synchronize spec with implementation (August 2017)Core Tor/Tor
#23301assigneddgouletprop224: Refactor connection_ap_handle_onionCore Tor/Tor
#23303closeddgouleths: Explain why we reset the directory connection timestamp client sideCore Tor/Tor
#23304closeddgouletprop224: Dump a malformed descriptor in a file and log_warn about itCore Tor/Tor
#23306assigneddgouleths: Use the state of a directory connection instead of the HAS_FETCHED purposeCore Tor/Tor
#23307assigneddgouleths: Don't bruteforce every pending connection when we get a RENDEZVOUS ackCore Tor/Tor
#23308closeddgouletprop224: Implement note_connection_attempt_succeeded() in the client codeCore Tor/Tor
#23310closedtest: prop224 client unit testsCore Tor/Tor
#23327closedprop224: client-side memleaks on the last hidserv request subsystemCore Tor/Tor
#23328closedprop224: Uninitialized hsdir indices if requesting onion before bootstrap completesCore Tor/Tor
#23355closeddgouletprop224: Implement a client purge state for NEWNYMCore Tor/Tor

Change History (6)

comment:1 Changed 10 months ago by dgoulet

Milestone: Tor: 0.3.2.x-finalTor: 0.3.3.x-final

Two of them are for 032 so far but the rest has been postponed so no need to keep the parent ticket in 032.

comment:2 Changed 6 months ago by dgoulet

Priority: HighMedium

comment:3 Changed 5 months ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

By the same reasoning, no need to keep this in 0.3.3: most of these are now 0.3.4 issues.

comment:4 Changed 4 months ago by nickm

Keywords: 034-triage-20180328 added

comment:5 Changed 4 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:6 Changed 3 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

Note: See TracTickets for help on using tickets.