Files
apirroneandClaude Opus 5.5 db7f0311bf robotctl configure --allow-dev-daemon: a dev board in one command
Making a board take branch builds meant copying team.dev.pub into
/etc/robot/trusted_keys under exactly the right name, sed-ing
allow_dev_keys in updater.toml, and restarting updaterd. On the Yocto
image both live in /etc, which an A/B OS update replaces, so the board
quietly stopped being a dev board at the next OS update.

updaterd now carries the dev public key built in (always dev-only), and
dev keys count when `allow-dev-builds` exists in its state_dir, under
/var/lib/robot, which survives OS updates. `sudo robotctl configure
--allow-dev-daemon on|off` writes or removes it and restarts updaterd.
allow_dev_keys = true in updater.toml still works, so provisioned boards
are unchanged; the shipped config keeps it false and nothing ships the
marker.

Needs an updaterd from a release that carries this: an older one
ignores the marker.

Docs: updater-design.md §5.4 owns the mechanism; install-dev,
cheatsheet-dev, dev-push, architecture, deploy READMEs, config comments,
--ref help text, xtask keygen and the dev.yml note point at the command.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 14:50:22 +01:00
..

The team dev key

team.dev.pub — the public half of the key CI signs branch builds with, so robotctl update apply --ref <branch> works on a dev board.

updaterd compiles this file in (updater::verify::BUILTIN_DEV_KEY), always as a dev-only key: every robot carries it, and it counts only on a robot made a dev board with sudo robotctl configure --allow-dev-daemon on. Nobody copies it onto a board for that. updater-design.md §5.4 owns the mechanism.

Not in ../trusted_keys/, deliberately. Every file there is copied onto every robot by scripts/install.sh and trusted as a release key, so a robot would install anything anyone on the team builds. Provisioning still sends this file (provision-board.sh, --no-dev-key declines), which is the path for an updaterd that predates the built-in key.

Committing a public key gives nothing away. Signing a build needs the private half, which lives in ~/.duck-keys and never leaves it.

Regenerating it, if the private half is ever lost — the new public half reaches dev boards with the release built from it, since it is compiled into updaterd:

minisign -R -s ~/.duck-keys/team.dev.key -p team.dev.pub