pkcs7_supply_detached_data(9)

okay so bestie, welcome to the pkcs7_supply_detached_data(9) page from the Kernel API Manual 💖 — it’s short, it’s iconic, and it’s all about giving a PKCS#7 message the detached data it needs to verify stuff. Slay.

✨ NAME ✨

pkcs7_supply_detached_data — supply the data needed to verify a PKCS#7 message. That’s the whole assignment, no cap 💅

🌸 SYNOPSIS 🌸

int pkcs7_supply_detached_data (struct pkcs7_message *pkcs7 , const void
       *data , size_t datalen );

🎀 ARGUMENTS 🎀

• pkcs7 — the PKCS#7 message. Your structured little bestie 🫶
• data — the data to be verified. Literally the data, bestie.
• datalen — the amount of data. Size matters here, and it’s a size_t ✨

🦋 DESCRIPTION 🦋

Okay so here’s the tea: you use this to supply the detached data needed to verify a PKCS#7 message. Note that no attempt to retain/pin the data is made — that is left to the caller. No cap, you’re responsible for that part.

The data will not be modified by pkcs7_verify and will not be freed when the PKCS#7 message is freed. So it’s giving borrowed-library-book energy, not “ours now” energy 🙈.

Returns -EINVAL if data is already supplied in the message, 0 otherwise. Periodt.

🌈 SEE ALSO 🌈

• Kernel file ./crypto/asymmetric_keys/pkcs7_verify.c
• pkcs7_verify(9) — the bestie this function is feeding 👑

mwah 💋 this page lives under ./crypto/asymmetric_keys, and it’s dated October 2026. Bye bestie, go verify something cute! 🎀