Opened 4 years ago

Last modified 14 months ago

#21423 new defect

Refactor choose_good_entry_server based on different usecases

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: guards, refactor, triaged-out-20170308, technical-debt tor-client
Cc: Actual Points:
Parent ID: #20822 Points: 1
Reviewer: Sponsor:


The choose_good_entry_server function was used in four ways: picking out guards for the old (pre-prop271) guard algorithm; picking out guards for circuits; picking out guards for testing circuits on non-bridgees; picking out entries when entry guards are disabled. These options should be disentangled.

Child Tickets

Change History (7)

comment:1 Changed 4 years ago by nickm

Parent ID: #20822

comment:2 Changed 3 years ago by nickm

Points: 1

comment:3 Changed 3 years ago by nickm

Keywords: triaged-out-20170308 added
Milestone: Tor: 0.3.1.x-finalTor: unspecified

Deferring all 0.3.1 tickets with status == new, owner == nobody, sponsor == nobody, points > 0.5, and priority < high.

I'd still take patches for most of these -- there's just nobody currently lined up to work on them in this timeframe.

comment:4 Changed 3 years ago by nickm

Keywords: technical-debt tor-client added

comment:5 Changed 3 years ago by nickm

Sponsor: SponsorV-can

comment:6 Changed 14 months ago by gaba

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

comment:7 Changed 14 months ago by gaba

Sponsor: SponsorV-can

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Note: See TracTickets for help on using tickets.