sha384_final(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sha384_final(9) β€” like, the grand finale of your SHA-384 hash πŸŽ€

okay so real talk, bestie: this is a page from the Kernel API Manual, section 9, and it's all about sha384_final β€” the little function that wraps up your SHA-384 digest and then minds its own business by wiping the evidence. iconic behavior honestly ✨


🌸 NAME 🌸

sha384_final β€” finish computing a SHA-384 message digest πŸ¦‹


✨ SYNOPSIS ✨

void sha384_final (struct sha384_ctx *ctx , u8 out[static
SHA384_DIGEST_SIZE] );

no like, that's literally it. two args, one void, zero drama πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • ctx β€” the context you're finalizing, and heads up: it must have been initialized already. don't come at it raw, bestie πŸ™ˆ
  • out β€” the output πŸ’– this is where the resulting SHA-384 message digest lands, so it's giving "main character" energy for sure.

πŸ”₯ DESCRIPTION πŸ”₯

so after it finishes doing its thing, this bad boy zeroizes ctx. yep, wipes it. so the caller does not need to do it themselves β€” no cap, that's one less chore for you 🫢

like it's giving "I'll clean up after myself, you're welcome" and honestly? obsessed πŸ’œ


🧚 CONTEXT 🧚

Any context. literally any. no constraints, we love a low-maintenance icon ⭐


πŸ‘‘ SEE ALSO πŸ‘‘

bestie there are so many friends in this extended universe, buckle up 🌈


πŸ’– tiny reminder bestie: ctx must be initialized before you call this. that's not a suggestion, that's the vibe check. πŸ’…

🌸 okay that's the whole page, and it comes to you straight from ./include/crypto, dated October 2026 β€” mwah, go forth and finalize those digests, iykyk πŸ“πŸ«Ά

πŸ“¦ where this page comes from