Commit 621f03c
committed
Sign appcast feed
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.1 parent c41bf02 commit 621f03c
4 files changed
Lines changed: 20 additions & 11 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
4 | | - | |
5 | | - | |
6 | | - | |
7 | | - | |
8 | | - | |
9 | | - | |
10 | | - | |
11 | | - | |
12 | | - | |
13 | | - | |
| 3 | + | |
| 4 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
0 commit comments