SHA3-512SUM(1)

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

πŸ’… SHA3-512SUM(1) β€” like, the whole manual page, bestie

okay so this is sha3-512sum, straight out of the sha3sum package (yes, that's the manual name, we're being thorough πŸ’–). General Commands Manual energy. Periodt.


✨ NAME ✨

sha3-512sum β€” compute and check SHA3-512 message digests 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

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

🌸 DESCRIPTION 🌸

It prints or checks SHA3-512 checksums, no cap. If you give it no file at all, or if the file is literally -, it reads from standard input. iconic behavior honestly.

  • -u β€” output checksums in upper-case hexadecimal. loud and proud.
  • -l β€” output checksums in lower-case hexadecimal. this is the default, so you get it for free ✨
  • -b β€” output checksums in binary representation. heads up: this suppresses the filenames and checksum delimiters, so literally only the checksums get printed. no extra decoration.
  • -c β€” read SHA3-512 sums from the file and check them against the files on your system. the input files should be formatted like this program's output, or similar. ⚠️ real talk: 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 the -z option. consider yourself warned πŸ’€
  • -v β€” print the hashing parameters. transparency queen.
  • -x β€” convert input files from hexadecimal form to binary form before calculating the checksums.
  • -z β€” lines end with NUL instead of LF. if you use it with -c, this applies to the files being read (not the output), but it will also apply more strict parsing and allow any whitespace in file names. so, like, the glow-up for messy filenames 🌈

πŸŽ€ the hashing-parameter options, aka the spicy ones

the following options change the hashing parameters:

  • -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.

πŸ”₯ EXIT STATUS πŸ”₯

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

πŸ’œ AUTHORS πŸ’œ

Mattias AndrΓ©e <m@maandree.se> β€” the main character who wrote this.


πŸ“ NOTES πŸ“

all commands in the sha3sum package let you change the hashing parameters. however β€” and this is the important part β€” it's only intended to be used with keccaksum(1), or if you know what you are doing. the exception is -N, which is intended to always be used with shake128sum(1), shake256sum(1), shake512sum(1), rawshake128sum(1), rawshake256sum(1), and rawshake512sum(1). iykyk 🧚

fr fr don't go changing parameters just for the vibes unless you actually know what you're doing, bestie.

⭐ SEE ALSO-ish (the package roll call) ⭐

keccaksum(1), shake128sum(1), shake256sum(1), shake512sum(1), rawshake128sum(1), rawshake256sum(1), rawshake512sum(1) β€” all referenced above, all in the sha3sum family πŸ’…


okay that's the whole page, nothing skipped, nothing dropped 🫢 this came to you from the SHA3SUM source / SHA3-512SUM(1) page in the General Commands Manual β€” mwah, go hash something slay πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from