Skip to content
Snippets Groups Projects
Closed (moved) Make Prop#291 ("Move to two guard nodes") choices
  • View options
  • Make Prop#291 ("Move to two guard nodes") choices

  • View options
  • Closed (moved) Issue created by Mike Perry

    We should make some decisions about 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 legacy/trac#25753 (moved), legacy/trac#24487 (moved), and legacy/trac#25705 (moved).

    Edited by Nick Mathewson

    Linked items ... 0

  • Activity

    • All activity
    • Comments only
    • History only
    • Newest first
    • Oldest first
    Loading Loading Loading Loading Loading Loading Loading Loading Loading Loading