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

feature request - upgrading and proper signing #40

Open
joeblew99 opened this issue Nov 17, 2016 · 0 comments
Open

feature request - upgrading and proper signing #40

joeblew99 opened this issue Nov 17, 2016 · 0 comments

Comments

@joeblew99
Copy link

This request follows on from the PKG bundling request.

With the package properly signed using the OSX toolset, it means we can do upgrades that are secure and tamper proof that check the signing.

There are many golang updaters out there that have various features btw, but this one looks good:
https://github.com/syncthing/syncthing/tree/master/lib/upgrade

  • Checks signatures
  • Battle Tested (handles allot of corner cases)
  • Manages version checking.
  • Tests

Also check this:
https://github.com/syncthing/syncthing/blob/master/build.go
Its a nice way to do it. The golang team does the same with a root build.go.

Lastly between the bundling and the upgrading we need to upload the bundle somewhere:
https://github.com/golang/build/blob/master/cmd/release/upload.go

I think that this makes it very easy to bundle and deploy and because its all golang based easy to fix and cross platform.

Curious what you think and any things you want changed etc ?

@joeblew99 joeblew99 changed the title feature request - TOA upgrading and proper signing feature request - upgrading and proper signing Nov 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant