Repository navigation
fix(bluefin): SSH as core; root is locked by the image since 26.10 - #70
Merged
Merged
Conversation
… locked since 26.10 projectbluefin/server #275 (26.10) ships root as !unprovisioned and its sshd runs without PAM, which refuses key logins to a locked account, so the root.sshAuthorizedKeys the node Ignition carried were never usable (seen on 26.10.816 and 26.10.827: the key is offered and rejected). The sshkeys builtin now provisions core, as on Flatcar and CoreOS: group wheel, /bin/bash, the configured keys, passwordHash "*" (useradd's default "!" would lock it the same way) and /etc/sudoers.d/booty-core (0440, NOPASSWD: ALL), mirroring upstream's developer-mode recipe. The root entry is gone. Golden fixtures regenerated. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Bluefin nodes now carry a core user with passwordless sudo and a locked root, so the SSH actuator logs in as core and runs sudo systemctl reboot|poweroff on every OS; sshUsers in /autopilot and the --rebootSSHKey help follow. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
…ked since 26.10 Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SSH to Bluefin Server nodes rendered by Booty stopped working with projectbluefin/server 26.10: #275 (`8824f9e`, "ship root locked; provision access per node") seeds root as `!unprovisioned`, and the image's sshd runs without PAM, which refuses publickey logins to a locked account. The `passwd.users[root].sshAuthorizedKeys` Booty wrote were therefore never usable (verified live on 26.10.816 and 26.10.827: the key is offered and rejected).
Rendered passwd block:
{"users":[{"groups":["wheel"],"name":"core","passwordHash":"*","sshAuthorizedKeys":["ssh-ed25519 ..."],"shell":"/bin/bash"}]}Why `passwordHash: "*"`
`useradd`'s default password field is `!` (locked), which the PAM-less sshd rejects exactly like root's `!unprovisioned`. Upstream's own sysusers drop-in and USB-installer "developer mode" recipe spell this out: "``: no password login, but not locked like sysusers' default `!`, which sshd (UsePAM no) refuses even for keys". Without it `core` would be as unreachable as root.
What upstream recommends, and what was adopted
`docs/skills/tpm2-credential-sealing.md#node-access` recommends Ignition `passwd.users name: root` + `sshAuthorizedKeys` (naming Booty as the consumer) or the `ssh.authorized_keys.root` credential — both write `/root/.ssh/authorized_keys`, and both hit the same locked-root wall on this image, so neither is adopted. The `passwd.hashed-password.root` / `ssh.listen` credentials need creds plumbing (SMBIOS/fw_cfg/encrypted ESP `.cred`) that Ignition cannot provide, so they are not used either. Upstream's developer-mode recipe (a user in `wheel`, `/etc/sudoers.d/50-` 0440 `NOPASSWD: ALL`, password `*`) is what this PR mirrors through Ignition; it also confirms `wheel` exists and the image's sudo includes `/etc/sudoers.d`. No `sudo`/`docker` groups exist in the image, so `core` is only in `wheel`.
Test plan
Ultraworked with Sisyphus