Include code and policy for AppArmor#9
Open
Doeme wants to merge 3 commits into
Open
Conversation
added 3 commits
July 31, 2018 18:06
…ore serving clients. This allows for more fine-grained control in apparmor, where we first allow the process to bind and chroot and setuidgid, and deny all those privileges afterwards.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What this patch does is it includes a policy for AppArmor (inside a new
dist/apparmorsubfolder, which might not be correct) and it lets the process drop its privileges before processing requests, after all the bind(2)-ing and chroot(2)-ing etc. is done.I'm also not sure whether it makes more sense to include this in the code-repo, or to distribute this as patches in e.g. portage.