<![CDATA[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 <info@netxms.org>
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 <info@netxms.org>
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:

  1. 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
  1. 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 update

I highly recommend you to migrate to netxms-release package.

  1. 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.

]]>https://forum.netxms.org/topic/7339/packages.netxms.org-signing-keys-are-expired-again-d-ohRSS for NodeFri, 13 Nov 2026 22:54:21 GMTMon, 28 Mar 2022 12:45:25 GMT60<![CDATA[Reply to packages.netxms.org – signing keys are expired (again, d'oh) on Wed, 06 Apr 2022 12:15:05 GMT]]>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.

]]>https://forum.netxms.org/post/31192https://forum.netxms.org/post/31192Wed, 06 Apr 2022 12:15:05 GMT<![CDATA[Reply to packages.netxms.org – signing keys are expired (again, d'oh) on Wed, 06 Apr 2022 11:50:09 GMT]]>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?

]]>https://forum.netxms.org/post/31191https://forum.netxms.org/post/31191Wed, 06 Apr 2022 11:50:09 GMT