Dear Maintainer,
The signing key for the ProtonVPN apt repository appears to be outdated
(at least in Bookworm and Sid).
The current key that extrepo tries to use is:
pub rsa3072 2024-03-20 [SC] [expired: 2025-03-20]
9E72DFDF2AF019F0CCFC68F38DD48989F43719CA
uid Proton Technologies AG <opensource@proton.me>
sub rsa3072 2024-03-20 [E] [expired: 2025-03-20]
Which Proton seems to have replaced with and now provides to users:
pub rsa3072 2025-03-03 [SC] [expires: 2027-03-03]
84B0D3492C76C9C6F5873C18EDA3E22630349F1C
uid Proton Technologies AG <opensource@proton.me>
sub rsa3072 2025-03-03 [E] [expires: 2027-03-03]
Which causes
$ sudo apt update
Hit:1 http://deb.debian.org/debian bookworm InRelease
[...]
Err:9 https://repo.protonvpn.com/debian stable InRelease
The following signatures couldn't be verified because the public key is
not available: NO_PUBKEY EDA3E22630349F1C
[...]
Reading package lists... Done
Building dependency tree... Done
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://repo.protonvpn.com/debian stable InRelease: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY EDA3E22630349F1C
W: Failed to fetch
https://repo.protonvpn.com/debian/dists/stable/InRelease The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY EDA3E22630349F1C
W: Some index files failed to download. They have been ignored, or old
ones used instead.
I worked around the issue by replacing the old key with the new one.
Best regards,
Frank T.
( •ᴗ•) b