Package Details: 1password-cli 2.31.1-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: 47
Popularity: 0.57
First Submitted: 2017-09-07 18:54 (UTC)
Last Updated: 2025-07-10 04:48 (UTC)

Pinned Comments

slurpee commented on 2022-03-22 11:18 (UTC) (edited on 2025-07-10 04:49 (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. Agilebits recently renewed their PGP key; if GPG reports the key has expired, simply run the receive command again and trust as you see fit.

gpg --receive-keys 3FEF9748469ADBE15DA7CA80AC2D62742012EA22

Latest Comments

1 2 3 4 5 6 Next › Last »

jacek2v commented on 2025-07-11 14:34 (UTC)

@slurpee Great, thanks for explaining.

slurpee commented on 2025-07-11 10:33 (UTC)

@jacek2v - that's the expected output and the warning is benign.

"Good signature from" indicates the signature on the file matches the public key you're verifying against and you can trust the archive as being from Agilebits.

The warning is because you haven't signed ("certified") Agilebits's public key with your own private key (or a key you trust in your web of trust - "a trusted signature"). If you don't intend to use PGP other than validating the signature on files, you can safely ignore the warning and continue with installation.

jacek2v commented on 2025-07-11 10:17 (UTC)

gpg: assuming signed data in '/home/jacek/.cache/yay/1password-cli/src/op'
gpg: Signature made śro, 28 maj 2025, 12:15:49 CEST
gpg:                using RSA key 3FEF9748469ADBE15DA7CA80AC2D62742012EA22
gpg: Good signature from "Code signing for 1Password <codesign@1password.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 3FEF 9748 469A DBE1 5DA7  CA80 AC2D 6274 2012 EA22

any tips on what to do with this?

slurpee commented on 2024-01-21 23:31 (UTC)

Appreciate the report. I've opted to stop installing completion, letting the user add it to their shell's dotfile, if they wish. The 2.24.0-2 release removes the previously provided file, /usr/share/zsh/site-functions/_op.

The 1P documentation has users set up their dotfile and the official packages do not ship completion either. IMO, it's good to have parity with the official package when possible.

Detailed instructions on setting up completion can be found in the 1P docs: https://developer.1password.com/docs/cli/reference/commands/completion/

sschmelzer commented on 2024-01-20 12:48 (UTC)

Building the pkg is stuck with the following message: Would you like to turn on the 1Password app integration? This allows you to sign in to 1Password CLI using the 1Password app. [Y/n]. No matter what is answered, the process wont finish.

Looking at the fopens during the process it turned out to be a check if ~/.config/op/config exists (with a minimal config) during the execution of "${pkgdir}"/usr/bin/op completion zsh > "${pkgdir}"/usr/share/zsh/site-functions/_op. If the file exists build passes without any user interaction.

Providing a dummy config via --config helps to avoid the user interaction on build.

Minimal config:

{
    "latest_signin": "",
    "device": "",
    "accounts": null,
    "dismissed_system_auth_prompt": true
}

strickczq commented on 2023-12-28 06:23 (UTC)

@0BAD-C0DE Add Agilebits's PGP key reference

curl -sS https://downloads.1password.com/linux/keys/1password.asc | gpg --import

0BAD-C0DE commented on 2023-11-01 13:29 (UTC)

Latest version fails to check signature. Any hint?

gpg: Signature made mar 24 ott 2023, 19:13:13 CEST
gpg:                using RSA key 3FEF9748469ADBE15DA7CA80AC2D62742012EA22
gpg: Can't check signature: No public key
==> ERROR: A failure occurred in check().
    Aborting...
error: failed to build '1password-cli-2.22.0-1': 
error: packages failed to build: 1password-cli-2.22.0-1

Sacro commented on 2023-08-23 19:24 (UTC)

Line 35, should be install -dm755 not install -d 755

g_sokol commented on 2023-03-21 20:15 (UTC)

On attempt of sign in via 1password app it returns the following error:

➜  ~ op signin        
[ERROR] 2023/03/21 22:01:50 connecting to desktop app: read: connection reset, make sure the CLI is correctly installed and Connect with 1Password CLI is enabled in the 1Password app

It also seems to be in a proper group:

➜  ~ ls -la $(which op)
-rwxr-sr-x 1 root onepassword-cli 19197952 Mar  6 15:28 /usr/bin/op

InTerFace commented on 2022-07-21 07:25 (UTC)

clean your locally cloned package repo of any existing build artifacts/archives and run makepkg again?

this fixed it for me. thx