aes_gcm_auth_update(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ aes_gcm_auth_update(9) ✨

okay so like, welcome to the Kernel API Manual bestie 🫢 this one's about aes_gcm_auth_update from the manual page aes_gcm_auth_update(9) β€” yes the name's in the title AND the manual name, it's giving main character energy πŸ’…


πŸ’– NAME πŸ’–

aes_gcm_auth_update β€” literally processes AES-GCM associated data incrementally, one little chunk at a time, no cap ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

void aes_gcm_auth_update (struct aes_gcm_ctx *ctx , const u8 *ad ,
       size_t len );

like, that's the whole signature. short and iconic πŸŽ€


🌸 ARGUMENTS 🌸

  • ctx β€” an AES-GCM context. your lil working space, your vibe holder πŸ’œ
  • ad β€” the associated data. yes, that's the ad right there πŸ“
  • len β€” number of bytes provided. and listen, the caller has to make sure the total associated data length doesn't exceed GCM's limit of 2^61 - 1. that's a real number, respect it πŸ”₯

πŸ‘‘ DESCRIPTION πŸ‘‘

IMPORTANT ⚠️ (like, actually important, not just me being dramatic): callers MUST NOT assume that any decrypted or associated data is authentic until the authentication tag has been verified. periodt. don't trust it till the tag says so πŸ™ˆ


πŸ’€ CONTEXT πŸ’€

Any context. literally any. we're flexible like that πŸ’…βœ¨


🌈 SEE ALSO 🌈

Kernel file ./include/crypto/aes-gcm.h, plus the whole squad:


and that's the page bestie, iykyk πŸ§šπŸ’– this came from ./include/crypto and it's dated October 2026, signed off with aes_gcm_auth_update(9) β€” slay, go verify that tag before you trust anything, mwah πŸ’‹β­

πŸ“¦ where this page comes from