aboutsummaryrefslogtreecommitdiff
path: root/proposals/291-two-guard-nodes.txt
diff options
context:
space:
mode:
Diffstat (limited to 'proposals/291-two-guard-nodes.txt')
-rw-r--r--proposals/291-two-guard-nodes.txt6
1 files changed, 4 insertions, 2 deletions
diff --git a/proposals/291-two-guard-nodes.txt b/proposals/291-two-guard-nodes.txt
index 43885e3..9b89eae 100644
--- a/proposals/291-two-guard-nodes.txt
+++ b/proposals/291-two-guard-nodes.txt
@@ -1,9 +1,10 @@
+```
Filename: 291-two-guard-nodes.txt
Title: The move to two guard nodes
Author: Mike Perry
Created: 2018-03-22
Supersedes: Proposal 236
-Status: Needs-Revision
+Status: Finished
0. Background
@@ -154,7 +155,7 @@ Status: Needs-Revision
However, while removing path restrictions will solve the immediate
problem, it will not address other instances where Tor temporarily opts
- use a second guard due to congestion, OOM, or failure of its primary
+ to use a second guard due to congestion, OOM, or failure of its primary
guard, and we're still running into bugs where this can be adversarially
controlled or just happen randomly[5].
@@ -254,3 +255,4 @@ References:
12. https://trac.torproject.org/projects/tor/ticket/10969
13. https://www.freehaven.net/anonbib/cache/wpes12-cogs.pdf
14. https://gitweb.torproject.org/torspec.git/tree/proposals/247-hs-guard-discovery.txt
+```