SHAKE128SUM(1)

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

πŸ’… shake128sum(1) β€” the General Commands Manual girlie ✨

okay so bestie, welcome to shake128sum, a member of the General Commands Manual family, and she is here to compute and check SHAKE128 message digests. no cap, that's literally the whole job. 🫢


🌸 NAME 🌸

shake128sum β€” Compute and check SHAKE128 message digests πŸ’–


πŸŽ€ SYNOPSIS πŸŽ€

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

✨ DESCRIPTION ✨

So the vibe is: print or check SHAKE128 checksums. super simple. If you hand her no file at all, or if the file is -, she just reads standard input like the main character she is. πŸ‘‘

  • -u β€” Output checksums in upper-case hexadecimal representation. LOUD hex. uppercase slay. πŸ”₯
  • -l β€” Output checksums in lower-case hexadecimal representation. this is the default, so she's already doing it, bestie πŸ’œ
  • -b β€” Output checksums in binary representation. ⚠️ this one suppresses the filenames and the checksum delimiters β€” only the checksums get printed. raw bytes, no accessories. πŸ’€
  • -c β€” Read SHAKE128 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. 🧚 here's the catch though: 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. iykyk. πŸ™ˆ
  • -v β€” Print the hashing parameters. like, show me the receipts. ✨
  • -x β€” Convert input files from hexadecimal form to binary form before calculating the checksums. glow-up the input first πŸ’…
  • -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. πŸ¦‹

The following options change the hashing parameters β€” like, she lets you tweak the math, which is lowkey iconic:

  • -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 and left no crumbs πŸ’…
  • 1 β€” Checksums did not match or a file did not exist. 😭
  • 2 β€” An error occurred. πŸ’€

πŸ‘‘ AUTHORS πŸ‘‘

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


🌈 NOTES 🌈

okay important thing, listen up: all commands in the sha3sum package allow changing the hashing parameters. but 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). so like, don't just go changing parameters for fun unless you're that girl. πŸ§šβ€β™€οΈ


fr fr, this page came from the SHA3SUM source, and yeah, SHAKE128SUM(1) is the same manual we've been living in the whole time. πŸŽ€

bye bestie, go hash something gorgeous πŸ’–πŸŒΈβœ¨

πŸ“¦ where this page comes from