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
Disable Container Capabilities for non-admins #4105
Labels
Milestone
Comments
|
blocking #4069 |
|
Re-opening this issue to be backported in 1.24.2 |
sbusso
added a commit
that referenced
this issue
Nov 3, 2020
sbusso
added a commit
that referenced
this issue
Nov 3, 2020
This was referenced Nov 25, 2020
34 tasks
|
Closed via #4510 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently provide the ability for a user to specify additional container capabilities when deploying a container, both using the container UX and also via a compose file. There are certain capabilities that could be escalate privilege higher than a user should need for reasonable activities, and therefore may be deemed a security risk.
We need to provide a new security option that allows the administrator to disable the ability for non-admin users to manually set container capabilities.
This change should be reflected in the front end (remove the option to set capabilities), and also the backend (to block the use via stacks or API).
The text was updated successfully, but these errors were encountered: