-
Notifications
You must be signed in to change notification settings - Fork 42
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
Please sign macOS binaries #148
Comments
This is not fixed by 174. We are getting dcrinstall signed and notarized for macos in this release, but the regular archive of unsigned executables will not run if you downloaded them from a browser. |
They will run, but you have to manually open (using right click or command click - double click will not work) all the executables and individually approve it (macOS will prompt for admin user/password) to get it around the built in security measures. Not an elegant look or approach for such a classy project ;P |
dcrinstall is properly signed and notarized and it can be used to install all of the remaining decred cli tools to ~/decred. There has been some talk about extending our macos .pkg files to install the entire decred distribution, rather than only installing dcrinstall and requiring the user to run it as an extra step, but that has not happened yet. One major annoyance for us is that signing the binaries breaks the build reproducibility, even if you remove the added signature you don't get the same file back. |
Here is a general solution to making reproducible builds for open source projects: https://stackoverflow.com/a/70836033/300224 |
Affected version 1.4.0.
Currently there is a "unidentified developer" warning. This is an unacceptable shortcoming for applications that involve physical health or monetary value.
The text was updated successfully, but these errors were encountered: