-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add code signing for Mac builds #251
Comments
There is https://github.com/pyinstaller/pyinstaller/wiki/Recipe-OSX-Code-Signing I imagine this means
|
Seems pretty straight forward. Can we have items in travis though that aren't in the repo? I'm not that familiar with travis. I ask because on concern I have is where the cert is located. Having the .p12 and the pass for it in the repo sort of defeats the purpose of it. :) If you don't know off hand I can do some research on it and on how other open source projects handle it. |
https://docs.travis-ci.com/user/encrypting-files/ describes how encrypted files are supported so you would store the encrypted cert in the repo and decrypt at build time |
@3ll3d00d Since I have my personal dev account active again for BEQBrowser I started looking at revising this issue. The first launch hoops are a bit annoying. Doing it with the GitHub actions looks to be pretty easy. I can generate the certs for you if you want to make the project secrets with them and add the task. Here's a guide on what needs to be done: https://localazy.com/blog/how-to-automatically-sign-macos-apps-using-github-actions To nutshell it, I creates the certs, we make a secrete with them and a password. Then add the task:
|
At some point we should add code signing to the mac build. Currently on first launch of each version the system blocks it from launching. The user then has to go into the security system preferences to allow it to be run. It's not difficult but it is an unneeded barrier.
Things to investigate:
The text was updated successfully, but these errors were encountered: