-
Notifications
You must be signed in to change notification settings - Fork 222
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
Comments
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.) |
Is there a suggestion that Microsoft may have whitelisted the installer now? |
Probably. But only the current version. Once we have a new release it starts again |
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? |
This issue focuses on Windows, while the other focuses on macOS. We might have to handle it differently |
Please continue with any further thoughts here #1042 |
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
hardwaresoftware.There are two options to solve this issue:
Related
#550 macOS
The text was updated successfully, but these errors were encountered: