CLI Binaries changed without notice? (signature still OK though)

Community Member

Dear 1Password CLI team,

I’m a co-maintainer for the 1password-cli package for 1Password CLI Beta on the Arch User Repository (AUR). Earlier today, a user of the AUR package has informed me that the 0.4.1 release packages for Linux on AgileBit’s site have changed since build #v41001 was released on 2018-05-10. I was able to confirm this.

The original checksums of the 0.4.1 Linux releases, as recorded by myself on 2018-05-15, were:


As of 2018-06-03, the current checksums for the 0.4.1 Linux releases are:


Per good practice, the AUR package rely mainly on the GPG signature by AgileBits; only as an additional safety net does it check the SHA signatures of the downloaded binaries. The modified binaries are indeed signed by AgileBits, and the signatures are perfectly good. While I assume they are therefore probably 100 % safe to use, I was unable to find any accompanying release note, blog article, or bump of version number and date, which I personally feel is barely unusual enough to make me feel a little uneasy. It also has never happened before since I’ve started checking SHAs for all of AgileBits’s binary releases.

To that end, despite the perfectly good signature, allow me to ask just for good measure and reassurance:

  1. Have AgileBits deliberately changed the Linux 0.4.1 release packages without at the same time bumping the build number?
  2. Are such changes to be expected regularly from now on without accompanying bump of build numbers?

Important clarification for other readers: The 1password-cli package is a community effort; it has no connection to AgileBits or the 1Password organization, and is not supported nor endorsed by either.

Thanks in advance and kind regards,

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Arch Linux
Sync Type: Not Provided


  • cohixcohix
    1Password Alumni

    @Claudi Thanks for pointing this out to us. This was not intentional, at least not by me (I generally perform the builds for the CLI), so I will check in with our ops team and see what could have caused this. I will reply back here when I've figured it out.


  • cohixcohix
    1Password Alumni

    @Claudi Alright, I've checked in; turns out our build servers went through some upgrades and re-configuration last week, and as such all our binaries got rebuilt automatically. So this won't normally happen, but it is possible. The build server handles signing, so that's why the signatures still check out :)

    I'll try to post in the forum if this happens in the future.

  • ClaudiClaudi
    Community Member

    @cohix Thanks for your response; that really helped! Also, that reassuring feeling ;)

  • cohixcohix
    1Password Alumni

    Any time :)

This discussion has been closed.