← ClaudeAtlas

espos-keys-ota-fleetlisted

Signing keys, OTA and fleet updates for espOS devices. Dev vs named vs CI signing keys and why a wrong key strands OTA, the device OTA flow and manifest, the P4's radio co-processor update, listing a firmware in the signalk-espOS registry, and how signalk-espos-manager flashes, discovers, authenticates (fleet API key) and updates a boat's devices.
signalk-espOS/skills · ★ 0 · API & Backend · score 72
Install: claude install-skill signalk-espOS/skills
# Keys, OTA and keeping a fleet current Verified against espOS v0.24.0, registry `schema: 1`, signalk-espos-manager 0.8.0, October 2026. Sources: `espOS/docs/ota.md`, `espOS/docs/security.md`, `espOS/docs/hardware.md`, `registry/README.md`, `registry/schema/*.schema.json`, manager `README.md` and `src/`. ## Two different "keys": do not conflate them | | Firmware **signing key** | **Fleet key** | |---|---|---| | What | RSA-3072 (Secure Boot V2 scheme) private key, one per firmware project | One HTTP API Bearer key for every espOS device on a boat | | Where | CI secret (`SIGNING_KEY_PEM`, or a project-named one such as `COCKPIT_SIGNING_KEY_PEM`, `N2K_GATEWAY_SIGNING_KEY_PEM`); locally `secure_boot_signing_key.pem`, git-ignored | Manager setting `auth.fleetKey`, managed on the webapp's Devices page; per-device keys in `<dataDir>/keys.json` (0600) | | On the device | the public key compiled into the **running** app; `esp_ota_end` checks against it | `httpd.api_key`; espOS httpd takes `Authorization: Bearer <key>` or the `espos_sid` cookie | | Lose / change it | Every fielded device refuses OTA, so each needs a USB reflash | Tell the manager and the devices the new one | Whoever builds a firmware owns its signing key. One key may sign several projects: measured from the release images in October 2026, the cockpit and the BLE gateway share key `b3381b48b9cc9941`, while the third-party 8relay uses `c21a11df97bc7699`. A third party who wants their own build on their own boat gene