-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Altered root user check for vm-driver=none #5123
Conversation
Welcome @WurmNL! |
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Hi @WurmNL. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: WurmNL The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Can one of the admins verify this patch? |
…t have the "Name" set.
Same as #4995 - not sure why that was "merged" with the Windows changes though ? @blueelvis ? As per the earlier reports, we might want to check for UID 0 rather than testing the login name... |
@afbjorklund - #4995 hasn't been merged. medya closed it in favor of #4745. I am still working on fixing those integration test issues. Details in there. Once that is merged, all of these issues would be fixed. |
Just saying that I think we should fix this one-liner first, and do those unrelated changes later. WDYT @medyagh |
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.
Update this to check that u.Uid
is 0 instead. Naming a user "root" should not confer any special powers.
I'm OK if this gets merged in first, so long as it is checking the correct field (uid). |
@minikube-bot OK to test |
Obsoleted by #5179 - thank you for bringing this to our attention! |
Altered current user check to use user.Username as some distro's don't have the "Name" set. This caused me to "add" root to the root user on ArchLinux:
root:x:0:0:thiscanbeanything:/root:/bin/bash