packages.netxms.org – signing keys are expired (again, d'oh)
-
As some of you already noticed – our signing key for deb repository is expired.
Normally we update the key and ship updated version of the netxms-release package, which transparently install correct version into trusted keys. This time we missed it and now most of you have expired key, which prevent further upgrades.Error looks something like this:
… Err:4 http://packages.netxms.org/debian bullseye InRelease The following signatures were invalid: EXPKEYSIG 179C0A80CDFADDB1 NetXMS Automatic Signing Key <[email protected]> Reading package lists... Done W: GPG error: http://packages.netxms.org/debian bullseye InRelease: The following signatures were invalid: EXPKEYSIG 179C0A80CDFADDB1 NetXMS Automatic Signing Key <[email protected]> E: The repository 'http://packages.netxms.org/debian bullseye InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default.How to fix it:
- If source and key was added by "netxms-release" package (recommended way), it's simple:
curl --proto '=https' --tlsv1.2 -O https://packages.netxms.org/netxms-release_1.10_all.deb dpkg -i netxms-release_1.10_all.deb apt update- If key was manually added to trusted.gpg.d
curl --proto '=https' --tlsv1.2 -o /etc/apt/trusted.gpg.d/netxms-keyring.gpg https://packages.netxms.org/netxms-keyring.gpg # adjust file location apt updateI highly recommend you to migrate to netxms-release package.
- If key was added with "apt-key add" command
apt-key del 179C0A80CDFADDB11 # repease until apt-key list shows no key curl --proto '=https' --tlsv1.2 -sSf https://packages.netxms.org/netxms.gpg | apt-key add -Again, I highly recommend you to migrate to netxms-release package.
-
Hi, I tried updating using the package, and using the netxms-keyring.gpg however I found I still got the old version expiring on the 24/3 with those.
Seemed only the third option (curl --proto '=https' --tlsv1.2 -sSf https://packages.netxms.org/netxms.gpg | apt-key add -) gave me the updated key and allowed apt update to work?
-
Check output of "apt-key list", most likely you have old key imported into another keystore.
@normalcy said in packages.netxms.org – signing keys are expired (again, d'oh):
Hi, I tried updating using the package, and using the netxms-keyring.gpg however I found I still got the old version expiring on the 24/3 with those.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login