-
Notifications
You must be signed in to change notification settings - Fork 14
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
Deliver macOS binaries in a way that doesn't require security overrides #280
Comments
This allegedly removes the warning |
I think we may need to create and sign an installer--not the binary itself. |
I decided to download the pre-built macOS Apple Silicon binary for the Oxide CLI from: In the macOS Terminal window, I verified the checksum with Then still in the macOS Terminal window, I immediately tried to run Since the Since I am familiar with security exceptions and I will just assume the Then I went back to my Terminal window and was able to proceed with However, there is very little (no) documentation on what to do with the pre-built binaries, especially in this case of macOS, as the user needs to know the magic trick to do the security exception (there are other ways, but the Finder is the easiest), which may be a bit alarming for the user, as it shows many warnings about untrusted/malicious developer(s). I'm running Little Snitch, and it gives me some more warnings when I try to do In case we're interested, it looks like it is 99 USD/year to have the ability to sign the binary. The Quick Start is not so quick so far, because I have to do a bunch of undocumented steps before I can start: https://docs.oxide.computer/cli/guides/quickstart |
This might mean signing the binary, but I notice that binaries installed by Homebrew aren't signed. We may need to provide instructions for downloading and installing the cli in a way that doesn't incur the security red flags.
The text was updated successfully, but these errors were encountered: