From 6f378100e597074a639a04bad849e81dce36140c Mon Sep 17 00:00:00 2001 From: Jim Newsome Date: Wed, 8 Nov 2023 16:31:33 -0600 Subject: Fix broken links --- proposals/340-packed-and-fragmented.md | 2 +- spec/bandwidth-file-spec/implementation-details.md | 2 +- spec/path-spec/path-selection-constraints.md | 4 ++-- spec/rend-spec/managing-streams.md | 2 +- spec/tor-spec/flow-control.md | 2 +- spec/tor-spec/negotiating-channels.md | 2 +- spec/tor-spec/subprotocol-versioning.md | 2 +- 7 files changed, 8 insertions(+), 8 deletions(-) diff --git a/proposals/340-packed-and-fragmented.md b/proposals/340-packed-and-fragmented.md index 74af5ca..82adb8e 100644 --- a/proposals/340-packed-and-fragmented.md +++ b/proposals/340-packed-and-fragmented.md @@ -31,7 +31,7 @@ This proposal combines ideas from [proposal 319](./319-wide-everything.md) (fragmentation) and [proposal 325](./325-packed-relay-cells.md) (packed cells). It requires [ntor v3](./332-ntor-v3-with-extra-data.md) and prepares for -[next-generation relay cryptography](./308-counter-galois-onion). +[next-generation relay cryptography](./308-counter-galois-onion.md). Additionally, this proposal has been revised to incorporate another protocol change, and move StreamId from the relay cell header into a new, diff --git a/spec/bandwidth-file-spec/implementation-details.md b/spec/bandwidth-file-spec/implementation-details.md index 08fac19..dbc02cc 100644 --- a/spec/bandwidth-file-spec/implementation-details.md +++ b/spec/bandwidth-file-spec/implementation-details.md @@ -393,6 +393,6 @@ References: The Torflow specification is outdated, and does not match the current implementation. See section A.1. for the format produced by Torflow. 3. [The Tor Directory Protocol](../dir-spec) -4. [How Tor Version Numbers Work In Tor](../version-spec) +4. [How Tor Version Numbers Work In Tor](../version-spec.md) 5. ``` diff --git a/spec/path-spec/path-selection-constraints.md b/spec/path-spec/path-selection-constraints.md index 7905466..8cac4fc 100644 --- a/spec/path-spec/path-selection-constraints.md +++ b/spec/path-spec/path-selection-constraints.md @@ -26,7 +26,7 @@ constraints: (C Tor overrides this with `EnforceDistinctSubnets`; Arti overrides this with `ipv[46]_subnet_family_prefix`.) - The first node must be a Guard (see - discussion [below](./guard-nodes) and in the + discussion [below](./guard-nodes.md) and in the [guard specification](../guard-spec)). - XXXX Choosing the length @@ -64,7 +64,7 @@ position they are being selected for. These weights are published in the consensus, and are computed as described in -["Computing Bandwidth Weights"](../dir-spec/computing-consensus#computing-bandwidth-weights) +["Computing Bandwidth Weights"](../dir-spec/computing-consensus.md#computing-bandwidth-weights) in the directory specification. They are: diff --git a/spec/rend-spec/managing-streams.md b/spec/rend-spec/managing-streams.md index 56f6f51..a32a352 100644 --- a/spec/rend-spec/managing-streams.md +++ b/spec/rend-spec/managing-streams.md @@ -14,7 +14,7 @@ and not set any flags on the begin message. > on port 443, a client would send a BEGIN message with > the address:port string of `":443"`, and a `FLAGS` value of 0. > The 0-values `FLAGS` would not be encoded, according to -> the instructions for [encoding BEGIN messages](../tor-spec/opening/streams#opening). +> the instructions for [encoding BEGIN messages](../tor-spec/opening-streams.md#opening). ## Receiving BEGIN messages { #receive-begin } diff --git a/spec/tor-spec/flow-control.md b/spec/tor-spec/flow-control.md index bf1abe2..91c04e3 100644 --- a/spec/tor-spec/flow-control.md +++ b/spec/tor-spec/flow-control.md @@ -33,7 +33,7 @@ information. See proposal 111 for details. Link padding can be created by sending PADDING or VPADDING cells along the connection; relay cells of type "DROP" can be used for long-range padding. The payloads of PADDING, VPADDING, or DROP -cells are filled with padding bytes. See [Cell Packet format](./cell-packet-format#cell-packet-format). +cells are filled with padding bytes. See [Cell Packet format](./cell-packet-format.md#cell-packet-format). If the link protocol is version 5 or higher, link level padding is enabled as per padding-spec.txt. On these connections, clients may diff --git a/spec/tor-spec/negotiating-channels.md b/spec/tor-spec/negotiating-channels.md index 2501d7f..948a1f3 100644 --- a/spec/tor-spec/negotiating-channels.md +++ b/spec/tor-spec/negotiating-channels.md @@ -145,7 +145,7 @@ Relevant certType values are: | 7 | Ed25519 identity, signed with RSA identity. The certificate format for certificate types 1-3 is DER encoded X509. -For others, the format is as documented in [a later section](./cert-spec.md) +For others, the format is as documented in [a later section](../cert-spec.md) Note that type 7 uses a different format from types 4-6. diff --git a/spec/tor-spec/subprotocol-versioning.md b/spec/tor-spec/subprotocol-versioning.md index 97c4409..780a337 100644 --- a/spec/tor-spec/subprotocol-versioning.md +++ b/spec/tor-spec/subprotocol-versioning.md @@ -295,7 +295,7 @@ Describes the communications mechanisms used to bundle circuits together, in order to split traffic across multiple paths. > TODO: This is not yet described here. For details see -> [Proposal 329](../proposals/329). +> [Proposal 329](../proposals/329-traffic-splitting.txt). -- cgit v1.2.3-54-g00ecf