Skip to content
New issue

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

[RFE] Use seccomp to create a syscall whitelist and drop capabilities that aren't needed at runtime #25

Closed
dkopecek opened this issue Apr 14, 2015 · 1 comment
Assignees
Milestone

Comments

@dkopecek
Copy link
Member

The code isn't bullet proof. Let's try to secure the daemon with all that's available. This feature should be on by default with an option to disable the feature.

@dkopecek dkopecek added this to the v1.0 milestone Apr 14, 2015
@dkopecek dkopecek self-assigned this Apr 15, 2015
@dkopecek
Copy link
Member Author

Resolved in 9e5e7ca

@dkopecek dkopecek modified the milestones: v0.4, v1.0 Apr 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant