Mentions kernel.yama.ptrace_scope = 3 breaks lxc v6+ procfs
#14
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
|
Thanks for the PR. I've read the other thread, nice debugging efforts. Restricting ptrace indeed has a lot of implications. I'll amend the text slightly and merge in a bit. |
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.
Hello @k4yt3x 👋
I've been recently struggling with this, and as lxc (unprivileged) containers are widely used to isolate some environments, I wondered whether this mention could be included here (as default Yama ptrace scope of
3definitely breaks procfs emulation, and could not be reverted without a reboot...).Thanks for your time, bye 👋