Skip to content

chore(oscap): re-pin CA bundle hash and fixture base-image digests - #134

Merged
egibs merged 1 commit into
mainfrom
update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9
Jul 27, 2026
Merged

chore(oscap): re-pin CA bundle hash and fixture base-image digests#134
egibs merged 1 commit into
mainfrom
update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9

Conversation

@octo-sts-3

@octo-sts-3 octo-sts-3 Bot commented Jul 27, 2026

Copy link
Copy Markdown

CA Certificate + Fixture Base-Image Update

Atomically re-pins three values that must stay in lockstep:

  1. The <ind:hash> under oval:org.CABundleHash:ste:1 in the OSCAP
    datastream (gpos/xml/scap/ssg/content/ssg-chainguard-gpos-ds.xml).
  2. The FROM cgr.dev/chainguard/wolfi-base:latest@sha256:... line in
    every tests/e2e/fixtures/*/Dockerfile.
  3. The pinned wolfi-base digest constant asserted by
    TestParseWolfiBaseRef in tests/oscap-offline/internal/scan/fixtures_test.go.

If these drift (e.g. Dependabot bumps the fixture digest before this
workflow refreshes the datastream hash, or vice versa), the
baseline-clean / cabundle-tampered E2E CertificateAudit check
fails because the fixture's CA bundle no longer matches the hash the
datastream asserts, and the offline harness unit tests break against
the stale test pin. This workflow is the authoritative update point
for all three values together; TestParseWolfiBaseRef was run
against the updated tree before this PR was opened.

  • Image: cgr.dev/chainguard/wolfi-base:latest
  • Digest: sha256:003627df3c1e1bba0c4116afcddb314aca9594ee2328c7e876a8081a6c988b2e
  • New CA SHA256: 61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9
  • Datastream changed: false
  • Fixtures changed: true
  • Test pin changed: true

Atomically updates the CA bundle SHA in the OSCAP datastream, the
digest-pinned FROM lines in tests/e2e/fixtures/*/Dockerfile, and the
pinned wolfi-base digest in the offline harness test
(TestParseWolfiBaseRef) so the three values can never drift out of
sync (which would flake the CertificateAudit E2E assertions or
break the offline unit tests).

Image: cgr.dev/chainguard/wolfi-base:latest
Digest: sha256:003627df3c1e1bba0c4116afcddb314aca9594ee2328c7e876a8081a6c988b2e
CA SHA: 61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9

Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@octo-sts-3 octo-sts-3 Bot added the automated pr This PR was opened by a bot label Jul 27, 2026
@egibs
egibs merged commit 590e81c into main Jul 27, 2026
6 checks passed
@egibs
egibs deleted the update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9 branch July 27, 2026 16:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated pr This PR was opened by a bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant