Skip to content

fix(bluefin): SSH as core; root is locked by the image since 26.10 - #70

Merged
jeefy merged 3 commits into
mainfrom
fix/bluefin-ssh-user
Oct 1, 2026
Merged

jeefy merged 3 commits into
mainfrom
fix/bluefin-ssh-user

Conversation

@jeefy

@jeefy jeefy commented Oct 1, 2026

Copy link
Copy Markdown
Owner

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).

  • Node Ignition: the `sshkeys` builtin now provisions `core` on Bluefin, the same login as Flatcar/CoreOS: `groups: [wheel]`, `shell: /bin/bash`, the configured keys, `passwordHash: "*"` and `/etc/sudoers.d/booty-core` (0440, `core ALL=(ALL) NOPASSWD: ALL`). The root entry is gone; `sshd.service` is still enabled alongside.
  • SSH actuator: `core` + `sudo systemctl reboot|poweroff` on every OS; `sshUsers` in `/autopilot`, `--rebootSSHKey` help and tests follow.
  • README: Bluefin node Ignition section, Features bullet, Autopilot/Power actuator text.

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

  • `gofmt`, `go vet`, `go test ./... -race` (712 pass), `golangci-lint` clean
  • Node ign unit test: core user with keys, wheel, bash, `*`, sudoers drop-in 0440, no root entry; goldens regenerated
  • Actuator tests: user map and commands for all three OSes
  • Live: boot a 26.10 Bluefin node from this build and `ssh core@node sudo systemctl status sshd`

Ultraworked with Sisyphus

jeefy and others added 3 commits October 1, 2026 14:58
… 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>
@jeefy
jeefy merged commit 9fd5c6a into main Oct 1, 2026
5 checks passed
@jeefy
jeefy deleted the fix/bluefin-ssh-user branch October 1, 2026 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant