profile_capable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to profile_capable(9) β€” the Kernel API Manual page that’s about to explain itself. πŸ’… No cap, every detail is staying.

🌸 NAME 🌸

profile_capable β€” test if profile allows use of capability @cap. periodt. ✨

✨ SYNOPSIS ✨

here’s the signature, character-for-character, don’t let the line break scare you:

int profile_capable (struct aa_profile *profile , int cap , unsigned int
       opts , struct apparmor_audit_data *ad );

πŸŽ€ ARGUMENTS πŸŽ€

  • profile β€” the profile being enforced. It’s NOT NULL and not unconfined (the original is very loud about this, and honestly same). 🫢
  • cap β€” the capability to test if allowed. πŸ”₯
  • opts β€” the CAP_OPT_NOAUDIT bit determines whether an audit record is generated. πŸ‘€
  • ad β€” audit data, and it is NOT NULL. periodt.

πŸ”₯ RETURN πŸ”₯

0 if allowed, else -EPERM β€” that’s the whole mood. βœ…πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹


mwah πŸ’‹ β€” source/version ./security/apparmor, date October 2026, page profile_capable(9). byeee πŸŽ€

πŸ“¦ where this page comes from