Skip to content

fix: build with Go 1.26.10 for the eMudhra CA compromise - #916

Merged
barnabasbusa merged 2 commits into
masterfrom
bbusa/emudhra-ca-fix
Oct 21, 2026
Merged

barnabasbusa merged 2 commits into
masterfrom
bbusa/emudhra-ca-fix

Conversation

@barnabasbusa

Copy link
Copy Markdown
Collaborator

Eight eMudhra intermediate CA private keys were compromised (Mozilla, Google), and Go 1.26.10/1.27.3 ship the crypto/x509 fix, so every binary built with an older toolchain still trusts certificates minted with those keys. This raises the go.mod minimum to go 1.26.10, so Docker, goreleaser and CI builds can no longer silently use an older toolchain, and moves pinned or pre-1.26 golang builder images and setup-go versions to match.

@redpandabot redpandabot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bumps the Go toolchain floor from 1.26.8 to 1.26.10 in go.mod and the Dockerfile builder image so builds pick up the crypto/x509 fix for the compromised eMudhra intermediates. The two files remain mutually consistent, CI's floating 1.26.x pins resolve to at least 1.26.10, and no dependencies changed. Nothing to fix.


Reviewed 2 changed file(s) @ b3e106ce — no blocking issues found.
"The most effective debugging tool is still careful thought, coupled with judiciously placed print statements." — Brian Kernighan

@samcm samcm left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the Go 1.26.10 bump: versions, image tags and pins check out.

@barnabasbusa
barnabasbusa merged commit bcbff3e into master Oct 21, 2026
8 of 9 checks passed
@barnabasbusa
barnabasbusa deleted the bbusa/emudhra-ca-fix branch October 21, 2026 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants