Repository navigation
Encompute 0.3.3
0.3.3 is the first completed, supported security update for the vulnerable 0.3.0 line. Upgrade from 0.3.0 (and from the 0.3.0 release candidates) to 0.3.3. It contains the control-plane fixes for privacy-ledger and revocation rollback (ENC-SF-2026-326, 329, 411, 412 and 413), the refreshed container base images, and a corrected release pipeline.
Use 0.3.3, not 0.3.1 or 0.3.2
0.3.1 and 0.3.2 were failed release attempts. Neither produced a GitHub release or signed release artifacts. Their tags (v0.3.1, v0.3.2) are immutable and kept as evidence, and the public container image tags 0.3.1 and 0.3.2 belong to those attempts: do not use them. The product code in 0.3.3 is the same as in those attempts. What changed is the release pipeline and its tests (a corrected shared test helper that proves the adversarial window or fails loudly, a nonpublishing rehearsal of the whole release path, a reproducible dependency lock).
What this release protects against, and what it does not
The threat model is a database writer (a database operator or a compromised database account) who can write while the control plane runs but has neither the control plane's signing key nor the external anchor store. 0.3.3 acknowledges a privacy spend, a ledger registration or a revocation, disable, cancellation, withdrawal or removal only when the external anchor holds exactly what the call committed, refuses spends on a ledger whose genesis the anchor does not hold, and checks the database against the anchored state before every request.
It does not provide comprehensive protection against every form of database-administrator compromise. Not covered: the database and the anchor restored together to an older consistent state; compromise of the signing key or of the anchor's custodian; authority recreated under a new record id; the time a request already past its check can be held (the in-transaction revalidation narrows this and does not close it); and a genesis that 0.3.0 already anchored, which is not repaired. There is no supported downgrade to 0.3.0.
Upgrading
Follow Upgrading from 0.3.0 to 0.3.3: back up the database and the independently held anchor first, review every ledger's genesis against the owner's records before running anchor-ledgers (with the service stopped), and expect ledgers that were never anchored to refuse spends until then.
Verifying
Follow verify-release.md with the tag v0.3.3: checksums, cosign signatures and GitHub attestations. The Linux binaries in this release were checked against the digests the release gate reproduced (the release workflow refuses to sign otherwise). Full notes: release-notes-0.3.3.md, CHANGELOG.
Built by the release workflow from b76a84690b26e0ebcdfeae4ba0adc33ad58454bf.
Container images (by digest):
ghcr.io/bader82t/encompute-evaluator@sha256:a28d8c5387cf556d96cd7edb3d348b54388a4d18e7e9ad679ffca99633632ab6
ghcr.io/bader82t/encompute-control@sha256:d95e4e44b5fdf9f1853072490963e6ef3d77c718bbee0d21629a50bc681f996b
ghcr.io/bader82t/encompute-services@sha256:d27544929cb80b84c7f32a48dd9cbe5a9a5fbdb9b27ec0f3d081c55326a2b2d7
Confidential Space workload images (by digest; the digests key brokers approve):
ghcr.io/bader82t/encompute-confidential-space@sha256:60b1a9d19f054b87c8eea328772aaea5770ba9340c6e402032c8d904621a8225
ghcr.io/bader82t/encompute-training@sha256:29dd67b3b542abd4aa70129567dd76a1ef39232e0d649e7e99e4f7c6b8d7964a