Skip to content

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

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

chore(oscap): re-pin CA bundle hash and fixture base-image digests#95
octo-sts-5[bot] wants to merge 1 commit into
mainfrom
update-ca-cert-61efbd6d3f829f71039c57b29dd37d15ac7f33c4ece861aaef8c7d7a519cd1d9

Conversation

@octo-sts-5
Copy link
Copy Markdown

@octo-sts-5 octo-sts-5 Bot commented May 18, 2026

CA Certificate + Fixture Base-Image Update

Atomically re-pins two 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.

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. This workflow is now the authoritative update
point for both values together.

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

Atomically updates the CA bundle SHA in the OSCAP datastream and the
digest-pinned FROM lines in tests/e2e/fixtures/*/Dockerfile so the
two values can never drift out of sync (which would flake the
CertificateAudit E2E assertions).

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

Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@octo-sts-5 octo-sts-5 Bot added the automated pr This PR was opened by a bot label May 18, 2026
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