commit 3bdbe6c9f290603c51c9b6700df5473f5c8b9073 Author: David Goulet dgoulet@torproject.org Date: Tue Aug 29 12:08:25 2017 -0400

prop224: Fix ordering of the hsdir_index construction

Turns out that it was implemented with period_num first and then period_length.

Like asn said, let us consider that as an interesting engineering artifact and change the spec instead of the code that has been tested like that for a while now.

Signed-off-by: David Goulet dgoulet@torproject.org --- proposals/224-rend-spec-ng.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt index dda7eb2..8ee5cdd 100644 --- a/proposals/224-rend-spec-ng.txt +++ b/proposals/224-rend-spec-ng.txt @@ -797,8 +797,8 @@ Table of contents:

hsdir_index(node) = H("node-idx" | node_identity | shared_random_value | - INT_8(period_length) | - INT_8(period_num) ) + INT_8(period_num) | + INT_8(period_length) )

where shared_random_value is the shared value generated by the authorities in section [PUB-SHAREDRANDOM], and node_identity is the ed25519 identity