Skip to content

chore(oscap): re-pin fixture base-image digests - #157

Closed
octo-sts-2[bot] wants to merge 1 commit into
mainfrom
update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9
Closed

chore(oscap): re-pin fixture base-image digests#157
octo-sts-2[bot] wants to merge 1 commit into
mainfrom
update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9

Conversation

@octo-sts-2

@octo-sts-2 octo-sts-2 Bot commented Aug 19, 2026

Copy link
Copy Markdown

Fixture Base-Image Update

Re-pins two values that must stay in lockstep:

  1. The FROM cgr.dev/chainguard/wolfi-base:latest@sha256:... line in
    every tests/e2e/fixtures/*/Dockerfile.
  2. 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 without the
test pin following), the offline harness unit tests break. This
workflow is the authoritative update point for both together;
TestParseWolfiBaseRef was run against the updated tree before this
PR was opened.

CertificateAudit itself no longer pins any hash — the OVAL reads each
expected digest from the stamp file shipped beside the file it
describes inside the scanned image
(/etc/ssl/certs/.ca-certificates.crt.sha256, and on Java images
/etc/ssl/certs/java/.cacerts.sha256). The Verify trust-store stamp files step above asserts both are present and agree, using
cgr.dev/chainguard/jre:latest because it carries both, so an image
that dropped one would fail this run rather than silently red the
E2E CertificateAudit assertions.

  • Image: cgr.dev/chainguard/wolfi-base:latest
  • Digest: sha256:a31344ab2cb8618db84f535eec56f76f6178b142cb92cb2e48676cc2dcebea72
  • Stamp image: cgr.dev/chainguard/jre:latest
  • Stamp image digest: sha256:aca19e6c8e1a5be89d5f28c4c5e0bec09a208ab00d8c6c794b8a8add925b0d08
  • CA SHA256: 61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9
  • Fixtures changed: true
  • Test pin changed: true

@octo-sts-2 octo-sts-2 Bot added the automated pr This PR was opened by a bot label Aug 19, 2026
@octo-sts-2
octo-sts-2 Bot force-pushed the update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9 branch from 42c2b7e to 73ac0d0 Compare August 20, 2026 01:30
@octo-sts
octo-sts Bot force-pushed the update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9 branch 2 times, most recently from 0b52347 to 2f33556 Compare August 21, 2026 22:17
@octo-sts-7
octo-sts-7 Bot force-pushed the update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9 branch from 2f33556 to f0027c6 Compare August 22, 2026 01:30
@octo-sts-2
octo-sts-2 Bot force-pushed the update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9 branch 2 times, most recently from 838c6fe to a3353e9 Compare August 24, 2026 03:40
Re-pins the digest-pinned FROM lines in tests/e2e/fixtures/*/Dockerfile
and the pinned wolfi-base digest in the offline harness test
(TestParseWolfiBaseRef) together, so the two can never drift out of
sync and break the offline unit tests.

Both stamp files CertificateAudit reads were checked first, on
cgr.dev/chainguard/jre:latest: the CA bundle matches
/etc/ssl/certs/.ca-certificates.crt.sha256 and the Java truststore
matches /etc/ssl/certs/java/.cacerts.sha256.

Image: cgr.dev/chainguard/wolfi-base:latest
Digest: sha256:a31344ab2cb8618db84f535eec56f76f6178b142cb92cb2e48676cc2dcebea72
Stamp image: cgr.dev/chainguard/jre:latest
CA SHA: 61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9

Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@octo-sts
octo-sts Bot force-pushed the update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9 branch from a3353e9 to 4ba2cc8 Compare August 24, 2026 18:23
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