Opened 5 years ago

Last modified 2 years ago

#14921 new defect

Investigate whether we sometimes remove all predicted ports at startup

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Normal Keywords: needs-investigation tor-client predicted-ports
Cc: Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor: SponsorU-can

Description

If we have no good exits when we call choose_good_exit_server_general(), it appears we will remove all the predicted ports immediately. Can this happen?

Hypothesized while investigating #14918

Child Tickets

Change History (20)

comment:1 Changed 5 years ago by nickm

We introduced the relevant logic in 0888c2f8f550 as a fix for #3296.

comment:2 Changed 4 years ago by nickm

Status: newassigned

comment:3 Changed 4 years ago by nickm

Keywords: 027-triaged-1-in added

Marking more tickets as triaged-in for 0.2.7

comment:4 Changed 4 years ago by isabela

Keywords: SponsorU added
Points: medium
Version: Tor: 0.2.7

comment:5 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:6 Changed 4 years ago by nickm

Keywords: SponsorU removed
Sponsor: SponsorU

Bulk-replace SponsorU keyword with SponsorU field.

comment:7 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final

These seem like features, or like other stuff unlikely to be possible this month. Bumping them to 0.2.9

comment:8 Changed 3 years ago by nickm

Sponsor: SponsorUSponsorU-can

comment:9 Changed 3 years ago by nickm

Keywords: tor-sponsorU-orphan added

comment:10 Changed 3 years ago by isabela

Points: medium3

comment:11 Changed 3 years ago by nickm

Status: assignednew

Put all unowned "assigned" tickets back into "new".

comment:12 Changed 3 years ago by isabela

Keywords: isaremoved added
Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

comment:13 Changed 3 years ago by teor

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

Milestone renamed

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

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:16 Changed 2 years ago by nickm

Keywords: 027-triaged-in added

comment:17 Changed 2 years ago by nickm

Keywords: 027-triaged-in removed

comment:18 Changed 2 years ago by nickm

Keywords: 027-triaged-1-in removed

comment:19 Changed 2 years ago by nickm

Keywords: isaremoved removed

comment:20 Changed 2 years ago by nickm

Keywords: needs-investigation tor-client predicted-ports added; tor-sponsorU-orphan removed
Severity: Normal
Note: See TracTickets for help on using tickets.