From a3fd19302312d44257f175bded3551bc1397ced6 Mon Sep 17 00:00:00 2001 From: Hans-Christoph Steiner Date: Tue, 26 Nov 2019 20:58:54 +0100 Subject: fix erroneous header numbering punctuation The clear standard is trailing "." after each numeric section. This fixes the small handful of outliers. This makes it easy to convert these headers to common markup formats, for example: http://hyperpolyglot.org/lightweight-markup --- glossary.txt | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) (limited to 'glossary.txt') diff --git a/glossary.txt b/glossary.txt index 767080d..6debe20 100644 --- a/glossary.txt +++ b/glossary.txt @@ -18,18 +18,18 @@ citing them authoritatively. ;) "OPTIONAL" in this document are to be interpreted as described in RFC 2119. -1.0 Commonly used Tor configuration terms +1.0. Commonly used Tor configuration terms ORPort - Onion Router Port DirPort - Directory Port -2.0 Tor network components +2.0. Tor network components - 2.1 Relays, aka OR (onion router) +2.1. Relays, aka OR (onion router) [Style guide: prefer the term "Relay"] - 2.1.1 Specific roles +2.1.1. Specific roles Exit relay: The final hop in an exit circuit before traffic leaves the Tor network to connect to external servers. @@ -57,11 +57,11 @@ citing them authoritatively. ;) Each party builds a three-hop circuit, meeting at the rendezvous point. - 2.2 Client, aka OP (onion proxy) +2.2. Client, aka OP (onion proxy) [Style: the "OP" and "onion proxy" terms are deprecated.] - 2.3 Authorities: +2.3. Authorities: Directory Authority: Nine total in the Tor network, operated by trusted individuals. Directory authorities define and serve the @@ -79,7 +79,7 @@ citing them authoritatively. ;) the client can ask any directory cache that's listed in the directory information it has.) - 2.4 Hidden Service: +2.4. Hidden Service: A hidden service is a server that will only accept incoming connections via the hidden service protocol. Connection @@ -87,7 +87,7 @@ citing them authoritatively. ;) service, allowing the hidden service to receive incoming connections, serve content, etc, while preserving its location anonymity. - 2.5 Circuit: +2.5. Circuit: An established path through the network, where cryptographic keys are negotiated using the ntor protocol or TAP (Tor Authentication @@ -104,29 +104,29 @@ citing them authoritatively. ;) network. For example, a client could connect to a hidden service via an internal circuit. - 2.6 Edge connection: +2.6. Edge connection: - 2.7 Consensus: The state of the Tor network, published every hour, +2.7. Consensus: The state of the Tor network, published every hour, decided by a vote from the network's directory authorities. Clients fetch the consensus from directory authorities, fallback directories, or directory caches. - 2.8 Descriptor: Each descriptor represents information about one +2.8. Descriptor: Each descriptor represents information about one relay in the Tor network. The descriptor includes the relay's IP address, public keys, and other data. Relays send descriptors to directory authorities, who vote and publish a summary of them in the network consensus. -3.0 Tor network protocols +3.0. Tor network protocols - 3.1 Link handshake +3.1. Link handshake The link handshake establishes the TLS connection over which two Tor participants will send Tor cells. This handshake also authenticates the participants to each other, possibly using Tor cells. - 3.2 Circuit handshake +3.2. Circuit handshake Circuit handshakes establish the hop-by-hop onion encryption that clients use to tunnel their application traffic. The @@ -155,12 +155,12 @@ citing them authoritatively. ;) contains the first part of the TAP or ntor key establishment handshake. - 3.3 Hidden Service Protocol +3.3. Hidden Service Protocol - 3.4 Directory Protocol +3.4. Directory Protocol -4.0 General network definitions +4.0. General network definitions Leaky Pipe Topology: The ability for the origin of a circuit to address relay cells to be addressed to any hop in the path of a circuit. In Tor, -- cgit v1.2.3-54-g00ecf