Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

man: clarify SCMP_FLTATR_CTL_NNP semantic #39

Closed
wants to merge 1 commit into from
Closed

man: clarify SCMP_FLTATR_CTL_NNP semantic #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
man: clarify SCMP_FLTATR_CTL_NNP semantic 
Clarify that the zero value results in a no-op on libseccomp
side, and applications will need to have to have proper caps
or set NO_NEW_PRIVS by themself.

Signed-off-by: Luca Bruno <[email protected]>
  • Loading branch information
@lucab
lucab committed Jun 10, 2016
commit 846a986d9d6580906d865caf210a99c343a5acec
7 changes: 4 additions & 3 deletions doc/man/man3/seccomp_attr_set.3
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,10 +59,11 @@ action.
.TP
.B SCMP_FLTATR_CTL_NNP
A flag to specify if the NO_NEW_PRIVS functionality should be enabled before
loading the seccomp filter into the kernel. If set to off (
loading the seccomp filter into the kernel. Setting this to off (
.I value
== 0) then loading the seccomp filter into the kernel will fail if CAP_SYS_ADMIN
is not set. Defaults to on (
== 0) results in no action, meaning that loading the seccomp filter into the
kernel will fail if CAP_SYS_ADMIN is missing and NO_NEW_PRIVS has not been
externally set. Defaults to on (
.I value
== 1).
.TP
Expand Down