Opened 12 months ago

Last modified 3 months ago

#25753 assigned defect

Check/enforce path restrictions for each path position

Reported by: mikeperry Owned by: mikeperry
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 034-roadmap-subtask, tor-guard, guard-discovery, 034-deferred-20180602, 035-removed-20180711
Cc: Actual Points:
Parent ID: #25546 Points: 20
Reviewer: Sponsor: SponsorV-can

Description

For the vanguard torrc options, we may want to check that each layer has at least one node from a different /16 and different node family than others in that layer, to ensure that a path can always be built using the vanguard set.

We may also want to do the same thing for Tor's Primary Guard set from Prop271, to ensure that an adversary can't force the user to pick guards randomly from Sampled Guards.

Doing both of these things at once should allow us to drop #24487.

See also: https://gitweb.torproject.org/torspec.git/tree/proposals/291-two-guard-nodes.txt#n33

Child Tickets

Change History (5)

comment:1 Changed 12 months ago by catalyst

Keywords: tor-guard guard-discovery added
Milestone: Tor: 0.3.4.x-final
Sponsor: SponsorV-can

comment:2 Changed 11 months ago by dgoulet

Owner: set to mikeperry
Status: newassigned

Assigning Owner to lead this. Feel free to change it but lets avoid having it empty.

comment:3 Changed 11 months ago by nickm

Keywords: 034-deferred-20180602 added
Milestone: Tor: 0.3.4.x-finalTor: 0.3.5.x-final

Deferring non-must tickets to 0.3.5

comment:4 Changed 9 months ago by nickm

Keywords: 035-removed-20180711 added
Milestone: Tor: 0.3.5.x-finalTor: unspecified

These tickets are being triaged out of 0.3.5. The ones marked "035-roadmap-proposed" may return.

comment:5 Changed 3 months ago by mikeperry

Points: 20
Note: See TracTickets for help on using tickets.