Package Details: 1password-cli 2.27.0-1

Git Clone URL: https://aur.archlinux.org/1password-cli.git (read-only, click to copy)
Package Base: 1password-cli
Description: 1Password command line tool
Upstream URL: https://app-updates.agilebits.com/product_history/CLI2
Keywords: 1password
Licenses: custom
Submitter: Sh4rk
Maintainer: slurpee
Last Packager: slurpee
Votes: 42
Popularity: 0.85
First Submitted: 2017-09-07 18:54 (UTC)
Last Updated: 2024-04-19 08:22 (UTC)

Pinned Comments

slurpee commented on 2022-03-22 11:18 (UTC) (edited on 2024-01-21 23:34 (UTC) by slurpee)

As of the 2.24.0-2 release, Zsh shell completion is no longer provided by the package to mirror the official packages. Users that wish to use shell completion can add a line to their shell's dotfile.

See the official docs for instructions specific to your shell: https://developer.1password.com/docs/cli/reference/commands/completion/

It is recommended to verify the authenticity of the binary by using Agilebits's PGP code signing key. Their public key ID is published in the install documentation.

gpg --receive-keys 3FEF9748469ADBE15DA7CA80AC2D62742012EA22

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Auerhuhn commented on 2019-05-29 09:59 (UTC)

@kurtmc Done. Thanks for the heads up.

kurtmc commented on 2019-05-22 03:26 (UTC)

@Auerhuhn any chance of updating the version (to 0.5.6-003) and checksums?

Auerhuhn commented on 2019-05-01 09:10 (UTC) (edited on 2019-05-01 09:11 (UTC) by Auerhuhn)

Thanks @myveo for the heads up. I’ve reached out to Connor from AgileBits [1]. I will update the package once they confirm that the change is legit.

[1] https://discussions.agilebits.com/discussion/comment/503735/#Comment_503735

myveo commented on 2019-05-01 08:18 (UTC) (edited on 2019-05-01 08:18 (UTC) by myveo)

Looks like cheksums are outdated. At least the checksum for the amd64 archive (i.e. op_linux_amd64_v0.5.5.zip) should be 5ddc73a573f008758d1765169cc4f28371742231cb6aadad6ebd9620f229ccb4.

Auerhuhn commented on 2018-07-01 15:54 (UTC)

Thanks @ddnomad for your suggestion.

You can configure GnuPG to auto-import public keys if that’s what you want. To do that, add a line to ~/.gnupg/gpg.conf that says: keyserver-options auto-key-retrieve. I wouldn’t recommend this though.

As a more secure alternative, I’d encourage everyone to import 1Password’s public key. I have added a pinned comment to explain how. Thanks again for the pointer!

Auerhuhn commented on 2018-07-01 15:53 (UTC)

You may want to first import 1Password’s PGP code signing key:

gpg --recv-keys 3FEF9748469ADBE15DA7CA80AC2D62742012EA22

To confirm the key is legit, see this comment by 1Password’s Jeffrey Goldberg:

https://discussions.agilebits.com/discussion/comment/420654/#Comment_420654

ddnomad commented on 2018-07-01 13:59 (UTC) (edited on 2018-07-01 13:59 (UTC) by ddnomad) 

gpg: Can't check signature: No public key

Not sure I should import the key manually. IMO the pkgbuild should handle this.

mprom commented on 2018-06-15 11:13 (UTC)

The check() step of the PKGBUILD gives an error if you haven't set GPG up. Removing it from PKGBUILD seems to have worked.

Auerhuhn commented on 2018-06-04 15:27 (UTC) (edited on 2018-06-04 15:28 (UTC) by Auerhuhn)

According to AgileBits [1] the modification is legit. I have now updated the signatures and bumped the package to v0.4.1, pkgrel 2. See commit message for full details.

Thanks again @chopps for reporting!

[1] https://discussions.agilebits.com/discussion/comment/438011/#Comment_438011

« First ‹ Previous 1 2 3 4 5 6 Next › Last »