Forum Discussion

Former Member's avatar
Former Member
5 years ago

The following signatures couldn't be verified because the public key is not available

The .deb packages signing gpg key got rotated?


W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://downloads.1password.com/linux/debian/amd64 beta InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AC2D62742012EA22
W: Failed to fetch https://downloads.1password.com/linux/debian/amd64/dists/beta/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AC2D62742012EA22

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

linux

11 Replies

  • 1P_PeterG's avatar
    1P_PeterG
    Icon for Community Manager rankCommunity Manager
    4 years ago

    Thanks for this note, @doug_collier. We appreciate it!

  • Former Member's avatar
    Former Member
    4 years ago

    The linux install steps to fix this did not work in zsh, I needed to use bash.

  • 1P_PeterG's avatar
    1P_PeterG
    Icon for Community Manager rankCommunity Manager
    5 years ago

    Thanks for letting us know, @nprokopic. We'll keep an eye out for this issue!

  • Former Member's avatar
    Former Member
    5 years ago

    I've hit this issue again, same workaround (redoing installation steps) helped.

  • 1P_Ben's avatar
    1P_Ben
    Icon for 1Password Team rank1Password Team
    5 years ago

    Got it. Thanks for sharing @mrdoodiddle. :)

    Ben

  • Former Member's avatar
    Former Member
    5 years ago

    Nah, it's been a while now I don't have the old repo config anymore, I am all set.

    Regardless im just saying that a repo change or sign key change is important for me, so having it in a release notes would have been a nice notice :).

  • 1P_Ben's avatar
    1P_Ben
    Icon for 1Password Team rank1Password Team
    5 years ago

    Hi @mrdoodiddle

    My understanding is that the key itself did not change, only where it is hosted. Are you seeing indications otherwise?

    Ben

  • Former Member's avatar
    Former Member
    5 years ago

    Yes I re-installed the public key, which allowed me to update and of course I failed to update my post here.

    Replacing the signing key surprised me, as blindly using a new key without any information is not good in my humble opinion.

    Is there a notification somewhere that the key got changed (maybe I missed it) ?

  • 1P_PeterG's avatar
    1P_PeterG
    Icon for Community Manager rankCommunity Manager
    5 years ago

    Hi @mrdoodiddle, thanks for letting us know about this.

    We've checked in with some of our server and development folks about this, and it turns out there was a change in how we host the public key. This has apparently caused an issue for a small number of customers. The good news is this issue shouldn't come up any more going forward.

    To fix the immediate problem, as @nprokopic helpfully mentioned, try redoing the installation steps at https://support.1password.com/install-linux/.

    If that doesn't work for you, let us know and we'll help you sort it out. And thank you again for bringing this to our attention!

  • Former Member's avatar
    Former Member
    5 years ago

    Hi Dayton_ag, I have installed 1Password for Linux after it was released to stable, but I've hit the same issue like @mrdoodiddle wrote above.

    I'm running KDE Neon (based on Ubuntu 20.04):


    Distributor ID: Neon
    Description: KDE neon User Edition 5.22
    Release: 20.04
    Codename: focal

    Redoing steps from https://support.1password.com/install-linux/ fixed the issue for me.