-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
packages.matrix.org signing key will expire on 2023-04-15 #10389
Comments
Ideas are:
The advantage of the second option is that it won't require any action by users. It's a fairly commonly-used pattern; see for example:
|
a keyring package would also be a good place to ensure that the revoked key ( |
Just a reminder that this will need sorting in Q1 next year. |
Seems like our solution has caused an error in some cases: element-hq/element-web#15176 |
What's the status---do we still need to generate/renew keys? |
we still need to republish the existing keys with an updated expiry date. This is on me. |
@richvdh for the uninitiated could you log the steps for me to blindly follow for packages.element.io please :) |
FTR this was fixed by a change to the way we build the keyring package. |
The steps are as follows, given a gpg data directory at
|
I now realise this is also all written down at https://gitlab.matrix.org/new-vector/internal/-/wikis/packages#renewing-the-debian-package-signing-keys (for element employees) |
The public key at https://packages.matrix.org/debian/matrix-org-archive-keyring.gpg is now updated. @matrix-org/synapse-core: please could you update the keyring package? |
I've updated the keyring package, so this should be done |
If anybody is seeing errors along the lines of the following:
... then that suggests you have an outdated copy of the To fix it:
|
The expiry date has now passed. Do we need to say anything about this in the release/upgrade notes, or should this be transparent to users of our deb packages? |
It'll be transparent to users who kept up to date, a keyring package was added as a recommended dependency which will keep the gpg keyring up to date. For users upgrading from old versions or with custom gpg setups will need to manually update the keyring. |
It was not transparent for me, on an Ubuntu LTS using managed releases. |
Probably related? I get the this error from the Element repository on my (Debian 11) Desktop.
Downloading the latest version of the keyring according to the documentation did not solve the problem. |
I'm not sure what "managed releases" mean, but it's possible you either haven't upgraded synapse recently, or you upgraded without installing recommended packages. |
I updated the keyring but still have the same issue. |
seems like for me the source.list need to be updated to include signed-by like so |
Yes, that is what it says at https://matrix-org.github.io/synapse/latest/setup/installation.html#matrixorg-packages. If your |
yeah I think mine is left over from years ago |
suggest you fix it, otherwise you will have the same problem in two years' time |
Hi, I upgraded to Ubuntu Lunar last Friday and noticed apt-get complaining about the F473DD4473365DE1 key for the matrix repository "deb [signed-by=/usr/share/keyrings/matrix-org-archive-keyring.asc] https://packages.matrix.org/debian lunar main" . |
@dannyp777 your I've removed the outdated |
|
Please don't do this. It means that the matrix.org keyring becomes trusted to replace any package on your system. |
XD Sorry for my poor Linux level |
I missed the window between when the new keyring package became available, and when the repo key was changed. I understand how I can update to use the new key (already done) but it kind of sucks that my chain of trust is now broken. Would you consider providing a human readable message signed by the old key which indicates the new key is trustworthy? (going forward) Obviously missing the window is entirely on me, but it would be nice to be able to recover the chain of trust in that event. |
The key has not been changed. Just the expiry date. |
The GPG key (F473DD4473365DE1) used to sign the Debian repository at https://packages.matrix.org has an expiry date of 2023-04-15. We'll need to do something about this well in advance.
Related: matrix-org/matrix.org#973
The text was updated successfully, but these errors were encountered: