Bugzilla – Bug 1199184
switch Tumbleweed to a 4096bit RSA signing key
Last modified: 2023-02-20 12:55:03 UTC
We currently still use a 2048 bit key for signing. It would be better to switch to a 4096 RSA key.
AFAIK 2048 bit RSA is still considered secure. What about switching to something like ECDSA/EdDSA?
Is still considered secure, but other distros use longer keys and e.g. Dirk Mueller already argues on why openSUSE does not switch. I am not yet familar how much could break with switching to elliptic curves though.
(In reply to Marcus Meissner from comment #2) > Is still considered secure, but other distros use longer keys and e.g. Dirk > Mueller already argues on why openSUSE does not switch. I'm not arguing, I was asking what needs to be done to implement a longer key for ALP. Based on factory first we should try to roll it out in openSUSE first and see the downsides before doing anything on SLE. From a brief look at https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-57pt1r5.pdf it appears that RSA2048 is the acceptable minimum, and other distributions are chosing larger keys. I don't really care which cryptographic method we chose, so elliptic curve is totally fine by me as well. I don't know the implications of that very thorughly though, more expertise is needed.
Looks like EdDSA support landed in RPM in 2020 and it works on TW (with sha256 only, https://github.com/rpm-software-management/rpm/issues/1877 is missing). It doesn't work on Leap though, so either that would have to be backported (https://github.com/rpm-software-management/rpm/pull/1202 at least) or we'd have to deal with RSA a bit longer. IMO it's better to keep RSA 2048 for a a bit longer and then switch to ECC directly instead of switching to RSA 4096 now (and maybe switch to ECC in the future).
I filed an OBS ticket to make signing keytypes configurable via api calls, as currently OBS API would only creating 2048bit RSA keys. https://jira.suse.com/browse/OBS-193
Is there also a github issue or such that I could watch for the OBS implementation discussion? (I want to change to a longer key in a private OBS instance and would hope that this discussion helps me achieve that seamlessly ;-))
https://github.com/openSUSE/open-build-service/pull/12528
just for the record, the pull request is for changing OBS defaults, but for tumbleweed it is a config setting we can do at any time.
Created attachment 860726 [details] openSUSE RSA 4096 key This is the new key that was created a few weeks back by Ruediger Oertel. Rudi can you confirm that this is the right key and that we have established backups etc?
Only one? While we are at it there would be the chance to have a second one that only exists offline and is stored away in a safe for emergencies. So far the SLE key serves as fallback which is a) odd and b) also seems to be only rsa2048.
> Rudi can you confirm that this is the right key and that we have established backups etc? yes, 35A2F86E29B700A4 is the key created 20220620 and this is also in the encrypted backup and in the safe. If a reserve key for openSUSE is needed we can of course create that, but maybe it makes sense to wait a few more weeks until we have the needed infrastructure working for ECC based keys (almost there but still fighting with a few performance issues when switching to current gpg versions).
pubkey update on its way to factory.
It's been a while here, but I don't see the factory key having changed to the new rsa 4096 key. curl https://download.opensuse.org/tumbleweed/repo/oss/repodata/repomd.xml.key | gpg -v pub rsa2048 2008-11-07 [SC] [expires: 2024-05-02] 22C07BA534178CD02EFE22AAB88B2FD43DBDC284 uid openSUSE Project Signing Key <opensuse@opensuse.org> when do we plan to switch?
Cross check with Dimstar. - switch only after new years as people are already in xmas vacation we need to put this key also in Leap, which I will be working on nowm, for migration purposes (and also to have Leap 15.5 and perhaps olders switch to it too.)
This is an autogenerated message for OBS integration: This bug (1199184) was mentioned in https://build.opensuse.org/request/show/1042405 15.4 / openSUSE-build-key https://build.opensuse.org/request/show/1042411 15.3 / openSUSE-build-key https://build.opensuse.org/request/show/1042414 15.5 / openSUSE-build-key
(In reply to Marcus Meissner from comment #14) > Cross check with Dimstar. > - switch only after new years as people are already in xmas vacation technically the tumbleweed key is already created, backed up and on the keyserver, so it is "just" a config change to activate it. it would be the easiest to do (but after xmas break is also fine)
openSUSE-RU-2022:10259-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1199184 CVE References: JIRA References: Sources used: openSUSE Leap 15.4 (src): openSUSE-build-key-1.0-lp154.3.3.1
openSUSE-RU-2023:0003-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1199184 CVE References: JIRA References: Sources used: openSUSE Leap 15.3 (src): openSUSE-build-key-1.0-lp153.4.11.1
Dominique, happy new year! when would be a good time to do the switch? from OBS side its a one liner config change and can be done at any point in time now. Also the leap update is released.
Talked with Dominique, lets target 23.1. for switchover
(In reply to Marcus Meissner from comment #20) > Talked with Dominique, lets target 23.1. for switchover The switch has been executed. Repodata is signed with the new key and rpms are gradually moving over to the new key (old one is still accepted) In case anything is missing, please reopen
This is an autogenerated message for OBS integration: This bug (1199184) was mentioned in https://build.opensuse.org/request/show/1066811 Factory / rpm-repos-openSUSE https://build.opensuse.org/request/show/1066812 15.4 / rpm-repos-openSUSE https://build.opensuse.org/request/show/1066813 15.5 / rpm-repos-openSUSE