verify_pkcs7_message_sig(9)

💖 verify_pkcs7_message_sig(9) 💖

Kernel API Manual — yes bestie, this is the one. Grab your iced coffee, we’re verifying signatures. 🧊✨

🌸 NAME 🌸

verify_pkcs7_message_sig — verify a PKCS#7-based signature on system data. That’s the gig: PKCS#7 signature, system data, verified. No cap. 💅

✨ SYNOPSIS ✨

int verify_pkcs7_message_sig (const void *data , size_t len , struct
pkcs7_message *pkcs7 , struct key *trusted_keys , enum
key_being_used_for usage , int (*view_content)(void *ctx, const void
*data, size_t len, size_t asn1hdrlen) , void *ctx );

The function signature is literally that, and the spacing is part of the aesthetic. Do not come for it. 🫶

🫶 ARGUMENTS 🫶

• data — the data to be verified. It’s NULL if you’re expecting internal data, okay?
• len — size of data. Simple as that. 📏
• pkcs7 — the PKCS#7 message that is the signature. Main character energy. 👑
• trusted_keys — trusted keys to use. NULL means builtin trusted keys only; (void *)1UL means all trusted keys. Very important bestie, do not freestyle this one. 🔐
• usage — the use to which the key is being put. It’s giving “what is this key even doing right now”. 🫡
• view_content — callback to gain access to content. iykyk. 👀
• ctx — context for callback. Gotta hand the callback its little context. 🎀

🌈 SEE ALSO 🌈

• Kernel file ./certs/system_keyring.c
• restrict_link_by_builtin_trusted(9)
• restrict_link_by_digsig_builtin(9)
• restrict_link_by_builtin_and_secondary_trusted(9)
• restrict_link_by_digsig_builtin_and_secondary(9)
• add_to_secondary_keyring(9)
• restrict_link_by_builtin_secondary_and_machine(9)
• verify_pkcs7_signature(9)

Okay that’s the whole page, bestie. Signed off with love from ./certs in the Kernel API Manual, dated October 2026 — periodt. 💌✨