[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[or-cvs] Fix base32 implementation; make base32 implementation follo...



Update of /home/or/cvsroot/doc
In directory moria.mit.edu:/tmp/cvs-serv20865/doc

Modified Files:
	rend-spec.txt 
Log Message:
Fix base32 implementation; make base32 implementation follow standard; add more tests for base32

Index: rend-spec.txt
===================================================================
RCS file: /home/or/cvsroot/doc/rend-spec.txt,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- rend-spec.txt	8 Apr 2004 02:07:53 -0000	1.15
+++ rend-spec.txt	8 Apr 2004 20:56:32 -0000	1.16
@@ -183,10 +183,8 @@
          1. Let H = H(PK).
          2. Let H' = the first 80 bits of H, considering each octet from
             most significant bit to least significant bit.
-         2. Generate a 16-character encoding of H', taking H' 5 bits at
-            a time, and mapping each 5-bit value to a character as follows:
-               0..25 map to the characters 'a'...'z', respectively.
-              26..31 map to the characters '0'...'5', respectively.
+         2. Generate a 16-character encoding of H', using base32 as defined
+            in RFC 3548.
 
    (We only use 80 bits instead of the 160 bits from SHA1 because we don't
    need to worry about man-in-the-middle attacks, and because it will make