Validate edge-update manifests using local trust fixtures
The simulator accepts any manifest signature. Add a trust adapter using ephemeral development keys.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Cryptography · Provider interfaces
Estimated field mix
- Security70%
- Embedded and edge30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional information kiosks receive small generated image blobs through a local update adapter. Simulate slots and boot outcomes in software; do not flash hardware or execute image contents.
Setup prerequisites
- Generate inert byte images with manifests and development-only signing fixtures.
- Implement simulated boot success failure and power-cut points.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Trusted fixture signature passes
- Unknown signer fails
- Tampered manifest fails
Implementation constraints
- No private keys enter source control or production configuration.
Verification to include
- Verify local signed fixture
- Change signed manifest field
Deliverables
- Trust adapter and negative cases
Rollout and recovery
Disable update acceptance if trusted verification is unavailable.
Value of the work
For the engineer: Practice update state machines and recoverable activation.
For the team: Inspect whether an engineer can prevent partial rollout from stranding devices under declared conditions.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.