[tor-bugs] #25754 [Core Tor/Tor]: Make Prop#291 choices

Tor Bug Tracker & Wiki blackhole at torproject.org
Mon Apr 9 19:35:07 UTC 2018


#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        |   Keywords:  034-roadmap-subtask
Actual Points:                |  Parent ID:  #25546
       Points:                |   Reviewer:
      Sponsor:  SponsorV-can  |
------------------------------+---------------------------------
 We should make some decisions about
 [https://gitweb.torproject.org/torspec.git/tree/proposals/291-two-guard-
 nodes.txt Proposal 291], since what we expect to do there influences how
 we want to handle vanguards and other things.

 The torspec.git proposal text is currently exactly the same as "Proposal:
 The move to two guard nodes" on the tor-dev mailinglist, in case people
 want to reply point-by-point.

 In particular, I wrote Section 3 with arma and Nick's points in mind, and
 section 2.4 with Isis's points in mind.

 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)
  3. Don't use Guard nodes as exits, RPs, HSDirs, or IPs. (Section 3.2)

 Tickets that are affected by our choice here include #25753, #24487, and
 #25705.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25754>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list