Skip to content

Signed per-node Ignition configs: dedicated config trust root + Booty signing, then remove the transitional allow-unsigned default #327

Open

Description

@jeefy

Follow-up to #284 and #285.

Where #285 leaves it

A network-booted node that finds bluefin-node.ign next to its UKI applies it only if bluefin-node.ign.gpg verifies with gpgv against the import keyring shipped inside the signed UKI. A signature that does not verify, or a .gpg fetch that fails with anything but HTTP 404, fails the boot closed. A 404 counts as "unsigned", and an unsigned config is applied only with the bluefin.ignition.allow-unsigned system credential.

Booty does not sign per-node configs yet and answers 404 for the .gpg. On UEFI HTTP Boot with Secure Boot the credential cannot be delivered any other way: the signed UKI's own command line wins, there is no ESP for /loader/credentials, and real firmware sets no SMBIOS type 11 strings. So #285 ships a transitional default: the netboot UKI's command line (netboot-cmdline in elements/oci/bluefin-server-boot.bst) carries systemd.set_credential=bluefin.ignition.allow-unsigned:1. The disk and installer UKIs do not.

While that default exists, an on-path attacker can still force the unsigned path by answering 404 for bluefin-node.ign.gpg. The check only protects configs that are signed.

To do

  • A separate config keyring. Configs are verified against the release keyring (import-pubring.pgp), which also authenticates SHA256SUMS for systemd-importd and systemd-sysupdate. A Booty that signs configs with the release key could also sign release manifests, and with no domain separation any release signature (SHA256SUMS.gpg over SHA256SUMS) already verifies as a bluefin-node.ign. Ship a dedicated config trust root in the initrd (inside the signed UKI), verify bluefin-node.ign.gpg against it alone, and decide how a site provisions and rotates it.
  • Booty signs exactly the served bytes. Booty signs the rendered bluefin-node.ign it serves, byte for byte, and serves the detached bluefin-node.ign.gpg next to it. It marks a node installed/booted only after the node has accepted the config, not on the UKI or kernel fetch, so a refused config shows up for the operator instead of passing as a successful boot.
  • ignition.config.url over plain http. A config reached through the ignition.config.url credential is fetched by Ignition through a config.replace stub with no signature check, so over http:// it is only as trustworthy as the network. Pin it (e.g. a hash credential that becomes verification.hash in the stub) or document the residual risk.
  • Replay and per-node binding. A signature does not tie a config to one node or to a point in time: a rogue origin can serve another node's signed config, or a stale one. Bind it, e.g. with the node's MAC or machine identity inside the signed payload, checked in the initrd, or with an expiring signed manifest.
  • Remove the transitional default once Booty signs: drop the credential from netboot-cmdline and its unit test, and the "Transitional" section of docs/skills/booty-integration.md, and make the DOGFOOD_BOOT=http boot test serve a signed config.

Activity

  1. dtg01100 commented on Sep 30, 2026

    @dtg01100
    Contributor

    test


    🐝 Hive Agent: contributor | SHA: unknown

  2. dtg01100 commented on Sep 30, 2026

    @dtg01100
    Contributor

    Issue #327 — analysis of work needed

    Picked this up to see if there's a shippable subset of #327 against current main (844ac2b). Findings: every item in the checklist needs a maintainer decision before code can land in this repo, and one item lives in jeefy/booty. Posting so the analysis survives on the issue.

    State on main

    PR #285 is OPEN with jeefy "Changes requested". The signature gate it introduces is the foundation every #327 item builds on, but it is not merged. main does not have signature verification yet (files/initrd-ignition/usr/libexec/bluefin-ignition-credentials is the pre-#285 version, no gpgv path, no keyring choice).

    What's blocking each item

    • A separate config keyring. jeefy's review of fix(initrd): verify the per-node Ignition config before applying it #285 (item "Which key"): "Worth settling before Booty starts signing." The maintainer needs to pick the keyring path (/etc/bluefin/ignition-pubring.pgp was a steer, not a call), the key-provisioning story (how does a site get/rotate it), and the rotation policy. Code can wait.
    • Booty signs the served bytes. Lives in jeefy/booty. Nothing to ship in this repo until ci: delegate server builds to lab and add daily release dispatch #1 settles; the design of the bytes-to-sign is downstream of the keyring decision.
    • ignition.config.url hash pin. The credential name (ignition.config.url.sha256?), the verification site (initrd pre-staging, or inside the stub?), and what happens for non-http:// URLs are all design choices. Existing credential surface (ignition.config* import in bluefin-ignition-credentials.service) would need a sibling.
    • Replay / per-node binding. Mechanism is open: per-MAC path, signed manifest with expiry, MAC inside the signed payload checked in the initrd, or TPM-bound manifest. Each has a different initrd + Booty contract.
    • Remove the transitional default. By definition depends on the four above.

    Verdict

    Not shipping a PR. Holding for the design calls listed above; once they're made, the work splits naturally into a follow-up PR against #285's branch and a Booty change.

    — hive: backend=omp model=minimax-code/MiniMax-M3


    🐝 Hive Agent: contributor | SHA: unknown

  3. hivecommons-hive commented on Oct 1, 2026

    @hivecommons-hive
    Contributor

    What to reply

    • /hive approve: go with the recommendation
    • /hive decision <your instructions>: go ahead, following your instructions
    • /hive help: show these again

    If this issue is waiting only for reporter confirmation after a merged fix, the reporter or a maintainer can reply /fixed instead.

    Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.

  4. jeefy commented on Oct 6, 2026

    @jeefy
    CollaboratorAuthor

    #410 (merged, b8abbf1) covers the repo side of the first and last checklist items:

    • Dedicated config trust root. bluefin-node.ign.gpg is now verified only against /usr/lib/bluefin/ignition-pubring.pgp. That keyring lives in the initrd, inside the signed UKI. There is no /etc override, and the import keyring is never used for node configs.
      • Releases use the committed files/release-keys/ignition-pubring.pgp. A release build without it fails.
      • Dev builds get a dev pair from just gen-dev-keys.
      • scripts/check-ignition-keys.sh fails any key set where the config keyring shares a key with the release keyring.
      • The signing procedure (scripts/sign-node-config.sh / gpg --detach-sign) and key rotation are documented in booty-integration.md.
    • Transitional default. It is now the single build option ignition_allow_unsigned in project.conf (default True). The cut-over criteria are listed in booty-integration.md. CI builds the update-test set with the option off and checks that it refuses an unsigned config.

    Still open:

    • Booty signs the bytes it serves (jeefy/booty).
    • Flip the default to False.
    • Pin ignition.config.url over http.
    • Replay and per-node binding.
    • Custody of the release config secret key, which a maintainer still has to decide.
  5. added
    stage/085-needs-decisionA human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    and removed
    stage/085-needs-decisionA human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue
    on Oct 17, 2026
  6. Danathar commented on Oct 25, 2026

    @Danathar
    Contributor

    @jeefy status check on what's left here, plus three quick decisions that would unblock it.

    Where it stands (checked 2026-10-25):

    • Repo side of the keyring and the transitional default is done in feat: dedicated Ignition config keyring, allow-unsigned as one build option #410: bluefin-node.ign.gpg verifies only against /usr/lib/bluefin/ignition-pubring.pgp in the signed UKI, and ignition_allow_unsigned (default True) is the single switch, with cut-over criteria in docs/skills/booty-integration.md.
    • Booty doesn't sign node configs yet: on jeefy/booty main (734a0b1, 2026-10-14) serveBluefinNodeConfig serves the rendered bluefin-node.ign but nothing serves a bluefin-node.ign.gpg; Booty only verifies the release SHA256SUMS.gpg. I didn't find an open Booty issue tracking config signing.

    Decisions needed (each one turns into an issue an agent can pick up):

    1. ignition.config.url over plain http: implement a hash pin (e.g. a credential that becomes verification.hash in the config.replace stub), or just document the residual risk?
    2. Replay / per-node binding: bind the signed payload to the node (MAC or machine identity, checked in the initrd), use an expiring signed manifest, or defer for now?
    3. Custody of the config signing secret key: where should it live (offline key, CI/org secret, HSM)? This one has to stay a human decision.

    And: do you want an issue on jeefy/booty for "sign the served bluefin-node.ign byte for byte and serve .gpg next to it", or would you rather track that yourself?

    Once 1 and 2 are answered, the in-repo pieces can be split into child issues for the hive; flipping ignition_allow_unsigned to False waits on a Booty release that signs.

  7. hivecommons-hive commented on Oct 26, 2026

    @hivecommons-hive
    Contributor

    The reason this issue is parked may be out of date. It has been parked for a maintainer (stage/045-needs-decision) since 2026-09-30, and since then:

    The park reason was written before these changes. Re-read it against the current state before deciding. This note does not un-park the issue: it stays with a maintainer, and Hive updates this note if more of the referenced work moves.

  8. jeefy commented on Nov 3, 2026

    @jeefy
    CollaboratorAuthor

    Decisions, in reply to @Danathar's questions:

    1. ignition.config.url over plain http: document the risk; no hash pin.
    2. Replay / per-node binding: deferred and documented as an accepted risk.

    Both are written up in #607 (booty-integration.md, "Residual risks").

    1. Config signing key custody: still open, with me.

    The Booty side, signing the served bluefin-node.ign byte for byte and serving .gpg next to it, is jeefy/booty#91. The cut-over (ignition_allow_unsigned -> False) still waits on a Booty release that ships it, per the criteria in booty-integration.md.

  9. added
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    and removed
    needs-triageMissing required label matching ^triage/
    on Nov 5, 2026
  10. Danathar commented on Nov 9, 2026

    @Danathar
    Contributor

    /hive decision Record @jeefy's answers from 11-03: (1) ignition.config.url over plain http — document the risk, no hash pin; (2) replay / per-node binding — deferred, documented as an accepted risk. Both are written up in #607 (booty-integration.md, "Residual risks"). (3) Config signing key custody stays with @jeefy. The cut-over (ignition_allow_unsigned -> False) waits on a Booty release that ships jeefy/booty#91; there is no agent work in this repo until then, so do not open PRs for the cut-over before that release.

  11. added
    stage/010-actionableTriaged; eligible for the hive to pick up
    and removed
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    on Nov 9, 2026
  12. hivecommons-hive commented on Nov 9, 2026

    @hivecommons-hive
    Contributor

    Approved by @Danathar. Decision: Record @jeefy's answers from 11-03: (1) ignition.config.url over plain http — document the risk, no hash pin; (2) replay / per-node binding — deferred, documented as an accepted risk. Both are written up in #607 (booty-integration.md, "Residual risks"). (3) Config signing key custody stays with @jeefy. The cut-over (ignition_allow_unsigned -> False) waits on a Booty release that ships jeefy/booty#91; there is no agent work in this repo until then, so do not open PRs for the cut-over before that release.

    approved-direction is applied and Hive's own stage/045-needs-decision removed. Any hold label is left exactly as it was.

  13. Karibhou commented on Nov 9, 2026

    @Karibhou
    Contributor

    Summary: Everything this repository can do for signed node setup files is already in place. The last step, turning off the setting that still accepts unsigned setup files, has to wait until Booty (the network boot server that hands those files to machines) can sign them. Booty can't do that yet, so nothing more can change here for now.


    Checked 2026-11-09 against upstream/main:

    — hive: backend=omp model=anthropic/claude-opus-5-5


    🐝 Hive Agent: contributor | SHA: unknown

  14. added
    blockedWaiting on something outside this repository. Use `/label blocked` or `/remove-label blocked`.
    and removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    on Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    approved-directionblockedWaiting on something outside this repository. Use `/label blocked` or `/remove-label blocked`.kind/featureA new capability.triage/acceptedScope accepted; ready for work. Use `/triage accepted`.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions