crypto_ahash_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… crypto_ahash_init(9) β€” the kernel API manual, but make it make sense πŸŽ€

okay so bestie, you're looking at crypto_ahash_init(9) from the Kernel API Manual. it's short, it's sweet, and it's literally about wiping the slate clean. let's get into it ✨


✨ NAME ✨

crypto_ahash_init β€” (re)initialize message digest handle

like, resets the vibe of your digest. fresh start energy πŸ’«


🌸 SYNOPSIS 🌸

int crypto_ahash_init (struct ahash_request *req );

πŸŽ€ ARGUMENTS πŸŽ€

  • req β€” your ahash_request handle 🫢 and no cap, it has to already be initialized with all the necessary data using the ahash_request_* API functions. like, do your homework first, then come talk to this function. it's giving "prerequisites matter" πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

so basically: this call (re-)initializes the message digest that your ahash_request handle is pointing at. πŸͺ„

and the way that any potentially existing state created by previous operations just gets discarded?? yep. gone. deleted. not me throwing away your whole history 😭 that's the whole point though β€” clean slate, main character energy, periodt. πŸ’€βœ¨


πŸ‘‘ RETURN πŸ‘‘

the return value? it lives over in crypto_ahash_final β€” go check there, iykyk πŸ”₯


🌈 SEE ALSO 🌈

the friend group 🫢 (all of these, fr fr):


okay that's the whole page, you ate that πŸ’–

sign-off bestie: this little legend lives in the Kernel file ./include/crypto, dated October 2026, and yes the manual name is crypto_ahash_init(9) β€” now go reinitialize something, slay πŸŒΈπŸ¦‹β­

πŸ“¦ where this page comes from