aboutsummaryrefslogtreecommitdiff
path: root/bridgedb-spec.txt
diff options
context:
space:
mode:
Diffstat (limited to 'bridgedb-spec.txt')
-rw-r--r--bridgedb-spec.txt3
1 files changed, 3 insertions, 0 deletions
diff --git a/bridgedb-spec.txt b/bridgedb-spec.txt
index 89f850a..a4c4708 100644
--- a/bridgedb-spec.txt
+++ b/bridgedb-spec.txt
@@ -209,6 +209,7 @@
the requirements. This ring is then used to select bridges as described.
"Mapping X to Y based on an HMAC" above means one of the following:
+
- We keep all of the elements of Y in some order, with a mapping
from all 160-bit strings to positions in Y.
- We take an HMAC of X using some fixed string as a key to get a
@@ -219,6 +220,7 @@
BridgeDB may be configured to "Give out at least L bridges with port
443, and at least M bridges with Stable, and at most N bridges
total." To do this, BridgeDB combines to the results:
+
- The first L bridges in the ring after the position that have the
port 443, and
- The first M bridges in the ring after the position that have the
@@ -299,6 +301,7 @@
To map previously unseen email addresses to a set of bridges, BridgeDB
proceeds as follows:
+
- It normalizes the email address as above, by stripping out dots,
removing all of the localpart after the +, and putting it all
in lowercase. (Example: "John.Doe+bridges@example.COM" becomes