mirrors/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2025-02-23 14:40:51 +01:00
Code Issues Projects Releases Wiki Activity

a few tweaks, plus actually close 107

Browse source 
svn:r9794
This commit is contained in:
Roger Dingledine 2007-03-10 08:13:34 +00:00
parent abd1ca188e
commit 146b1e919f
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/spec/proposals/107-uptime-sanity-checking.txt
View file

@ -4,12 +4,12 @@ Version:
Last-Modified:
Author: Kevin Bauer & Damon McCoy
Created: 8-March-2007
Status: Open
Status: Closed
Overview:
This document describes how to cap the uptime that is used when computing
which routers are maked as stable such that highly stable routers cannot
which routers are marked as stable such that highly stable routers cannot
be displaced by malicious routers that report extremely high uptime
values.
@ -33,7 +33,7 @@ Specification:
"Stable" -- A router is 'Stable' if it is running, valid, not
hibernating, and either its uptime is at least the median uptime for
known running, valid, non-hibernating routers, or its uptime is at
least one month. Routers are never called stable if they are running
least 30 days. Routers are never called stable if they are running
a version of Tor known to drop circuits stupidly. (0.1.1.10-alpha
through 0.1.1.16-rc are stupid this way.)
@ -47,8 +47,9 @@ Implementation:
Discussion:
Initially, this proposal set the maximum at 50 days, not 30; the 30 day
Initially, this proposal set the maximum at 60 days, not 30; the 30 day
limit and spec wording was suggested by Roger in an or-dev post on 9 March
2007.
This proposal also led to 108-mtbf-based-stability.txt