aboutsummaryrefslogtreecommitdiffstats
path: root/b256sum.1
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--b256sum.122
1 files changed, 21 insertions, 1 deletions
diff --git a/b256sum.1 b/b256sum.1
index 4a1fa89..f0a3c18 100644
--- a/b256sum.1
+++ b/b256sum.1
@@ -3,7 +3,7 @@
b256sum - Compute and check BLAKE-256 message digests
.SH SYNOPSIS
.B b256sum
-[-c | -B | -L | -U] [-xz]
+[-c | -B | -L | -U] [-S salt] [-xz]
.RI [ file "] ..."
.SH DESCRIPTION
Print or check BLAKE-256 checksums.
@@ -34,6 +34,26 @@ option is also used.
.B -L
Output checksums in lower-case hexadecimal representation. (Default)
.TP
+.BI "-S " salt
+Specify a 16-byte salt that the BLAKE-256 algorithm shall use.
+This salt shall be expressed in full length hexadecimal: 32
+hexadecimal digits, or rather 16 pairs of hexadecimal digits,
+ordered from left to right to specify the values from index 0
+to the last byte. In each pair, the left digit stores the high
+bits of the byte, and the right digit stores the low bits of
+the byte. For example, the digit pair
+.B 80
+represents a byte with the decimal value 128, whereas the
+digit pair
+.B 08
+represents a byte with the decimal value 8. The pairs
+are joined without any delimiters, and no byte may be
+omitted. So, for a salt where each byte's value is its
+index, the salt is expressed as,
+.BR 000102030405060708090a0b0c0d0e0f ,
+however each letter may be either small or capital.
+If no salt is specified, an all-zeroes salt is used.
+.TP
.B -U
Output checksums in upper-case hexadecimal representation.
.TP