chore(oscap): re-pin fixture base-image digests - #165
Open
octo-sts-9[bot] wants to merge 1 commit into
Open
Conversation
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:19f7a7b40a11c435311e3784bd134c6b6f19677462440da48f96d5c84eefd669 Stamp image: cgr.dev/chainguard/jre:latest CA SHA: b8d837841b88bfaa1a0fa827cbca8e2576418dd47c9fc4bb7f1f9d89c83111b9 Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
octo-sts-2
Bot
force-pushed
the
update-ca-cert-b8d837841b88bfaa1a0fa827cbca8e2576418dd47c9fc4bb7f1f9d89c83111b9
branch
from
August 27, 2026 02:35
385de03 to
01c197b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixture Base-Image Update
Re-pins two values that must stay in lockstep:
FROM cgr.dev/chainguard/wolfi-base:latest@sha256:...line inevery
tests/e2e/fixtures/*/Dockerfile.pinnedwolfi-base digest constant asserted byTestParseWolfiBaseRefintests/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;
TestParseWolfiBaseRefwas run against the updated tree before thisPR 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). TheVerify trust-store stamp filesstep above asserts both are present and agree, usingcgr.dev/chainguard/jre:latestbecause it carries both, so an imagethat dropped one would fail this run rather than silently red the
E2E CertificateAudit assertions.
cgr.dev/chainguard/wolfi-base:latestsha256:19f7a7b40a11c435311e3784bd134c6b6f19677462440da48f96d5c84eefd669cgr.dev/chainguard/jre:latestsha256:4bd8023f972f81f643dfe2f46f47b05a364b339e1891a6a4c507d349b528fcd2b8d837841b88bfaa1a0fa827cbca8e2576418dd47c9fc4bb7f1f9d89c83111b9truetrue