man: clarify SCMP_FLTATR_CTL_NNP semantic #39
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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]>
|
I stepped into this while exploring a more complex systemd scenario, and I was not sure about proper usage. I digged into source to be sure about the semantic, and I think re-wording the manpage in this way makes it more explicit. /cc @alban |
|
Merged in 937e774, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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]