aboutsummaryrefslogtreecommitdiff
path: root/proposals/131-verify-tor-usage.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2008-03-27 17:20:13 +0000
committerNick Mathewson <nickm@torproject.org>2008-03-27 17:20:13 +0000
commit48182e5e22d88850fb351a862771db7768c2d23b (patch)
treeda9c3d8d5b694c990cdfb07748f4aad8a4df2bc7 /proposals/131-verify-tor-usage.txt
parent3fb3822318d4c5998ad93af3ae556c0eb2638663 (diff)
downloadtorspec-48182e5e22d88850fb351a862771db7768c2d23b.tar.gz
torspec-48182e5e22d88850fb351a862771db7768c2d23b.zip
r19107@catbus: nickm | 2008-03-27 13:20:09 -0400
Fix typos in proposal 131 spotted by Jens Kubieziel on or-dev. svn:r14221
Diffstat (limited to 'proposals/131-verify-tor-usage.txt')
-rw-r--r--proposals/131-verify-tor-usage.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/proposals/131-verify-tor-usage.txt b/proposals/131-verify-tor-usage.txt
index bbc0b36..2687139 100644
--- a/proposals/131-verify-tor-usage.txt
+++ b/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: