SparkleProject/sparkle-project.github.io
1
0
Fork 0
mirror of https://github.com/sparkle-project/sparkle-project.github.io.git synced 2025-11-01 15:35:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove .sh from tool names

Browse Source
This commit is contained in:
Zorg
2015-08-29 10:05:24 -04:00
parent 4cc0c88be1
commit bdf3736016
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/index.md
+1 -1
View File
@@ -57,7 +57,7 @@ If you are using [CocoaPods](https://cocoapods.org), then follow these [alternat
* If you are specifying a DSA signature of your update's archive:
* First, make yourself a pair of DSA keys; Sparkle includes a tool to help:
* (from the Sparkle distribution root):<br />
<code>./bin/generate_keys.sh</code>
<code>./bin/generate_keys</code>
* You can use the keys this tool generates to sign your updates.
* Back up your private key (dsa_priv.pem) and <strong>keep it safe.</strong> You don't want anyone else getting it, and if you lose it, you may not be able to issue any new updates.
* Add your public key (dsa_pub.pem) to the Resources folder of your Xcode project.
documentation/publishing/index.md
+1 -1
View File
@@ -19,7 +19,7 @@ In order to prevent corruption and man-in-the-middle attacks against your users,
To cryptographically sign your updates, Sparkle includes a script to help you make a DSA signature of the archive. From the Sparkle distribution:
./bin/sign_update.sh path_to_your_update.zip path_to_your_dsa_priv.pem
./bin/sign_update path_to_your_update.zip path_to_your_dsa_priv.pem
The output string is your update's DSA signature; you'll add this as an attribute to your enclosure in the next step. You can remove any newlines in this string.