aboutsummaryrefslogtreecommitdiff
path: root/proposals/115-two-hop-paths.txt
AgeCommit message (Collapse)Author
2009-05-05Remove all svn metadata minus what I missed.Sebastian Hahn
Tor doesn't use SVN anymore, making $Revision$, $Id$ and $Date$ meaningless. Remove them without replacement.
2008-04-10 r19289@catbus: nickm | 2008-04-10 00:36:10 -0400Nick Mathewson
Mark 110 as needs-revision; 113 as superseded; 115 and 116 as dead; 117 as needs-revision; 118 as draft. Add comment to end of 113 about status. svn:r14343
2007-06-06Fix some typos, clarify some minor semantics, change phases to reflectMike Perry
PathlenCoinWeight-style implementation (for fingerprinting resistance). svn:r10508
2007-06-05Attempt to address points brought up in #tor flamewar. In particular, movedMike Perry
"Who will enable this option?" section towards the top of the proposal, to attempt to get everyone on the same page right away as far as assumptions go. Also, added section on "Consideration of risks for node operators" where the additional risk of should-be-3-but-actually-2 hop users pose to node operators is discussed. Upon consideration of this, determined that two hop users should be made to rotate guards with some frequency on the order of days (basically, long enough to help scan the network for active adversary guards, and then move on). Please re-flame if you feel these or other issues have not been adequately addressed. svn:r10498
2007-06-03Think a little harder about guard nodes. What if they could be made to beMike Perry
reliable and not rotate as much for dialup, mobile, or transient network users, and what if users were actually notified more visibly who their guards were and came to trust the guard nodes they have? Some effects of this are considered. svn:r10470
2007-06-01Add Two Hop Paths proposal as 115. Mark 112 superseded by 115.Mike Perry
svn:r10435