Repository navigation
fix(docker): bump chainguard/git base to drop emSign ECC Root CA - G3 - #465
Merged
Merged
Conversation
The pinned digest's ca-certificates still trusts emSign ECC Root CA - G3, which Mozilla removed after eMudhra's G3 intermediates were found to have trivially recoverable private keys (Mozilla bug 2083449). The current chainguard/git image no longer ships it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SUSTAPLE117
force-pushed
the
fix/chainguard-git-drop-emsign-g3
branch
from
October 21, 2026 13:20
3560fc9 to
164f6f1
Compare
fproulx-boostsecurity
approved these changes
Oct 21, 2026
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
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.
The poutine image pins
cgr.dev/chainguard/gitto a digest whoseca-certificatesstill trusts emSign ECC Root CA - G3. Mozilla removed that root after it emerged that eMudhra's eight G3 intermediates were issued with P-384 private keys under 256, so anyone can recover them (bug 2083449, write-up, PoC). poutine runsgitand Go HTTPS clients inside this image, and neither enforces Certificate Transparency, so either one could be MITMed with a cert minted under those keys.This PR bumps the digest in both places it is pinned (
Dockerfile,.goreleaser.yamlkos) to the currentchainguard/git:latest.Here is what I checked in
/etc/ssl/certs/ca-certificates.crt:06119871…62087eb4…(amd64 + arm64)G1 matches Mozilla's decision to keep it.
docker build .fails onmainbefore this change, and fails the same way with it. The pinned goreleaser v2.3.1 rejectsformatsat.goreleaser.yamlline 69. I left that alone because released images come fromkos.🤖 Generated with Claude Code