The following signatures were invalid: EXPKEYSIG F8F2C31744774B28 Mattermost Build <dev-ops@mattermost.com>

Troubleshooting
3

however.

  1. why does mattermostmost keep this key in /usr/share/keyrings/mattermost-archive-keyring.gpg instead of /etc/apt/trusted.gpg.d/ folder?
  2. does anything else besides apt use this keyring? (as for apt the gpg --dearmor is totally unnecessary step there. apt can use ascii key files for repo signatures just as well.)
  3. But why not just use deb https://deb.packages.mattermost.com jammy main in mattermost.list? seems to work fine… for sudo apt update at least.

anyway, thanks for help and inspired by this, on my case just as normal, non-root user…

curl -s https://deb.packages.mattermost.com/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/mattermost-archive-keyring.gpg

…was enough, to fix this. To overwrite original, old, already existing expired key. Repos and everything else was already in place.

1 Like