Update to new Code Signing Certificate 2017 #3499
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is a screenshot on MacOS if you try to install a binary WITHOUT code signing. It's not possible. |
|
This is a screenshot (thanks @Siedlerchr ) when you try to install an entirely unsigned .exe on windows. |
1 task
6 tasks
|
I'll close this now, as the certificate does not seem to be accepted by the major operating systems. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Works for me on MacOS, but there's a problem with Windows: The root certificate (TeleSec) is not configured to allow code signing per default. The user could, in theory, change that, but well... who does that.
This solution: Don't sign Windows, sign Macos.
Test binaries: http://builds.jabref.org/new-cert