diff options
Diffstat (limited to 'spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md')
| -rw-r--r-- | spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md b/spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md index dce072c..707c7da 100644 --- a/spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md +++ b/spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md @@ -1,6 +1,6 @@ <a id="rend-spec-v3.txt-2.3"></a> -## Publishing shared random values [PUB-SHAREDRANDOM] +## Publishing shared random values \[PUB-SHAREDRANDOM\] Our design for limiting the predictability of HSDir upload locations relies on a shared random value (SRV) that isn't predictable in advance or @@ -8,7 +8,7 @@ too influenceable by an attacker. The authorities must run a protocol to generate such a value at least once per hsdir period. Here we describe how they publish these values; the procedure they use to generate them can change independently of the rest of this -specification. For more information see [SHAREDRANDOM-REFS]. +specification. For more information see \[SHAREDRANDOM-REFS\]. According to proposal 250, we add two new lines in consensuses: @@ -31,7 +31,7 @@ SRV = H("shared-random-disaster" | INT_8(period_length) | INT_8(period_num)) where period_length is the length of a time period in minutes, rounded down; period_num is calculated as specified in -[TIME-PERIODS] for the wanted shared random value that could not be +\[TIME-PERIODS\] for the wanted shared random value that could not be found originally. <a id="rend-spec-v3.txt-2.3.2"></a> |