Bump Sparkle to 2.9.6 for upstream security fixes - #40
Merged
Conversation
2.9.5 predates two security fixes upstream ships in 2.9.6: hardened handling of the downloaded archive during install, and removal of the root-owned cache directory usage that could be abused for local privilege escalation on processes running Sparkle as root. Bumps the pinned SPM package in project.yml and the checksum-verified CLI download in install-ci-tools.sh together, per the existing version/checksum pinning convention.
Owner
|
Thanks — checksum verified against the upstream asset, and both pins moved together. CI approved; merging once it is green, ships in tomorrow's release. |
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.
Summary
project.ymlpins the Sparkle SPM package at2.9.5, andscripts/install-ci-tools.shpins the matchingsign_updatedownload at the same version+checksum.2.9.6together, following the existing "keep in sync" convention already enforced by the version-match check at the top ofinstall-ci-tools.sh.Test plan
scripts/install-ci-tools.shlocally end to end — the newSPARKLE_SHA256value verifies against the actualSparkle-2.9.6.tar.xzrelease asset andsign_updateextracts successfully.ci.yml) build/test/lint on this PR.