KECCAK-224SUM(1)

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

πŸ’… keccak-224sum β€” bestie edition ✨

okay so this is the keccak-224sum page from the General Commands Manual, and honestly? it's giving "tiny tool, big brain energy." she computes and checks Keccak-224 message digests and she does it flawlessly. no cap. 🫢


🌸 NAME 🌸

keccak-224sum β€” compute and check Keccak-224 message digests πŸ’–


✨ SYNOPSIS ✨

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

like yes, that's a lot of brackets, but stay with me bestie, we're gonna go through every single one. πŸ”₯


πŸŽ€ DESCRIPTION πŸŽ€

She prints or checks Keccak-224 checksums. that's the whole vibe. if you hand her no file at all, or if the file is literally -, she reads standard input instead. simple as that. πŸ¦‹

  • -u β€” output checksums in upper-case hexadecimal representation. LOUD hex. screaming hex. iconic. πŸ‘‘
  • -l β€” output checksums in lower-case hexadecimal representation. this is the default, so she's already doing it. lowercase rights. 🌸
  • -b β€” output checksums in binary representation. heads up though: this suppresses the filenames and the checksum delimiters, so literally only the checksums get printed. just the raw vibes, nothing else. πŸ’€
  • -c β€” read Keccak-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 something similarly shaped. ⚠️ important caveat: this is not going to work if any of the filenames in the input file start with a regular space or a horizontal tab, or if they contain a line feed, carriage return, or form feed β€” unless you also use -z. so yeah, watch out for that. πŸ™ˆ
  • -v β€” print the hashing parameters. she'll tell you what she's working with. transparency queen. 🧚
  • -x β€” convert input files from hexadecimal form to binary form before calculating the checksums. transformation moment. ✨
  • -z β€” lines end with NUL instead of LF. and if you use it with -c, it applies to the read files (not the output) β€” but it also kicks in more strict parsing and allows any whitespace in file names. so it's stricter AND more permissive at the same time, which is honestly such a mood. πŸ’…

🌈 the hashing-parameters options 🌈

these next ones change the actual hashing parameters. yes, you can just... do that. ⭐

  • -R rate β€” change the rate. ⚑
  • -C capacity β€” change the capacity. πŸ“
  • -N, -O output-size β€” change the output size. (-O is her lil alias, slay.) πŸ’–
  • -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. squeeze. 🧚

πŸ’€ EXIT STATUS πŸ’€

  • 0 β€” successful completion. we ate. πŸ”₯
  • 1 β€” checksums did not match, or a file did not exist. 😭 it happens bestie.
  • 2 β€” an error occurred. the other kind of bad. πŸ’€

🫢 AUTHORS 🫢

Mattias AndrΓ©e <m@maandree.se> β€” the mastermind, the main character. πŸ‘‘


⚠️ NOTES ⚠️

okay so real talk for a sec. 🫢

All commands in the sha3sum package allow changing the hashing parameters. however β€” and this is the important part β€” it is only intended to be used with keccaksum(1), or if you know what you are doing. like, actually know. not "I read half a blog post" know. πŸ’€

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). that one's the designated bestie of the shake family. 🌊✨


lowkey the takeaway is: default behaviour = chef's kiss, changing parameters = proceed with intention and good vibes only. πŸ’…

and that's the page!! mwah πŸ’– this lil manual comes to you courtesy of SHA3SUM, and the page itself is KECCAK-224SUM(1) β€” see you in the group chat, bestie. πŸŽ€πŸ¦‹βœ¨

πŸ“¦ where this page comes from