diff options
| -rw-r--r-- | bridgedb-spec.txt | 4 | ||||
| -rw-r--r-- | path-spec.txt | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/bridgedb-spec.txt b/bridgedb-spec.txt index c897226..89f850a 100644 --- a/bridgedb-spec.txt +++ b/bridgedb-spec.txt @@ -231,11 +231,11 @@ are fulfilled as possible within the first few bridges. This list is then truncated to N bridges, if possible. N is currently defined as a piecewise function of the number of bridges in the ring such that: - + / | 1, if len(ring) < 20 | - N = | 2, if 20 <= len(ring) <= 100 + N = | 2, if 20 <= len(ring) <= 100 | | 3, if 100 <= len(ring) \ diff --git a/path-spec.txt b/path-spec.txt index a79a4d6..82f07cd 100644 --- a/path-spec.txt +++ b/path-spec.txt @@ -672,7 +672,7 @@ of their choices. threat model. It also allows targeted attacks aimed at monitoring the activity of specific users, bridges, or Guard nodes. - There are two points where path selection can be manipulated: + There are two points where path selection can be manipulated: during construction, and during usage. Circuit construction can be manipulated by inducing circuit failures during circuit extend steps, which causes the Tor client to transparently retry |