Repository navigation
v0.1.32
⚠️ Isolation suites were not run for this tag
The Cilium packet-level suite and the Kata boot probe did not execute, so
tenant isolation is unverified and the control and guest image digests
were not verified by them. This release continues only because a
workflow_dispatch run set isolation_skip=true (acknowledgement none):
a tag push cannot take this path.
Set SANDBOX_ISOLATION_RUNNER and re-run the release without the skip
input. See docs/release-process.md#isolation-gate.
What's Changed
- feat: a create kill switch that does not stop live sessions by @ejackson-vp in #224
- feat: Postgres PITR to an object store, with a drill that was actually run by @ejackson-vp in #228
- docs(security): close F-19 and the Kata row in the gate by @ejackson-vp in #229
- docs(site): beta copy that states what is and is not proven by @ejackson-vp in #232
- test(security): let the probe pod pull the image the cluster runs by @ejackson-vp in #230
- cleanup(shared,sdk,cli): one implementation each, and a smaller SDK by @ejackson-vp in #235
- cleanup(api): one definition per repeated answer by @ejackson-vp in #237
- test(security): assert a usable Retry-After, not a boolean by @ejackson-vp in #238
- cleanup(controller): one reader per shape, one decision per question by @ejackson-vp in #236
- cleanup: delete nothing that is used, and correct the docs that drifted by @ejackson-vp in #234
- fix: a tag cannot pin a different release, and bumping is one command by @ejackson-vp in #231
- fix(test): make SIGSTOP observable before a frame is forwarded by @ejackson-vp in #240
- test(property): generate unique settlement nonces by @ejackson-vp in #239
- docs(orr): record the one alert delivery that happened by @ejackson-vp in #233
- release: allow a lagging guest, and pin 0.1.32 by @ejackson-vp in #241
Full Changelog: v0.1.31...v0.1.32
Images
Multi-arch (linux/amd64, linux/arm64), published to GHCR:
ghcr.io/ejackson-vp/sandbox-control:v0.1.32ghcr.io/ejackson-vp/sandbox-guest:v0.1.32
These tags were created only after both images passed the Trivy
gate. Each image carries an SBOM and SLSA build provenance as OCI
attestations:
docker buildx imagetools inspect ghcr.io/ejackson-vp/sandbox-control:v0.1.32Verifying provenance
The *.sigstore.json assets are keyless Sigstore bundles produced by
this workflow, covering exactly the digests above. Verify the image
itself:
gh attestation verify \
oci://ghcr.io/ejackson-vp/sandbox-control:v0.1.32 \
--repo ejackson-vp/sandboxAdd --bundle-from-oci to check the attestation stored in the
registry instead of the one on GitHub.
*.intoto.jsonl is the in-toto statement carried inside the bundle,
for SLSA tooling that consumes statements rather than bundles.
The guest image is what runs inside the microVM and must match the
cluster architecture. CVE results for this tag are in the Security
tab (trivy-control, trivy-guest).
Staging images from the build (staging-<run-id>-<sha>) are not
release artifacts; see docs/release-process.md for cleanup.