We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Consider adding defense-in-depth mechanisms limiting the scope of what a compromised dangerzone & associated programs can do on the system.
Strategies to consider:
Related:
The text was updated successfully, but these errors were encountered:
This should be added only after setting up a set of automated tests both to help generate the profiles and to guarantee we caught most regular usage.
Sorry, something went wrong.
Tentatively added to 0.4.0 milestone, but we'll need to decide initial scope (e.g., AppArmor only?).
Closing this issue in favor of #225 (seccomp) and #227 (AppArmor), which are part of the larger #221 (defense in depth) issue.
No branches or pull requests
Consider adding defense-in-depth mechanisms limiting the scope of what a compromised dangerzone & associated programs can do on the system.
Strategies to consider:
Related:
The text was updated successfully, but these errors were encountered: