-
Notifications
You must be signed in to change notification settings - Fork 54
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
Best practice: Container should execute process(es) as a non-root user #182
Conversation
This covers the least privilege best practice of avoiding running processes as root in containers Co-authored-by: Ian Wells <iawells@cisco.com>
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are "no root" and "non-root" terms the same? If that's true the document uses those interchangeably so I'll be nice to clarify it.
Co-authored-by: Taylor Carpenter <taylor@vulk.coop>
Co-authored-by: Ian Wells <iawells@cisco.com>
Co-authored-by: Jeffrey Saelens <nerdengineering@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good, but I have a couple comments and questions as I am a little unclear about the use of "privileged" and "privileges" throughout the BP
@pgoyal01 please review again. Your items have been resolved and user stories have been added. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
I have only one nit pick in line, please check.
This patch also seem to contain quite some unrelated changes. I don't know if that's because of a rebase or it's intentionally addressing multiple issues, it would be great to avoid this in the future if possible as it makes reviewing harder.
Thanks,
Ildikó
Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com>
typos and grammar from @pgoyal01 Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com>
capabilities instead of privileges to avoid confusion
fixed thanks.
Yes, that was a rebase. I hoped to avoid updates that were already accepted. Unfortunately, we ended up with more changes showing :/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick fix, it looks good to me now.
I also think it might be worthwhile to merge this and have follow up PRs in case there are still other bits to fix to avoid it picking up more unrelated changes.
- added a set of supply chain attack stories - reference these stories from the non-root best practice * adding links to user stories * Updating best practice user story index links * Apply suggestions from code review ref: - https://github.com/cncf/cnf-wg/pull/182 - https://github.com/cncf/cnf-wg/pull/193 Sign-off: Taylor Carpenter <taylor@vulk.coop> Co-Authored-by: Ian Wells <iawells@cisco.com> Co-authored-by: Gergely Csatari <gergely.csatari@nokia.com> Co-authored-by: Michael Sølvkær Pedersen <michaelx.pedersen@intel.com>
Co-authored-by: Victor Morales <v.morales@samsung.com>
This covers the least privilege best practice of avoiding running processes as root in containers
See least privilege issue #67 and discussion https://github.com/cncf/cnf-wg/discussions/20
Alternative best practice name: "Container should execute process(es) as non-root user"
Co-authored-by: Ian Wells iawells@cisco.com