crypto_krb5_...are_checksum(9)

💅 crypto_krb5_prepare_checksum — kernel API manual, section 9, bestie

okay so this is a page from the Kernel API Manual (section 9, the big-kid kernel space one), and it's literally all about getting your AEAD crypto object ready for checksum-mode. yes, that's the whole vibe. let's get into it 🎀

---

✨ NAME ✨

crypto_krb5_prepare_checksum — prepare an AEAD crypto object for checksum-mode, no cap 💖

---

🌸 SYNOPSIS 🌸

struct crypto_shash * crypto_krb5_prepare_checksum (const struct
krb5_enctype *krb5 , const struct krb5_buffer *TK , u32 usage , gfp_t
gfp );

like, that's the signature. it returns a struct crypto_shash *, bestie. remember that for later 👑

---

🦋 ARGUMENTS 🦋

• krb5 — the encoding to use. yes, that one. the enctype. ✨
• TK — the transport key to use. your key, your rules 💜
• usage — the usage constant for key derivation. it's giving "context matters" 🫶
• gfp — allocation flags. the usual allocation-flag situation 🌈

---

🔥 DESCRIPTION 🔥

so what this actually does: it allocates a crypto object that does all the necessary crypto — the whole thing, not just part of it — keys it up, sets its parameters, and hands you back the crypto handle to it. iconic behaviour honestly 👑

and then? then you can use that handle to dispatch get_mic and verify_mic operations. that's the payoff. that's the main character energy 💅

ngl, this is the "get your object ready so the MIC stuff can actually happen" function. no shortcuts, no extra steps, just allocate + key + set params + return handle. slay ✨

---

👀 SEE ALSO 👀

• Kernel file ./crypto/krb5/krb5_api.c
• crypto_krb5_find_enctype(9)
• crypto_krb5_how_much_buffer(9)
• crypto_krb5_how_much_data(9)
• crypto_krb5_where_is_the_data(9)
• crypto_krb5_check_data_len(9)
• crypto_krb5_prepare_encryption(9)
• crypto_krb5_encrypt(9)
• crypto_krb5_decrypt(9)
• crypto_krb5_get_mic(9)
• crypto_krb5_verify_mic(9)

like a whole little krb5 crypto friend group. iykyk 🧚

---

okay that's the page!! sources say it lives at ./crypto/krb5, dated October 2026, and the header/footer label it crypto_krb5_...are_checksum(9) (the name got a lil truncated, it's fine, we love a mystery 🫶). bye bestie, go prepare some checksums 💖✨🎀