aboutsummaryrefslogtreecommitdiff
path: root/spec/path-spec/detecting-route-manipulation.md
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2023-10-14 18:52:20 -0400
committerNick Mathewson <nickm@torproject.org>2023-10-14 18:53:18 -0400
commit3457b0720834c8347d8318c1080ebc9486d77300 (patch)
treeb486a3d03fdfae7d98c4e6cf510179cf907c443f /spec/path-spec/detecting-route-manipulation.md
parenta331e9f48790ad4beaba1ee443c5ad8b13d3afb4 (diff)
downloadtorspec-3457b0720834c8347d8318c1080ebc9486d77300.tar.gz
torspec-3457b0720834c8347d8318c1080ebc9486d77300.zip
Add short IDs for most long section names
I've left off sections that are headings for their whole document.
Diffstat (limited to 'spec/path-spec/detecting-route-manipulation.md')
-rw-r--r--spec/path-spec/detecting-route-manipulation.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/spec/path-spec/detecting-route-manipulation.md b/spec/path-spec/detecting-route-manipulation.md
index c7ff50c..48cf4f7 100644
--- a/spec/path-spec/detecting-route-manipulation.md
+++ b/spec/path-spec/detecting-route-manipulation.md
@@ -1,6 +1,6 @@
<a id="path-spec.txt-7"></a>
-# Detecting route manipulation by Guard nodes (Path Bias)
+# Detecting route manipulation by Guard nodes (Path Bias) {#pathbias}
The Path Bias defense is designed to defend against a type of route
capture where malicious Guard nodes deliberately fail or choke circuits
@@ -35,7 +35,7 @@ section 7.5).
<a id="path-spec.txt-7.1"></a>
-## Measuring path construction success rates
+## Measuring path construction success rates {#construction-success-rate}
Clients maintain two counts for each of their guards: a count of the
number of times a circuit was extended to at least two hops through that
@@ -52,7 +52,7 @@ requested to close by the client, this is counted as a failure.
<a id="path-spec.txt-7.2"></a>
-## Measuring path usage success rates
+## Measuring path usage success rates {#usage-success-rate}
Clients maintain two usage counts for each of their guards: a count
of the number of usage attempts, and a count of the number of
@@ -88,7 +88,7 @@ failures.
<a id="path-spec.txt-7.3"></a>
-## Scaling success counts
+## Scaling success counts {#scaling}
To provide a moving average of recent Guard activity while
still preserving the ability to verify correctness, we periodically
@@ -104,7 +104,7 @@ scaling, and added back after scaling.
<a id="path-spec.txt-7.4"></a>
-## Parametrization
+## Parametrization {#parameters}
The following consensus parameters tune various aspects of the
defense.
@@ -189,7 +189,7 @@ defense.
<a id="path-spec.txt-7.5"></a>
-## Known barriers to enforcement
+## Known barriers to enforcement {#barriers}
Due to intermittent CPU overload at relays, the normal rate of
successful circuit completion is highly variable. The Guard-dropping