Add PR_SET_NO_NEW_PRIVS flag #65
Merged
Conversation
This file contains hidden or 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
bleggett
force-pushed
the
bleggett/add-no-new-privs
branch
from
fcd4c5f to
1d8a5b5
Compare
bleggett
force-pushed
the
bleggett/add-no-new-privs
branch
from
1d8a5b5 to
49cb1ca
Compare
azenla
approved these changes
Jan 29, 2026
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is a bit of a niche flag and IMO somewhat pointless as a security knob versus just properly dropping capabilities, but it is something container runtimes will conditionally set in combination with capabilities and which can be observed in a workload context, so we should plumb it thru.