aboutsummaryrefslogtreecommitdiff
path: root/spec/path-spec/old-notes.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/old-notes.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/old-notes.md')
-rw-r--r--spec/path-spec/old-notes.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/spec/path-spec/old-notes.md b/spec/path-spec/old-notes.md
index ce3ec44..495a69a 100644
--- a/spec/path-spec/old-notes.md
+++ b/spec/path-spec/old-notes.md
@@ -4,9 +4,10 @@
<a id="path-spec.txt-X.1"></a>
-## Do we actually do this?
+## Do we actually do this? {#is-this-real}
```text
+
How to deal with network down.
- While all helpers are down/unreachable and there are no established
or on-the-way testing circuits, launch a testing circuit. (Do this
@@ -31,7 +32,7 @@ remove it. -NM\]
<a id="path-spec.txt-X.2"></a>
-## A thing we could do to deal with reachability
+## A thing we could do to deal with reachability {#a-thing}
And as a bonus, it leads to an answer to Nick's attack ("If I pick
my helper nodes all on 18.0.0.0:\*, then I move, you'll know where I
@@ -43,7 +44,7 @@ Is that smart or just complex?
<a id="path-spec.txt-X.3"></a>
-## Some stuff that worries me about entry guards. 2006 Jun, Nickm
+## Some stuff that worries me about entry guards. 2006 Jun, Nickm {#worries}
It is unlikely for two users to have the same set of entry guards.
Observing a user is sufficient to learn its entry guards. So, as we move