SHA3-224SUM(1)

πŸ“¦
version 1.2.5 Β· 2 versions
, in arch rolling

πŸ’… SHA3-224SUM(1) β€” the general commands manual, but make it cute

okay so this is sha3-224sum(1), from the SHA3SUM manual set β€” a general commands manual page, bestie, and it's literally about computing and checking SHA3-224 message digests. stay with me, it's good, i promise 🫢


✨ NAME ✨

sha3-224sum β€” compute and check SHA3-224 message digests. that's it, that's the vibe πŸ’–


🌸 SYNOPSIS 🌸

sha3-224sum [-u | -l | -b | -c] [-R rate] [-C capacity] [-N output-size]
[-S state-size] [-W word-size] [-Z squeeze-count] [-vxz] [file ...]

copy it exactly, don't @ me πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

so the whole point: it prints SHA3-224 checksums, or checks them for you. if you pass no file at all β€” or you pass - as the file β€” it reads standard input. iconic behaviour, no notes πŸ‘‘

πŸŽ€ the output/behaviour flags

  • -u β€” output checksums in upper-case hexadecimal. shouty hex, we love her.
  • -l β€” output checksums in lower-case hexadecimal. this one is the default, so it's the main character by design ✨
  • -b β€” output checksums in binary representation. heads up though: this suppresses the filenames and the checksum delimiters, so literally only the checksums get printed. no names, no separator, just vibes πŸ’€
  • -c β€” read SHA3-224 sums from the file and check them against the files on your system. the input files should be formatted as the output of this program, or similarly (close enough counts). ⚠️ and here's the caveat, bestie, listen: this is not going to work if any of the filenames in the input file start with a regular space or horizontal tab, or if they contain a line feed, carriage return, or form feed β€” unless you also use -z. so yeah, use -z.
  • -v β€” print the hashing parameters. like a little receipt of your settings 🧾
  • -x β€” convert input files from hexadecimal form to binary form before calculating the checksums. glow-up transformation, honestly πŸ¦‹
  • -z β€” lines end with NUL instead of LF. and if you use it with -c, that applies to the read files (not the output) β€” but it also turns on more strict parsing and lets any whitespace be allowed in file names. chef's kiss, fr fr πŸ™ˆ

πŸ’œ the hashing-parameter flags (yes, you can change them)

  • -R rate β€” change the rate. 🌊
  • -C capacity β€” change the capacity. πŸ«™
  • -N, -O output-size β€” change the output size. πŸ“
  • -S, -B state-size β€” change the state size. 🧠
  • -W word-size β€” change the word size. πŸ”€
  • -Z squeeze-count β€” change the number of squeezes that is performed. πŸ‹ (i had to, sorry, but that's exactly what it says)

πŸ”₯ EXIT STATUS πŸ”₯

  • 0 β€” successful completion. slay πŸ’…
  • 1 β€” checksums did not match, or a file did not exist. 😭
  • 2 β€” an error occurred. πŸ’€

πŸ‘‘ AUTHORS πŸ‘‘

Mattias AndrΓ©e <m@maandree.se> β€” the icon who made this. bow 🫢


🌈 NOTES 🌈

okay so important tea: all commands in the sha3sum package allow changing the hashing parameters. the way that's a lot of power, bestie. but it is only intended to be used with keccaksum(1) β€” or if you actually know what you are doing. 🧚

there's one exception though: -N is intended to always be used with shake128sum(1), shake256sum(1), shake512sum(1), rawshake128sum(1), rawshake256sum(1), and rawshake512sum(1). all six, periodt.


⭐ sign-off ⭐

that's the whole page, bestie β€” it's from the SHA3SUM set, and you're reading SHA3-224SUM(1). go hash something and think of me πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«Ά

πŸ“¦ where this page comes from