-
Notifications
You must be signed in to change notification settings - Fork 16
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 1password-cli Formula #2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Biometric Unlock feature requires the CLI to be installed in /usr/local/bin/
as part of the validation the 1Password apps do to validate the authenticity of the binary that connects (https://developer.1password.com/docs/cli/get-started#install).
We'll need to figure out a way forward here that achieves these three things:
- We continue to provide the same security guarantees
- Allow installation via a Brew Formulae (in a different location)
- 1Password apps allow connections via Biometric Unlock
I recommend chatting with @jpcoenen.
Hey @SimonBarendse - Horia's submitted an MR on core that includes the brew formula installation location sandbox exception that's been getting enough approvals. I think we can merge this and begin testing it. We can serve the Cask and formula both in this tap for now while we test - what do you think? |
Looks like merging this may not work. When trying to install the formula via this tap on this branch, I get the following error:
Looking a bit more into this error, it seems that brew is only allowing formula rb files generated by their brew commands due to security reasons:
Of course these pkgs can be still installed via local formula ruby files ( Update: It looks like first adding the tap and then installing the package still works:
Would appreciate if anyone else could confirm this. What I don't understand is how brew is able to figure out to pull the |
Looks like this is no longer the case, and that the 1Password CLI now works fine in |
Closing |
Problem
The current method of downloading the cli using brew conflicts with the cask
1password-cli
that is hosted onhomebrew/cask
.Solution
In order to avoid future conflicts with upgrading the CLI, adding a Formula and specifying the
build-from-source
flag when runningbrew install
will solve that.