sha3_384(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sha3_384(9) β€” Kernel API Manual, bestie edition

okay so this is a page from the Kernel API Manual and it's about sha3_384, which is literally the "do it all in one go" way to get a SHA3-384 digest πŸŽ€ no incantations, no state to babysit, just vibes and bytes.


✨ NAME ✨

sha3_384 β€” Compute SHA3-384 digest in one shot πŸ’«


🌸 SYNOPSIS 🌸

void sha3_384 (const u8 *in , size_t in_len , u8
out[SHA3_384_DIGEST_SIZE] );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • in β€” The input data to be digested πŸ“ like, the actual snack, the data itself
  • in_len β€” Length of the input data in bytes πŸ“ yes bestie, in bytes
  • out β€” The buffer into which the digest will be stored πŸ«™ it's gonna hold SHA3_384_DIGEST_SIZE worth of digest, that's the whole point

πŸ’– DESCRIPTION πŸ’–

A convenience function that computes a SHA3-384 digest ✨ That's it, that's the whole thing.

Use this instead of the incremental API if you're able to provide all the input at once πŸ‘‘ like, if you've already got the entire blob sitting there in in? then why would you do the incremental dance, this is the shortcut, take it πŸ’…


🌈 CONTEXT 🌈

Any context πŸ”₯ literally any. no restrictions, no special preconditions, go off.


πŸ‘‘ SEE ALSO πŸ‘‘

Bestie, the whole crypto sha3/shake friend group is here β€” go say hi:

ngl the incremental API is great and all, but if you've got every byte up front there is genuinely zero reason to suffer through init/update/final 😭 this one-shot function ate πŸ’€

okay that's the page!! mwah πŸ’œ this came from ./include/crypto, dated October 2026 β€” and yes the manual itself is sha3_384(9) up top, love that for us 🌸🫢 periodt ✨

πŸ“¦ where this page comes from