aes_ecb_decrypt(9)

💅 aes_ecb_decrypt(9) — like, the whole glow-up

okay bestie, so this is a page from the Kernel API Manual and honestly? it's a short one but it's iconic in a "we only keep you around for legacy reasons" kind of way. anyway, buckle up 🎀

---

✨ NAME ✨

aes_ecb_decrypt — decrypt data using AES-ECB 🔓

---

✨ SYNOPSIS ✨

void aes_ecb_decrypt (u8 *dst , const u8 *src , size_t len , const
struct aes_key *key );

like yes, that's the whole signature, no cap 💅

---

✨ ARGUMENTS ✨

• dst — the destination buffer, queen 👑. it can be in-place or out-of-place, so do whatever fits your life. but for other overlaps the behavior is unspecified, so like… don't, okay? 🙈 that's the vibe check you can absolutely fail.
• src — the source data, aka the ciphertext you're trying to un-scramble. 🌸
• len — number of bytes to decrypt. must be a multiple of AES_BLOCK_SIZE, fr fr, no exceptions. 😤
• key — the key, already prepared using aes_preparekey 🔑. don't come at it raw.

---

✨ DESCRIPTION ✨

ngl, ECB mode is insecure by itself. 💀 like, we said what we said. this function exists only for compatibility with legacy protocols and for internal use by other modes. so it's giving "main character with a tragic backstory" — it's here, it works, but it's not the hero of this story. 😭

it does support incremental decryption though, bestie ✨ — just remember that the length of each chunk must be a multiple of AES_BLOCK_SIZE. every single one. periodt. 💅

🫶 real talk: don't build something new on ECB. the manpage literally says it's insecure. take the warning seriously even while we're being cute about it.

---

✨ CONTEXT ✨

any context. literally any. 🌈 go wild.

---

✨ SEE ALSO ✨

• the kernel file ./include/crypto/aes-ecb.h
• aes_ecb_encrypt(9) — the encryption twin, go say hi 🦋

---

aaaand that's the page!! 🌸 this little cutie lives in ./include/crypto and it's dated October 2026, so like, mark your calendar bestie 💖 mwah, go decrypt responsibly ✨🎀