-
Notifications
You must be signed in to change notification settings - Fork 394
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
Add option to disable TTY autologin in grub #1625
base: main
Are you sure you want to change the base?
Conversation
Hi @dalees. Thanks for your PR. I'm waiting for a kubernetes-sigs 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-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
/ok-to-test |
Thanks @dalees this looks great! Do you have an example of how to set this value when running image-builder? I can never remember how to override the Ansible variables at runtime. 🙈 |
I'd encourage defaulting The implications of VM console access leading to a trivial root shell without interrupting the host doesn't seem like a great default for Flatcar, or the CAPI image builder. With this proposed option as |
Also the linting is failing because of the use of If you feel |
Yeah, certainly. On the ansible-playbook command line add |
100% agree. I might actually be ok with us doing that by default now actually. I think it's best to encourage best practices when it comes to security. Especially as we've had a couple CVEs we've had to deal with recently it'd be good to have a stricter default on these things. @mboersma @jsturtevant @drew-viles any objections to making this the new default? |
I meant as a user running image-builder via EDIT: Ah! Found it! We support setting |
Ok thanks; I can change the |
Flatcar defaults tty autologin to true[1], and the core user logged in has passwordless sudo. To allow disabling of this, we add an ansible variable 'flatcar_disable_autologin' that defaults to false to disable this during the image build[2]. This does not change the autologin during the image build process but secures the console during use within Kubernetes clusters. [1] flatcar/Flatcar#396 [2] https://www.flatcar.org/docs/latest/setup/customization/other-settings/#enable-flatcar-container-linux-autologin
e449db6
to
786e0fa
Compare
I don't have any objections. Looking at it, it seems sensible BUT I don't use nor have I used flatcar directly so can't say with 100% knowledge on the matter! 😆 |
Change description
Flatcar defaults tty autologin to true[1], and the core user logged in has passwordless sudo.
To allow disabling of this, we add an ansible variable 'flatcar_disable_autologin' that defaults to false to disable this during the image build[2].
This does not change the autologin during the image build process but secures the console during use within Kubernetes clusters.
[1] flatcar/Flatcar#396
[2] https://www.flatcar.org/docs/latest/setup/customization/other-settings/#enable-flatcar-container-linux-autologin
Related issues
None
Additional context
Links included above.