B2SUM(1)

๐Ÿ’… b2sum โ€” it's giving BLAKE2, bestie

okay so this is the b2sum page from the User Commands section of the GNU coreutils manual, and it's literally about computing and checking BLAKE2 message digests. Yes, that's the whole vibe. Let's go. ๐Ÿฆ‹


โœจ NAME โœจ

b2sum โ€” compute and check BLAKE2 message digest ๐Ÿ’–


๐ŸŒธ SYNOPSIS ๐ŸŒธ

b2sum [OPTION]... [FILE]...

๐ŸŽ€ DESCRIPTION ๐ŸŽ€

So what does it do? It prints or checks BLAKE2b (512-bit) checksums. That's it, that's the job. It's the legacy interface to the cksum(1) utility, iykyk. ๐Ÿ‘‘

If you give it no FILE at all, or if FILE is literally -, it reads from standard input. Classic.

Also, real talk: mandatory arguments to long options are mandatory for short options too. That's not a suggestion, that's the rules. ๐Ÿ™ˆ

๐Ÿซถ the options, babes

  • -b, --binary โ€” read in binary mode
  • -c, --check โ€” read checksums from the FILEs and check them
  • -l, --length=BITS โ€” digest length in bits; it must not exceed the max size, and it must be a multiple of 8 for blake2b; for sha2 or sha3 it must be 224, 256, 384, or 512
  • --tag โ€” create a BSD-style checksum
  • -t, --text โ€” read in text mode (this is the default, so it's the chill one)
  • -z, --zero โ€” end each output line with NUL, not newline, and disable file name escaping
  • --help โ€” display this help and exit
  • --version โ€” output version information and exit

๐Ÿ” the following five options are useful only when verifying checksums:

  • --ignore-missing โ€” don't fail or report status for missing files
  • --quiet โ€” don't print OK for each successfully verified file
  • --status โ€” don't output anything, status code shows success
  • --strict โ€” exit non-zero for improperly formatted checksum lines
  • -w, --warn โ€” warn about improperly formatted checksum lines

The sums are computed exactly as described in RFC 7693, no cap. ๐Ÿงš

When you're checking, the input should be a former output of this program โ€” like, it has to be your own past receipts, okay?

The default mode is to print a line with: the checksum, a space, a character indicating the input mode ('*' for binary, ' ' for text or where binary is insignificant), and the name for each FILE. That's the whole format. Slay. โœจ

There is no difference between binary mode and text mode on GNU systems. Periodt.

๐Ÿ‘‘ AUTHOR ๐Ÿ‘‘

Written by Padraig Brady and Samuel Neves. Icons, honestly.


๐Ÿ˜ญ REPORTING BUGS ๐Ÿ˜ญ


Copyright ยฉ 2026 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law. Fr fr, none. ๐Ÿ’€

๐ŸŒˆ SEE ALSO ๐ŸŒˆ

Full documentation <https://www.gnu.org/software/coreutils/b2sum> or available locally via: info '(coreutils) b2sum invocation'


and that's the whole page, bestie โ€” this one's from GNU coreutils 9.12, dated September 2026, so it's fresh out the box ๐ŸŽโœจ go check your checksums, you got this ๐Ÿ’…๐Ÿฆ‹

๐Ÿ“ฆ where this page comes from