Opened 7 years ago

Closed 3 years ago

#7173 closed project (fixed)

Analyze risks and benefits of clients having three guards

Reported by: karsten Owned by:
Priority: High Milestone: Tor: 0.2.9.x-final
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Normal Keywords: tor-client, SponsorZ, 027-triaged-1-in, tor-guard, tor-guards-revamp
Cc: arma Actual Points:
Parent ID: Points: 4.5
Reviewer: Sponsor: SponsorU-can

Description

(Re-using Roger's text here.)

Based on the WPES 2012 paper "Changing of the Guards: A Framework for Understanding and Improving Entry Guard Selection in Tor", write a Tor proposal to pick safer parameters for guard selection (pick fewer guards, rotate them less often, etc). Then help with the follow-up paper to start exploring whether there are better algorithms to assign the Guard flag (to improve safety and performance).

Child Tickets

Change History (14)

comment:1 Changed 7 years ago by nickm

Keywords: tor-client SponsorZ added
Milestone: Tor: unspecified
Priority: normalmajor

comment:2 Changed 4 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.2.7.x-final

Worth looking at during 0.2.7 triage IMO

comment:3 Changed 4 years ago by nickm

Status: newassigned

comment:4 Changed 4 years ago by nickm

Keywords: 027-triaged-1-in added

Marking some tickets as triaged-in for 0.2.7 based on early triage

comment:5 Changed 4 years ago by isabela

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

comment:6 Changed 4 years ago by nickm

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

comment:7 Changed 4 years ago by nickm

Keywords: SponsorU removed
Sponsor: SponsorU

Bulk-replace SponsorU keyword with SponsorU field.

comment:8 Changed 3 years ago by nickm

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

Turn most 0.2.8 "assigned" tickets with no owner into "new" tickets for 0.2.9. Disagree? Find somebody who can do it (maybe you?) and get them to take it on for 0.2.8. :)

comment:9 Changed 3 years ago by isabela

Sponsor: SponsorUSponsorU-must

comment:10 Changed 3 years ago by mikeperry

Severity: Normal
Sponsor: SponsorU-mustSponsorU-can

Working with Isabela today, we think this is actually a SponsorU-can rather than must. It looks like an alternate to the Proposal 259 set of work which will also satisfy SponsorU, and less well-scoped.

comment:11 Changed 3 years ago by mikeperry

Keywords: tor-guard added

comment:12 Changed 3 years ago by nickm

Keywords: tor-guards-revamp added

comment:13 Changed 3 years ago by isabela

Points: medium/large4.5

comment:14 Changed 3 years ago by asn

Resolution: fixed
Status: newclosed

I feel this ticket can be closed now. We are pretty sure that 1 guard is better than 3 guards for most use cases, and there have not been any strong counter arguments yet.

Proposal 236 specifies the change and most of it is already implemented.

Closing this. Feel free to reopen if you think something is missing.

Note: See TracTickets for help on using tickets.