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

Windows SmartScreen: Jamulus Code Signing #785

Closed
ann0see opened this issue Dec 15, 2020 · 6 comments
Closed

Windows SmartScreen: Jamulus Code Signing #785

ann0see opened this issue Dec 15, 2020 · 6 comments

Comments

@ann0see
Copy link
Member

ann0see commented Dec 15, 2020

Currently, if you install Jamulus on Windows, SmartScreen warns you on Windows 10 (Error: This software might harm your PC). MS Edge even blocks the download.

This evokes a bad impression especially for new users.

Due to the frequent release cycle there’s no way Jamulus might get on SmartScreen‘s list of known hardware software.

There are two options to solve this issue:

  1. Buy an overly expensive code signing certificate although there‘s something like https://www.certum.eu/en/code-signing-certificates/
  2. Make one installer which downloads the latest version of Jamulus and after some time will be downloaded enough times to get on the whitelist. The installer of Jamulus should be able to do online installs, I think. This would also allow us to do a few pre-checks (e.g. is an ASIO Driver installed?)

Related
#550 macOS

@ann0see ann0see changed the title Jamulus Code Signing (SmartScreen) Windows SmartScreen: Jamulus Code Signing Dec 15, 2020
@pljones
Copy link
Collaborator

pljones commented Dec 17, 2020

If this kicks off (point 2, I suppose), then it and #738 should be done together, I suppose. No point getting it right in one then binning it and getting it wrong in the other...

My Windows scripting is too ancient to pick this up, unfortunately. (Even for #738 it should be redone in a more modern manner whilst retaining the flexibility.)

@gilgongo
Copy link
Member

Is there a suggestion that Microsoft may have whitelisted the installer now?

@ann0see
Copy link
Member Author

ann0see commented Dec 31, 2020

Probably. But only the current version. Once we have a new release it starts again

@corrados
Copy link
Contributor

corrados commented Jan 3, 2021

Isn't this very much related to #550? I don't want to have two issue with the same topic. Can we close one of these?

@ann0see
Copy link
Member Author

ann0see commented Jan 3, 2021

This issue focuses on Windows, while the other focuses on macOS. We might have to handle it differently

@gilgongo
Copy link
Member

Please continue with any further thoughts here #1042

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

4 participants