From 3bc512cfe2ad26870407d1365028aa5d1c40a73a Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Thu, 27 Mar 2008 17:20:13 +0000 Subject: [PATCH] r19107@catbus: nickm | 2008-03-27 13:20:09 -0400 Fix typos in proposal 131 spotted by Jens Kubieziel on or-dev. svn:r14221 --- doc/spec/proposals/131-verify-tor-usage.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/spec/proposals/131-verify-tor-usage.txt b/doc/spec/proposals/131-verify-tor-usage.txt index bbc0b3634a..2687139189 100644 --- a/doc/spec/proposals/131-verify-tor-usage.txt +++ b/doc/spec/proposals/131-verify-tor-usage.txt @@ -125,14 +125,14 @@ Security and resiliency implications: What attacks are possible? - If the IP addressed used for this feature moves there will be two + If the IP address used for this feature moves there will be two consequences: - A new website at this IP address will remain inaccessible over Tor - Tor users who are leaking DNS will be informed that Tor is not working, rather than that it is active but leaking DNS We should thus attempt to find an IP address which we reasonably - belive can remain static. + believe can remain static. Open issues: