Pin the bundled CA certificates to a dated curl release - #541
Merged
Merged
Conversation
The moving cacert.pem fails checksum verification whenever curl publishes a new bundle.
LouisLotter
approved these changes
Oct 1, 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
2 participants
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.
DEB package builds are failing on every branch: the
cacertsrecipe downloads the movinghttps://curl.se/ca/cacert.pemagainst a pinned SHA-256, and curl published a new bundle on 2026-09-25. This pins the dated releasecacert-2026-09-25.peminstead. Its checksum matches curl's published.sha256, and it's the same content as today'scacert.pem. New curl releases no longer break builds; updating the bundle becomes a deliberate change of version and checksum.Fixes #540
Validation: the recipe parses (
ruby -c). The DEB package build on this branch is the real check.🤖 Generated with Claude Code