security_capset(9)

📦 version 7.3.1, in nixpkgs unstable

💅 security_capset(9)

Okay so bestie, pull up a chair, this one's from the Kernel API Manual and honestly? It's a whole lil' baddie of a function. Let's get into it ✨

🎀 NAME 🎀

security_capset — sets the capability sets for a process. That's it. That's the whole job. Iconic, honestly.

🌸 SYNOPSIS 🌸

int security_capset (struct cred *new , const struct cred *old , const
       kernel_cap_t *effective , const kernel_cap_t *inheritable , const
       kernel_cap_t *permitted );

Like, look at all those parameters — she's got range 💅

🦋 ARGUMENTS 🦋

  • new — the brand-new credentials for the target process. the glow-up in progress 💖
  • old — the current credentials of the target process. the before picture, if you will.
  • effective — the effective capability set. the one that's actually live and doing the thing.
  • inheritable — the inheritable capability set. the one that gets passed down, like trauma but for permission bits 🎀
  • permitted — the permitted capability set. the ceiling of what's allowed.

👑 DESCRIPTION 👑

So the vibe here is simple: this sets the effective, inheritable, and permitted capability sets for the current process. All three at once. No cap. Slay 💅

Like yes, it's "just" setting caps — but it's setting all three of them, so don't sleep on it.

⭐ RETURN ⭐

Returns 0 and updates new if permission is granted. That's the whole deal — 0 plus a freshly updated new, and you're golden 🫶

🌈 SEE ALSO 🌈

Kernel file ./security/security.c — and okay, the extended fam is enormous, so here goes, in order, no skips, no cap 🧚

And that's the whole extended fam — genuinely the longest contact list I've ever seen, but she ate and left no crumbs 👑💜

Okay bye bestie, this page came from the ./security source and it's dated October 2026, filed under security_capset(9) — go forth and set those caps 💖✨🎀

📦 where this page comes from