-
Notifications
You must be signed in to change notification settings - Fork 277
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
[BUG] MCAL 1.4 dmg Is Not Code Signed #5817
Comments
@joshmc82 & @jonbartels Thanks for bringing this up! We have added a note about it to the Upgrade Guide as well so that users will hopefully not have to go looking for this GitHub item to know how to work around it. As that note says, we may be addressing this in our next release. Thanks again! |
Perhaps worth adding that if you download the stand-alone tar.gz file, the launcher executable is not signed in that package and will result in the same security issue. |
@joshmc82 your workaround is not correct. It should be |
Good catch. Edited the OP for clarity. |
Previously reported on 1.3.0 #5575 |
Describe the bug
The MCAL 1.4 dmg file for MacOS is not code signed and causes errors trying to launch.
To Reproduce
Setup steps (if required). Example:
Steps to reproduce the behavior:
Expected behavior
The dmg file itself should be signed like the underlying app
Actual behavior
The dmg is not signed and produces an error from MacOS
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Workaround(s)
Hold ctrl key then click the dmg to open it. This bypasses the security check.
Additional context
It should be pretty easy to sign the dmg the same way you sign the app itself.
Reference: https://stackoverflow.com/questions/23824815/how-to-add-codesigning-to-dmg-file-in-mac
The text was updated successfully, but these errors were encountered: