aes_cmac_update(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… aes_cmac_update(9) β€” from the Kernel API Manual, bestie

Okay so picture this: you're deep in the kernel, you've got an AES-CMAC or an AES-XCBC-MAC context, and you have more data to feed it. That's literally this function. It's from the Kernel API Manual, which is giving very "the source of truth, no cap" energy.


✨ NAME ✨

aes_cmac_update β€” bestie, this updates an AES-CMAC or AES-XCBC-MAC context with more data. That's it. That's the whole job. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void aes_cmac_update (struct aes_cmac_ctx *ctx , const u8 *data , size_t
data_len );

Like, look at it. Three args. Clean. Iconic. πŸ‘‘


🌸 ARGUMENTS 🌸

  • ctx β€” the context you're updating, babes. It must have been initialized β€” no showing up uninvited to this party. πŸ™ˆ
  • data β€” the message data. The actual bytes. The main character, honestly. ⭐
  • data_len β€” how long data is, in bytes. And lowkey the best part? It doesn't need to be block-aligned. Fr fr, feed it whatever length you want. πŸ”₯

πŸ’– DESCRIPTION πŸ’–

This can be called any number of times. Literally any number. Zero, one, forty-seven, a million β€” it's not picky, and that's why we stan. ✨


🌈 CONTEXT 🌈

Any context. Yes, any β€” this function is for everyone, no gatekeeping here. 🫢


πŸ’œ SEE ALSO πŸ’œ

The kernel file ./include/crypto/aes-cbc-macs.h, and the whole friend group:

Like, go read them. They're the supporting cast and they ate. πŸ’…


🧚 Quick vibe check: ctx must be initialized before you call this. That's not a suggestion, that's the rule, iykyk. 😭

That's the whole page, bestie β€” sourced from ./include/crypto, dated October 2026. Screenshot it, memorize it, whatever, just go slay in the kernel. πŸ“πŸ‘‘βœ¨

πŸ“¦ where this page comes from