RAWSHAKE256SUM(1)

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

Hey bestie, welcome to the RAWSHAKE256SUM(1) page β€” it lives in the General Commands Manual, and we’re about to make message-digest checking feel like a group chat πŸ’…βœ¨

πŸ’– NAME πŸ’–

rawshake256sum β€” Compute and check RawSHAKE256 message digests 🫢

✨ SYNOPSIS ✨

The whole flex is:

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

πŸ¦‹ DESCRIPTION πŸ¦‹

Print or check RawSHAKE256 checksums. If no file is given, or when the file is -, read standard input. That’s the vibe 🌸.

πŸ’… The regular options, bestie πŸ’…

  • -u β€” Output checksums in upper-case hexadecimal representation. ALL CAPS energy πŸ”₯
  • -l β€” Output checksums in lower-case hexadecimal representation. This is the default, so it’s the main-character setting πŸ‘‘
  • -b β€” Output checksums in binary representation. This suppresses the filenames and checksum delimiters β€” only the checksums are printed. It’s giving β€œjust the bytes, no small talk” πŸ’€
  • -c β€” Read RawSHAKE256 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. 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 the -z option is also used. Consider this your lowercase warning, bestie 😭
  • -v β€” Print the hashing parameters. A little peek behind the curtain ✨
  • -x β€” Convert input files from hexadecimal form to binary form before calculating the checksums. Hex input gets converted before the checksum math, slay πŸ¦‹
  • -z β€” Lines end with NUL instead of LF. If used with -c, this applies to read files (not the output), but it will also apply more strict parsing and allow any whitespace in file names. NUL-terminated lines said β€œI contain multitudes” πŸ’…

The following options change the hashing parameters β€” yes, you can mess with the recipe πŸ”§:

  • -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. The vibe check failed πŸ’€
  • 2 β€” An error occurred. Something went sideways, no cap 😭

πŸŽ€ AUTHORS πŸŽ€

Mattias AndrΓ©e <m@maandree.se> β€” the icon behind this page 🫢

⭐ NOTES ⭐

All commands in the sha3sum package allow changing the hashing parameters. However it is only intended to be used with keccaksum(1), or if you know what you are doing; apart from -N which is intended to always be used with shake128sum(1), shake256sum(1), shake512sum(1), rawshake128sum(1), rawshake256sum(1), and rawshake512sum(1). That’s the whole footnote, periodt 🌈.


Cute sign-off: this page is from the source/version SHA3SUM and is titled RAWSHAKE256SUM(1); the date isn’t printed in the original footer, bestie πŸ«ΆπŸ’–

πŸ“¦ where this page comes from