Skip to content
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

Closed
mtibben opened this issue Mar 6, 2023 · 2 comments
Closed

Issues with the Homebrew distribution #1179

mtibben opened this issue Mar 6, 2023 · 2 comments
Labels

Comments

@mtibben
Copy link
Member

mtibben commented Mar 6, 2023

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 binary

All 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:

  • Double prompts when "Allow"-ing access to the keychain
  • Errors when deleting credentials
  • Different versions aws-vault requiring re-authentication to credentials
  • Messages saying "the authenticity of aws-vault cannot be verified"

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.

@mtibben mtibben pinned this issue Mar 6, 2023
@github-actions
Copy link

github-actions bot commented Sep 6, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Sep 6, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 14, 2023
@mtibben mtibben reopened this Sep 20, 2023
@github-actions github-actions bot removed the stale label Sep 20, 2023
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Mar 19, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant