B2SUM(1)

πŸ“¦
version 9.10 Β· 5 versions
, in ubuntu stonking

πŸ’– B2SUM(1) πŸ’–

okay bestie, welcome to b2sum β€” she's a User Command in the GNU coreutils fam and she computes AND checks BLAKE2 message digests. her whole personality is "hashing things, but make it certified". let's get into it ✨


✨ NAME ✨

b2sum β€” compute and check BLAKE2 message digest πŸ¦‹


🌸 SYNOPSIS 🌸

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

πŸ‘‘ DESCRIPTION πŸ‘‘

So what she actually DOES: prints or checks BLAKE2b (512-bit) checksums. she's the legacy interface to the cksum utility, which β€” iykyk β€” means she's been around and she's still that girl. πŸ’…

If you give her no FILE, or if FILE is literally just -, she reads standard input. stdin girlies rise up πŸ™ˆ

okay and a big one, truly no cap: mandatory arguments to long options are mandatory for short options too. like the rule is the rule, both ways, periodt.

  • -b, --binary β€” reads in binary mode πŸ’€
  • -c, --check β€” reads checksums out of the FILEs and, like, checks them ✨
  • -l, --length=BITS β€” this is the digest length in bits. heads up bestie, it must not exceed the max size, and it must be a multiple of 8 for blake2b; and for sha2 or sha3 it must be 224, 256, 384, or 512. so no freestyling with the numbers okay πŸŽ€
  • --tag β€” makes a BSD-style checksum, very chic
  • -t, --text β€” reads in text mode, which is the default btw 🌈
  • -z, --zero β€” every output line ends with a NUL instead of a newline, AND it disables file name escaping. that second part is lowkey important, don't skip it 🫢

πŸ”₯ the five options that are literally only useful when you're verifying checksums πŸ”₯

bestie these are the verification-only girlies, they do NOTHING unless you're checking πŸ‘‘

  • --ignore-missing β€” doesn't fail and doesn't report status for files that are missing. she's unbothered πŸ’…
  • --quiet β€” doesn't print OK for every single file that verified successfully. for when the success spam is too much 😭
  • --status β€” outputs absolutely nothing. the status code is the whole entire story. silence is the vibe πŸ”‡
  • --strict β€” exits non-zero for checksum lines that are improperly formatted. she's strict because she loves you πŸŽ€
  • -w, --warn β€” warns you about improperly formatted checksum lines, like a good friend would πŸ¦‹
  • --help β€” displays this help and exits ⭐
  • --version β€” outputs version information and exits πŸ‘‘

the sums get computed exactly as described in RFC 7693, no notes. πŸ“œ

when you're checking, the input should be a former output of this program β€” like, she's checking her own receipts, it's a self-care thing.

and the default mode prints a line with: the checksum, then a space, then a character that indicates the input mode (* for binary, ' ' for text or where binary is insignificant), then the name, for each FILE.

also, real talk: there is no difference between binary mode and text mode on GNU systems. so if you were stressed about picking β€” on GNU, you can just chill 🌈


πŸŽ€ AUTHOR πŸŽ€

Written by Padraig Brady and Samuel Neves. icons only, we stan πŸ‘‘


πŸ’œ REPORTING BUGS πŸ’œ

found a bug? not to be dramatic but tell someone:


πŸ¦‹ SEE ALSO πŸ¦‹

Packaged by Ubuntu (9.10-1ubuntu2)

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.


and that's the whole page bestie πŸ’– this one's from GNU coreutils 9.10, dated August 2026 β€” go hash something and feel gorgeous doing it. slay, stay checksummed, periodt. πŸ‘‘βœ¨

πŸ“¦ where this page comes from