hmac_sha384_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 hmac_sha384_init β€” from the Kernel API Manual, bestie πŸ’…

Okay so picture this: you're in the kernel, you've got an HMAC-SHA384 situation, and you need a fresh context for a brand new message. That's literally this function. Welcome to the group chat ✨


✨ NAME ✨

hmac_sha384_init β€” ngl, it just initializes an HMAC-SHA384 context for a new message πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void hmac_sha384_init (struct hmac_sha384_ctx *ctx , const struct
       hmac_sha384_key *key );

πŸ’œ ARGUMENTS πŸ’œ

  • ctx β€” (output) the HMAC context you're initializing, bestie. It gets filled in for you 🫢
  • key β€” the prepared HMAC key. Already prepared, okay? Like, do the prep first, this is not the prep step πŸ’…

πŸ”₯ DESCRIPTION πŸ”₯

Lowkey the whole point: this sets up your context so you can compute incrementally. But listen β€” if you don't need incremental computation, consider hmac_sha384 instead. It's giving one-and-done energy and honestly? Sometimes that's the move 😌


🌈 CONTEXT 🌈

Any context. Fr fr, any. You're free πŸ¦‹


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./include/crypto/sha2.h

The sha224 fam πŸ“:

The hmac_sha224 squad πŸ’–:

The sha256 crew ✨:

The hmac_sha256 icons πŸŽ€:

The sha384 girlies (our main character's home base) πŸ’…:

The hmac_sha384 besties β€” yes, us 🌸:

The sha512 extended universe 🧚:

And the hmac_sha512 legends, closing us out πŸ’€πŸ”₯:


Not me listing every single one of these because every single one of these matters. Iykyk 🫢

And that's the whole page, bestie β€” brought to you by ./include/crypto, dated October 2026, no cap. Mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from