Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sparkle support #50

Closed
kasper opened this issue Nov 23, 2015 · 6 comments
Closed

Sparkle support #50

kasper opened this issue Nov 23, 2015 · 6 comments
Assignees
Labels
Milestone

Comments

@kasper
Copy link
Owner

kasper commented Nov 23, 2015

Use Sparkle-framework (with CocoaPods) to enable automatic software updates.

@kasper kasper added the feature label Nov 23, 2015
@kasper kasper self-assigned this Nov 23, 2015
@kasper kasper added this to the 2.0 milestone Nov 23, 2015
@kasper
Copy link
Owner Author

kasper commented Nov 25, 2015

We can probably use GitHub for the appcast. I’m working on this and I think this will be the last feature to be included into 2.0 before release.

@jasonm23
Copy link
Contributor

Ok sounds good

On 26 Nov 2015, at 2:40 AM, Kasper Hirvikoski notifications@github.com wrote:

We can probably use GitHub for the appcast. I’m working on this and I think this will be the last feature to be included to 2.0 before release.


Reply to this email directly or view it on GitHub.

kasper added a commit that referenced this issue Nov 26, 2015
@kasper
Copy link
Owner Author

kasper commented Nov 26, 2015

Since Sparkle is downloading executable code to users’ systems, here’s a security check that we will conform to http://sparkle-project.org/documentation/#segue-for-security-concerns:

  • We will be serving the appcast over https through this repository
  • We will be serving the updates over https through GitHub releases
  • Phoenix will be signed with my Apple Developer ID to retain integrity
  • Update archives will be signed with a DSA signature
  • It should be fine to keep the DSA public key in this repository
  • I will keep the DSA private key secure and share when required

Sparkle support should be implemented in the add-sparkle-support-branch. I’ll test it out before merging.

@jasonm23
Copy link
Contributor

Sounds good

On 26 Nov 2015, at 8:06 PM, Kasper Hirvikoski notifications@github.com wrote:

Since Sparkle is downloading executable code to users’ systems, here’s a security check that we will conform to http://sparkle-project.org/documentation/#segue-for-security-concerns:

We will be serving the appcast over https through this repository
We will be serving the updates over https through GitHub releases
Phoenix will be signed with my Apple Developer ID to retain integrity
Update archives will be signed with a DSA signature
It should be fine to keep the DSA public key in this repository
I will keep the DSA private key secure and share when required
Sparkle support should be implemented in the add-sparkle-support-branch. I’ll test it out before merging.


Reply to this email directly or view it on GitHub.

kasper added a commit that referenced this issue Nov 26, 2015
kasper added a commit that referenced this issue Nov 26, 2015
kasper added a commit that referenced this issue Nov 26, 2015
@kasper
Copy link
Owner Author

kasper commented Nov 26, 2015

Well look at that! Sparkle support is integrated, tested and ready for the launch. :)

@kasper kasper closed this as completed Nov 26, 2015
@jasonm23
Copy link
Contributor

Decent :) 👍

On 26 Nov 2015, at 11:52 PM, Kasper Hirvikoski notifications@github.com wrote:

Closed #50.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants