[tor-commits] [torspec/master] prop224: Clarify how checksum truncation works.

[asn@xxxxxxxxxxxxxx]

commit 717fa8a4560d876f0144d82914fc4fb4ce3e9c30
Author: George Kadianakis <desnacked@xxxxxxxxxx>
Date:   Wed Feb 1 14:36:48 2017 +0200

    prop224: Clarify how checksum truncation works.
---
 proposals/224-rend-spec-ng.txt | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt
index 6f71b32..69cd7c6 100644
--- a/proposals/224-rend-spec-ng.txt
+++ b/proposals/224-rend-spec-ng.txt
@@ -1875,7 +1875,7 @@ Table of contents:
    encoded as shown below:
 
      onion_address = base32(PUBKEY || CHECKSUM || VERSION) + ".onion"
-     CHECKSUM = H(".onion checksum" || PUBKEY || VERSION)
+     CHECKSUM = H(".onion checksum" || PUBKEY || VERSION)[:2]
 
      where:
        - PUBKEY is the 32 bytes ed25519 master pubkey of the hidden service.
@@ -1883,11 +1883,11 @@ Table of contents:
        - ".onion checksum" is a constant string
        - CHECKSUM is truncated to two bytes before inserting it in onion_address
 
-  Here are a few example addresses (with broken checksum):
+  Here are a few example addresses:
 
-       l5satjgud6gucryazcyvyvhuxhr74u6ygigiuyixe3a6ysis67ororad.onion
-       btojiu7nu5y5iwut64eufevogqdw4wmqzugnoluw232r4t3ecsfv37ad.onion
-       vckjr6bpchiahzhmtzslnl477hdfvwhzw7dmymz3s5lp64mwf6wfeqad.onion
+       pg6mmjiyjmcrsslvykfwnntlaru7p5svn6y2ymmju6nubxndf4pscryd.onion
+       sp3k262uwy4r2k3ycr5awluarykdpag6a7y33jxop4cs2lu5uz5sseqd.onion
+       xa4r2iadxm55fbnqgwwi5mymqdcofiu3w6rpbtqn7b2dyn7mgwj64jyd.onion
 
    For more information about this encoding, please see our discussion thread
    at [ONIONADDRESS-REFS].

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits