diff options
| author | Tom Gundersen <teg@jklm.no> | 2015-07-23 18:45:49 +0200 |
|---|---|---|
| committer | Tom Gundersen <teg@jklm.no> | 2015-07-27 20:34:47 +0200 |
| commit | 75c0cab158e9da7f78ad040d23cd52720a025659 (patch) | |
| tree | 01bb7d344a6639b53c6b75646f6c85d517732f36 | |
| parent | c73ee39d1031f8d7e01448bf1a9810943d7c6560 (diff) | |
| download | systemd-75c0cab158e9da7f78ad040d23cd52720a025659.tar.gz systemd-75c0cab158e9da7f78ad040d23cd52720a025659.tar.bz2 systemd-75c0cab158e9da7f78ad040d23cd52720a025659.zip | |
util: base32hex - explain distinction with base32
| -rw-r--r-- | src/basic/util.c | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/src/basic/util.c b/src/basic/util.c index 7896be8788..1c15fbc172 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"; |