Merged
Conversation
Sparkle 2.9 added the ability to verify appcast feeds with the developer's code signature. This adds an extra layer of security so that a supply chain / MITM attack cannot use a compromised appcast feed to show a malicious message. In order to support that, the server needs to serve signed appcasts first or the updated client will reject it. Split the appcast feed into further components so we can add in a signed portion. We now have latest.xml (which is signed), and a new latest_unsigned.xml (which is unsigned). The latest_unsigned.xml should not be used by the client at all and is only used for development purposes, as we need an unsigned version to sign against in the publishing process. From now on every time we want to publish a new appcast or do a slight edit to the release notes we will need to remember to re-sign the appcast.
ychin
added a commit
to ychin/macvim
that referenced
this pull request
Apr 7, 2026
Sparkle 2.9 introduced the ability to verify appcast feeds using a signature. Turn that on to prevent MITM attacks. This requires the appcast on the server side to be re-generated with signature at the end. This was done in macvim-dev/macvim-dev.github.io#5.
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
1 participant
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.
Sparkle 2.9 added the ability to verify appcast feeds with the developer's code signature. This adds an extra layer of security so that a supply chain / MITM attack cannot use a compromised appcast feed to show a malicious message. In order to support that, the server needs to serve signed appcasts first or the updated client will reject it.
Split the appcast feed into further components so we can add in a signed portion. We now have latest.xml (which is signed), and a new latest_unsigned.xml (which is unsigned). The latest_unsigned.xml should not be used by the client at all and is only used for development purposes, as we need an unsigned version to sign against in the publishing process. From now on every time we want to publish a new appcast or do a slight edit to the release notes we will need to remember to re-sign the appcast.
For reference, see https://sparkle-project.org/documentation/#signing-feeds-optional