aead_gcm_esp_setkey(9)

📦 version 7.3.1, in nixpkgs unstable

💅 aead_gcm_esp_setkey(9) — the Kernel API Manual, but make it cute

Okay bestie, so this is a page straight out of the Kernel API Manual, and it's called aead_gcm_esp_setkey(9). It's the setkey() operation for the ESP variant of GCM AES. Lowkey a whole mouthful, but we move. 🫶

✨ NAME ✨

aead_gcm_esp_setkey — literally the setkey() operation for the ESP variant of GCM AES. That's it, that's the vibe. 💅

🌸 SYNOPSIS 🌸

int aead_gcm_esp_setkey (struct crypto_aead *cipher , const u8 *key ,
unsigned int keylen );

Short, sweet, returns an int. Slay. ✨

🎀 ARGUMENTS 🎀

  • cipher — the AEAD structure. It's giving "main character" of this whole call, ngl.
  • key — the key, followed by 4 bytes of salt. Yes, the salt is riding shotgun, don't separate them. 🧂
  • keylen — the length of the key plus the salt, in bytes. So it's not just the key length, bestie, it's the whole package. 📏

🦋 DESCRIPTION 🦋

So what does it actually do? It extracts the salt from key and stores it, so that it can be prepended to the IV on each request. Iconic behaviour, honestly. 🌈

And important detail incoming: the digest is always 16 bytes. No cap. 🔥

⭐ RETURN ⭐

It returns the value from the generic gcm setkey. That's the whole tea. 🍓

👑 SEE ALSO 👑

This is the part where the group chat gets long, so buckle up bestie — here's the full squad, all from the kernel file ./drivers/crypto/bcm/cipher.c:

All of them. Every single one. We don't skip entries in this house. 💜

Fr fr though, if you ever touch key and keylen, remember they're a package deal — the salt is in there and it wants to be counted. 🙈

And that's the page, babe! 💖 This lil' beauty lives in ./drivers/crypto/bcm, dated October 2026, and it's your girl aead_gcm_esp_setkey(9) signing off. Mwah! 💋🎀

📦 where this page comes from