aboutsummaryrefslogtreecommitdiff
path: root/proposals/203-https-frontend.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2012-08-13 16:11:46 -0400
committerRoger Dingledine <arma@torproject.org>2012-08-13 16:11:46 -0400
commit5ce6cbbb5f6b2e9f40ccecea0029c82e3fdea61c (patch)
tree8e0d0a50405372a46c569ec45a541be063b9270a /proposals/203-https-frontend.txt
parent79b1f8f47e7f47f7b9a2603a5aeead53404a1480 (diff)
downloadtorspec-5ce6cbbb5f6b2e9f40ccecea0029c82e3fdea61c.tar.gz
torspec-5ce6cbbb5f6b2e9f40ccecea0029c82e3fdea61c.zip
trivial fixes from earlier readings
Diffstat (limited to 'proposals/203-https-frontend.txt')
-rw-r--r--proposals/203-https-frontend.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/proposals/203-https-frontend.txt b/proposals/203-https-frontend.txt
index 8d3c2e3..26101b3 100644
--- a/proposals/203-https-frontend.txt
+++ b/proposals/203-https-frontend.txt
@@ -39,7 +39,7 @@ Goals and requirements:
HTTPS client talking to an HTTPS server.
We should make it impossible for an active attacker talking to the
- server to tell a Tor bridge server from regular HTTPS server.
+ server to tell a Tor bridge server from a regular HTTPS server.
We should make it impossible for an active attacker who can MITM the
server to learn from the client whether it thought it was connecting
@@ -205,7 +205,7 @@ Some considerations on distinguishability
entirely.)
Against an active non-MITM attacker, the best probing attacks will be
- ones designed to provoke the system in acting in ways different from
+ ones designed to provoke the system into acting in ways different from
those in which a webserver would act: responding earlier than a web
server would respond, or later, or differently. We need to make sure
that, whatever the front-end program is, it answers anything that