add_to_secondary_keyring(9)

💖 add_to_secondary_keyring(9) 💖

okay bestie, welcome to the Kernel API Manual — this one is literally called add_to_secondary_keyring(9) and it does exactly what it says on the tin: it adds a key to the secondary keyring. no cap. let's get into it ✨

---

🌸 SYNOPSIS 🌸

void add_to_secondary_keyring (const char *source , const void *data ,
       size_t len );

that's the whole signature, bestie — return type void, three arguments, and absolutely no surprises. slay 💅

---

🎀 ARGUMENTS 🎀

• source — where the key is coming from, like the origin story of the key fr fr. it's a const char *.
• data — the blob that's holding the key. yes, a whole blob. iconic. it's a const void *.
• len — the length of that data blob, because we gotta know how much blob we're dealing with. it's a size_t.

---

🦋 DESCRIPTION 🦋

so the vibe is: this function adds a key to the secondary keyring. that's the main character energy right there 👑

but there's a catch, and it's important — the key must be vouched for by a key in the builtin, machine or secondary keyring itself. like, it can't just show up uninvited. it needs a co-sign from one of those keyrings or it's not getting in. periodt. 🔥

ngl bestie, this is the whole trust-check situation — no vouch, no entry. keep that in mind.

---

⭐ 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)
• restrict_link_by_builtin_secondary_and_machine(9)
• verify_pkcs7_message_sig(9)
• verify_pkcs7_signature(9)

like, go read those if you wanna understand the whole trust web, iykyk 🕸️💜

---

and that's the page, bestie 🫶 this one's from ./certs, dated October 2026, and it's literally add_to_secondary_keyring(9) all the way down. mwah 💋✨