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

Unsigned Installers #273

Open
1 of 6 tasks
trevorboydsmith opened this issue May 3, 2016 · 8 comments
Open
1 of 6 tasks

Unsigned Installers #273

trevorboydsmith opened this issue May 3, 2016 · 8 comments

Comments

@trevorboydsmith
Copy link

trevorboydsmith commented May 3, 2016

the most recent version 1.0.2 installer is not signed and when you install under windows 10 you get a popup complaining about "unknown" source.

if possible it might be good to add "signing" of the code as an additional step for your build on windows 10.

(personally this is low priority. I personally do not have issues clicking "ok" when presented with a dialog from windows 10 complaining about unsigned code but other users may.)

if signing the code is too bothersome somehow, then maybe providing an md5sum hash that users can use to check against.


Status

  • Known Issue
  • Documented Workaround(s)
  • Documented Code Location(s)
  • Priority Established
  • Bounty Attached
  • Developer Assigned

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@blurymind

This comment has been minimized.

@trevorboydsmith

This comment has been minimized.

@RodneyBaker

This comment has been minimized.

@ghost ghost changed the title version 1.0.2 is not signed Installers are not signed Aug 29, 2016
@ghost

This comment has been minimized.

@RodneyBaker

This comment has been minimized.

@RodneyBaker
Copy link
Collaborator

Is a signed license something that just needs to be funded? As in purchasing a certificate or certificate granting autorization? If that is the case we mostly just need to know how much it would cost to consider whether to move forward.

@RodneyBaker

This comment has been minimized.

@artisteacher
Copy link
Contributor

MacOS has the same issue. This has to turn off some users over fears of security risks. It also makes it a little bit more of a hassle to install.

On the mac side, to release a signed app, you need to be part of the Apple Developer Program. There's a $99 yearly fee. The fee can be waived in some cases. It would certainly be worth it to apply for the waiver in case we qualify.

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

No branches or pull requests

5 participants