-
Notifications
You must be signed in to change notification settings - Fork 801
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
Issues with the Homebrew distribution #1179
Labels
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Homebrew distribution does not sign the aws-vault binaries, while the "cask" distribution does.
❌
brew install aws-vault
-> unsigned binary✅
brew install --cask aws-vault
-> signed binaryAll Apple documentation guides the developer to sign binaries when dealing with the keychain, but I am unclear of the exact limitations of these unsigned binaries.
I myself have run into issues when using unsigned binaries with the keychain, however I've struggled to provide concrete examples to the homebrew maintainers.
Issues I've anecdotally seen with the unsigned Homebrew binaries:
These issues are suspected to be caused by the unsigned homebrew binaries
I've previously raised these issues with the maintainers at Homebrew/homebrew-core#84589
My advice is to NOT use the Homebrew distribution, use the cask distribution instead.
The text was updated successfully, but these errors were encountered: