Skip to content
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

Unavailable Debian archive key B4D2D216F1FD7806 #1634

Open
paulmenzel opened this issue Apr 16, 2021 · 3 comments
Open

Unavailable Debian archive key B4D2D216F1FD7806 #1634

paulmenzel opened this issue Apr 16, 2021 · 3 comments

Comments

@paulmenzel
Copy link
Contributor

With

deb https://download.jitsi.org unstable/

running apt update, the messages below are shown.

Get:4 https://download.jitsi.org unstable/ InRelease [1,888 B]                               
Err:4 https://download.jitsi.org unstable/ InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B4D2D216F1FD7806
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://download.jitsi.org unstable/ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B4D2D216F1FD7806
W: Failed to fetch https://download.jitsi.org/unstable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B4D2D216F1FD7806
W: Some index files failed to download. They have been ignored, or old ones used instead.

Installing jitsi-archive-keyring/unstable does not help either.

@paulmenzel paulmenzel changed the title GPG error: https://download.jitsi.org unstable/ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B4D2D216F1FD7806 Unavailable Debian archive key B4D2D216F1FD7806 Apr 16, 2021
@paulmenzel
Copy link
Contributor Author

Purging the package jitsi-archive-keyring again, and manually installing the keyring as described in the Self-Hosting Guide worked around the issue. (s/stable/unstable/ for my usecase.)

curl https://download.jitsi.org/jitsi-key.gpg.key | sudo sh -c 'gpg --dearmor > /usr/share/keyrings/jitsi-keyring.gpg'
echo 'deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg] https://download.jitsi.org unstable/' | sudo tee /etc/apt/sources.list.d/jitsi-unstable.list > /dev/null

The the packages could be installed. It looks like jitsi-meet also has some scripts to remove the old key.

Setting up jitsi-meet (2.0.5792-1) ...
We found the old key EF8B479E2DC1389C, which is no longer valid and we removed it.

Still a working upgrade path to rotate keys seems to be missing.

@damencho
Copy link
Member

Still a working upgrade path to rotate keys seems to be missing.

Yes, this is known and we will work on fixing that. This concerns all debian packages we create.

@bs27975
Copy link

bs27975 commented Sep 1, 2022

Purging the package jitsi-archive-keyring again, and manually installing the keyring ...

Purging the package also solved the NO_PUBKEY B4D2D216F1FD7806 issue for me. Chased my tail for much time until google-fu got me to that comment - thanks for making it. Wish the solution had been more prominent in my googling. Maybe this comment will help with that. Manual install done but not helpful until.

Did purge, but remove might have worked too.

# apt-get purge jitsi-archive-keyring

is what fixed the problem for me, however, it auto-removed jitsi too.

# apt-get install jitsi

showed it did nothing - so the auto-removed jitsi apt-get message seems not credible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants