From: Tom Gundersen <teg@jklm.no>
Date: Thu, 23 Jul 2015 16:45:49 +0000 (+0200)
Subject: util: base32hex - explain distinction with base32
X-Git-Tag: v223~19^2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=75c0cab158e9da7f78ad040d23cd52720a025659;p=platform%2Fupstream%2Fsystemd.git

util: base32hex - explain distinction with base32
---

diff --git a/src/basic/util.c b/src/basic/util.c
index 7896be8..1c15fbc 100644
--- a/src/basic/util.c
+++ b/src/basic/util.c
@@ -954,7 +954,12 @@ int unhexmem(const char *p, size_t l, void **mem, size_t *len) {
         return 0;
 }
 
-/* https://tools.ietf.org/html/rfc4648#section-6 */
+/* https://tools.ietf.org/html/rfc4648#section-6
+ * Notice that base32hex differs from base32 in the alphabet it uses.
+ * The distinction is that the base32hex representation preserves the
+ * order of the underlying data when compared as bytestrings, this is
+ * useful when representing NSEC3 hashes, as one can then verify the
+ * order of hashes directly from their representation. */
 char base32hexchar(int x) {
         static const char table[32] = "0123456789"
                                       "ABCDEFGHIJKLMNOPQRSTUV";