sha3_512(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so this is sha3_512(9), straight out of the Kernel API Manual β€” we're doing a whole cryptographic glow-up today and honestly? obsessed. 🫢


✨ NAME ✨

sha3_512 β€” my girl computes a SHA3-512 digest in one shot, no cap. 🎯


🌸 SYNOPSIS 🌸

void sha3_512 (const u8 *in , size_t in_len , u8
out[SHA3_512_DIGEST_SIZE] );

like literally that's the whole signature. she's compact. she's iconic. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • in β€” the input data that's getting digested, bestie. the main character of the operation. πŸ’–
  • in_len β€” the length of in, measured in bytes (size_t, so she's got range). πŸ“
  • out β€” the buffer where the digest gets stored. she's u8 out[SHA3_512_DIGEST_SIZE], so you already know exactly how much room she needs. ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

so this is a convenience function that computes a SHA3-512 digest. that's it, that's the vibe. 🌈

use sha3_512 instead of the incremental API if you're able to provide all the input at once β€” like if you've got the whole thing in hand already, why be extra about it? not every moment needs to be a multi-step process, fr fr. πŸ“


πŸ’œ CONTEXT πŸ’œ

Any context. 🧚 like genuinely, she doesn't gatekeep β€” any context is fine, do your thing, slay.


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./include/crypto/sha3.h, plus the whole friend group:


πŸ’€ pro tip from your girl: if you can't hand over all the input at once, don't force it β€” that's literally what the incremental API is for. read the room. πŸ™ˆ

⭐ and that's the page!! sources say she lives in ./include/crypto, dated October 2026, and she answers to sha3_512(9) β€” okay bye bestie, go hash something gorgeous πŸ’–πŸ”₯πŸ‘‘

πŸ“¦ where this page comes from