SHA224SUM(1)

🌸 SHA224SUM(1) β€” User Commands 🌸

okay so bestie, we're in section 1 (User Commands) of the manual, and this one's about sha224sum. sit down, hydrate, and let's get into it πŸ’–


✨ NAME ✨

sha224sum β€” compute and check SHA224 message digest πŸ’…


✨ SYNOPSIS ✨

sha224sum [OPTION]... [FILE]...

✨ DESCRIPTION ✨

So what does it actually do? It prints or checks SHA224 (224-bit) checksums. That's the whole vibe. It's also the legacy interface to the cksum(1) utility, so like… it's the older sibling, still iconic, still showing up. πŸ‘‘

If you give it no FILE, or if FILE is literally -, it reads standard input. no file? no problem. 🫢

Here are the options, and yes, I'm listing every single one, no skipping:

  • -b, --binary β€” read in binary mode
  • -c, --check β€” read checksums from the *FILE*s and check them
  • --tag β€” create a BSD-style checksum
  • -t, --text β€” read in text mode (this is the default, so if you do nothing, you already did this πŸ’…)
  • -z, --zero β€” end each output line with NUL, not newline, and disable file name escaping

the next five? only useful when verifying checksums, so if you're not checking, these are just sitting there being pretty ✨

  • --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
  • --help β€” display this help and exit
  • --version β€” output version information and exit

The sums are computed as described in RFC 3874 β€” that's the receipt, bestie πŸ“œ. When checking, the input should be a former output of this program (like, it has to actually be output from this thing, don't just feed it anything and act surprised).

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

and here's the tea 🍡: there is no difference between binary mode and text mode on GNU systems. none. zero. the binary/text distinction is just out here vibing.

✨ AUTHOR ✨

Written by Ulrich Drepper, Scott Miller, and David Madore. legends, fr fr πŸ‘‘


✨ REPORTING BUGS ✨

Found a bug? Don't suffer in silence, bestie:


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. (like, none. zero. don't come for them 😭)

✨ SEE ALSO ✨

Full documentation https://www.gnu.org/software/coreutils/sha224sum β€” or available locally via: info '(coreutils) sha2 utilities'


and that's the whole page, bestie πŸŽ€ this was GNU coreutils 9.12, dated September 2026 β€” mwah, go checksum something πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from