This is an automated email from the git hooks/post-receive script.
nickm pushed a commit to branch main in repository torspec.
The following commit(s) were added to refs/heads/main by this push: new 09d74ee Fix typos 09d74ee is described below
commit 09d74eec67044e87dbc709430cd32c629281a227 Author: Georg Koppen gk@torproject.org AuthorDate: Tue Jul 12 09:53:42 2022 +0000
Fix typos
Closes: #164 --- proposals/264-subprotocol-versions.txt | 6 ++---- proposals/326-tor-relay-well-known-uri-rfc8615.md | 4 ++-- 2 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/proposals/264-subprotocol-versions.txt b/proposals/264-subprotocol-versions.txt index 75a1c8f..bd58125 100644 --- a/proposals/264-subprotocol-versions.txt +++ b/proposals/264-subprotocol-versions.txt @@ -151,9 +151,7 @@ Implemented-In: 0.2.9.4-alpha versions we expect to continue supporting.]]
These lines should be voted on. A majority of votes is sufficient to - make a protocol un-supported. - - and should require a supermajority of + make a protocol un-supported and it should require a supermajority of authorities (2/3) to make a protocol required. The required protocols should not be torrc-configurable, but rather should be hardwired in the Tor code. @@ -301,7 +299,7 @@ Implemented-In: 0.2.9.4-alpha
Adding new protocol types is pretty cheap, given compression.
-A.1. Inferring missing proto lines. +A.1. Inferring missing proto lines
The directory authorities no longer allow versions of Tor before 0.2.4.18-rc. But right now, there is no version of Tor in the diff --git a/proposals/326-tor-relay-well-known-uri-rfc8615.md b/proposals/326-tor-relay-well-known-uri-rfc8615.md index 2f820ea..7648162 100644 --- a/proposals/326-tor-relay-well-known-uri-rfc8615.md +++ b/proposals/326-tor-relay-well-known-uri-rfc8615.md @@ -1,6 +1,6 @@ ``` Filename: 326-tor-relay-well-known-uri-rfc8615.md -Title: The "tor-relay" Well-Known Resource Identifier +Title: The "tor-relay" Well-Known Resource Identifier Author: nusenu Created: 14 August 2020 Status: Open @@ -23,7 +23,7 @@ organization by pointing to its website: Tor relay/bridge contact information fi under the specified URI, because attackers can not easily place these files at the given location.
* By publishing Tor relay IDs or hashed bridge IDs under this URI the website operator claims to be the responsible entity for these Tor relays/bridges. -The verification of listed Tor relay/bridge IDs only succeeds if the claim can be verified bidirectionally +The verification of listed Tor relay/bridge IDs only succeeds if the claim can be verified bidirectionally (website -> relay/bridge and relay/bridge -> website).
* This URI is not related to Tor onion services.