aboutsummaryrefslogtreecommitdiff
path: root/ext-orport-spec.txt
diff options
context:
space:
mode:
authorDimitris Apostolou <dimitris.apostolou@icloud.com>2021-10-25 23:03:20 +0300
committerNick Mathewson <nickm@torproject.org>2021-10-25 16:35:13 -0400
commit29245fd50d1ee3d96cca52154da4d888f34fedea (patch)
treee15e67dcf9ba6c6beb0d3681e1db5ea0de0b6e8b /ext-orport-spec.txt
parentc10dd31c0dcf970b8e199e029d56fc483f8a216c (diff)
downloadtorspec-29245fd50d1ee3d96cca52154da4d888f34fedea.tar.gz
torspec-29245fd50d1ee3d96cca52154da4d888f34fedea.zip
Fix typos and cleanup
Diffstat (limited to 'ext-orport-spec.txt')
-rw-r--r--ext-orport-spec.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/ext-orport-spec.txt b/ext-orport-spec.txt
index ec88244..6b8f8e1 100644
--- a/ext-orport-spec.txt
+++ b/ext-orport-spec.txt
@@ -63,14 +63,14 @@ Table of Contents
We define one authentication type: SAFE_COOKIE. Its AuthType
value is 1. It is based on the client proving to the bridge that
- it can access a given "cookie" file on disk. The purpose of
+ it can access a given "cookie" file on disk. The purpose of
authentication is to defend against cross-protocol attacks.
If the Extended ORPort is enabled, Tor should regenerate the cookie
file on startup and store it in
$DataDirectory/extended_orport_auth_cookie.
- The location of the cookie can be overriden by using the
+ The location of the cookie can be overridden by using the
configuration file parameter ExtORPortCookieAuthFile, which is
defined as:
@@ -139,7 +139,7 @@ Table of Contents
Status [1 octet]
Where,
- + Status is 1 if the authentication was successfull. If the
+ + Status is 1 if the authentication was successful. If the
authentication failed, Status is 0.
3. The extended ORPort protocol