Debian-testing/debian-stable public.key has expired

Hello, just something I noticed while updating my Rock 5 today. I’m running the Bullseye release provided by Radxa and it appears that I’m getting an error when trying to update from either of the apt repositories (testing/stable), indicating that there is no valid signature (The following signatures were invalid: EXPKEYSIG B99C4BEFEC47E96E Radxa dev@radxa.com)

Further investigation listing the keys with apt-key list, has shown this to be correct:

pub rsa3072 2020-11-24 [SC] [expired: 2022-11-24]
*** 466B 1E7F 6809 6652 1384 8FCA B99C 4BEF EC47 E96E***
uid [ expired] Radxa dev@radxa.com

/etc/apt/trusted.gpg.d/debian-archive-bullseye-security-automatic.gpg

Attempting to manually re-add the public keys from the apt.radxa.com repositories, as well as the github ones, yield the same (expired) key.

Thanks!

-Jarrod

Yes, i had the same experience.

Updating the gpg key now…

1 Like

HI Jack,
I’ve got this error:
Err:2 http://apt.radxa.com/bullseye-stable bullseye Release
404 Not Found [IP: 185.199.108.153 80]

Thank you

1 Like

Same problem has occurred on the Ubuntu public key.

Hi jack, it seem that public key is not available again

same here

Err:5 http://apt.radxa.com/bullseye-stable bullseye InRelease                                                                                                                                              
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9B98116C9AA302C7
Reading package lists... Done                                                                                                                                                                              
W: GPG error: http://apt.radxa.com/bullseye-stable bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9B98116C9AA302C7
E: The repository 'http://apt.radxa.com/bullseye-stable bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

had to temporarily skip security check by putting [trusted=yes] in front of the repository to be able to update