Commit Graph

3 Commits

Author SHA1 Message Date
Mike Perry
6ad4c8a376 Attempt to address points brought up in #tor flamewar. In particular, moved
"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-05 07:44:52 +00:00
Mike Perry
2b054774a5 Think a little harder about guard nodes. What if they could be made to be
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-03 19:41:51 +00:00
Mike Perry
1f4e93ce56 Add Two Hop Paths proposal as 115. Mark 112 superseded by 115.
svn:r10435
2007-06-01 04:41:51 +00:00