Keep signing keys outside the build workspace
The build job receives an exportable private key file that any build script could read or include in the archive.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Key isolation · Provider interfaces · Signing
Estimated field mix
- DevOps70%
- Security30%
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
A fictional command-line product publishes local package archives. Builds contain timestamps, checksums are copied without provenance, and cleanup can delete the only rollback artifact. Use generated source trees, ephemeral development signing keys, and local object storage; no public registry or production key is supplied.
Setup prerequisites
- Content hashing
- Archive formats
- Release metadata
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Build produces an unsigned digest and signing request
- Signing provider accepts only authorized artifact metadata
- Private key bytes never enter workspace, logs, or artifacts
Implementation constraints
- Use ephemeral local keys behind a provider interface; production key management remains unprovisioned.
Verification to include
- Sign and verify an authorized fixture artifact.
- Search outputs for a sentinel key and reject an unauthorized digest request.
Deliverables
- Signing-provider boundary and leak tests
Rollout and recovery
Keep unsigned artifacts nonpromotable while the development signer is enabled.
Value of the work
For the engineer: Practice reproducible artifacts, provenance validation, signing-key isolation and retention safety.
For the team: Review a supply path that can trace, verify, retain, and revoke artifacts without relying on mutable names.
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.