#25754: Make Prop#291 choices -------------------------------------------------+------------------------- Reporter: mikeperry | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: Tor: | 0.3.4.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: 034-roadmap-subtask, tor-guard, | Actual Points: guard-discovery | Parent ID: #25546 | Points: Reviewer: | Sponsor: | SponsorV-can -------------------------------------------------+-------------------------
Comment (by asn): Replying to [ticket:25754 mikeperry]: > > At a high level, the choices are: > 0. Do nothing. (If we choose this, I want us to do it for specific reasons, rather than default to it). > 1. Use two guards, and ensure one is from a different /16 and node family (Section 1.1 and 1.2). > 2. Abandon all of Tor's path restrictions (Section 3.1) This '''"all of Tor's path restrictions"''' phrasing is scary. First of all, we only need to relax the path restrictions on HS-related circuits right (particularly HSDir, IP and RP circs)? And in particular we need to relax the single restriction of disallowing guard and final hop being the same node (or in the same family or /16). No other path restrictions should be edited IIUC. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25754#comment:3> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs