sha1_final(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay bestie, meet sha1_final(9) from the Kernel API Manual β€” the function that does one thing and does it iconically: Finish computing a SHA-1 message digest. that’s the whole name-and-purpose vibe, no cap ✨

✨ SYNOPSIS ✨

void sha1_final (struct sha1_ctx *ctx , u8 out[static SHA1_DIGEST_SIZE]
);

🌸 ARGUMENTS 🌸

  • ctx β€” the context to finalize; it must have been initialized πŸ’…
  • out β€” (output) the resulting SHA-1 message digest 🫢

πŸ’– DESCRIPTION πŸ’–

so after it finishes, this zeroizes ctx. literally wipes it for you. so the caller does not need to do it β€” periodt, that’s the whole tea πŸ“

πŸ¦‹ CONTEXT πŸ¦‹

Any context. that’s the vibe check, bestie β€” no special context restrictions listed here 🌈

🌈 SEE ALSO 🌈

Kernel file ./include/crypto/sha1.h, struct sha1_ctx(9), sha1_init(9), sha1_update(9), sha1(9), struct hmac_sha1_key(9), struct hmac_sha1_ctx(9), hmac_sha1_preparekey(9), hmac_sha1_init(9), hmac_sha1_init_usingrawkey(9), hmac_sha1_update(9), hmac_sha1_final(9), hmac_sha1(9), hmac_sha1_usingrawkey(9) πŸ‘‘


okay that’s the page, bestie β€” source/version: ./include/crypto, dated October 2026, and it’s giving sha1_final(9) energy πŸ’…βœ¨

πŸ“¦ where this page comes from