Bug 2188684
Summary: | contains expired RPM-GPG-KEY-openSUSE-Backports key | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Brian J. Murrell <brian.murrell> |
Component: | distribution-gpg-keys | Assignee: | Miroslav Suchý <msuchy> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 38 | CC: | copr-team, msuchy |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | distribution-gpg-keys-1.87-1.fc38 distribution-gpg-keys-1.87-1.fc37 distribution-gpg-keys-1.87-1.el7 distribution-gpg-keys-1.87-1.el8 distribution-gpg-keys-1.87-1.el9 distribution-gpg-keys-1.87-1.fc36 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-04-24 18:32:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brian J. Murrell
2023-04-21 16:04:24 UTC
This problem gets more interesting. The same version of mock (3.5) on F37 and F38 behave differently with this expired key. On F37: Importing GPG key 0x65176565: Userid : "openSUSE:Backports OBS Project <openSUSE:Backports.org>" Fingerprint: 637B 32FF 3D83 F07A 7AE1 C40A 9C21 4D40 6517 6565 From : /usr/share/distribution-gpg-keys/opensuse/RPM-GPG-KEY-openSUSE-Backports Key imported successfully but on F38: Importing GPG key 0x65176565: Userid : "openSUSE:Backports OBS Project <openSUSE:Backports.org>" Fingerprint: 637B 32FF 3D83 F07A 7AE1 C40A 9C21 4D40 6517 6565 From : /usr/share/distribution-gpg-keys/opensuse/RPM-GPG-KEY-openSUSE-Backports error: Certificate 9C214D4065176565: The certificate is expired: The primary key is not live Did something change in F38 with regard to importing expired keys? Did Fedora, prior to 38 not check if a key was expired when it imported it but 38 has started validating the expiry of the key? Is it perhaps the switch to Sequoia crypto (https://fedoraproject.org/wiki/Changes/RpmSequoia)? Several issues here: > On F37 > From : /usr/share/distribution-gpg-keys/opensuse/RPM-GPG-KEY-openSUSE-Backports >Key imported successfully This is a problem. Cc @jmracek And I guess that - yes - this is related to rpmSequoia change. Not sure if DNF team will want on fix in F37 when it works correctly in F38. > the problem is actually the expired key being included in distribution-gpg-keys I do NOT see this as a problem. This **is** the key that SUSE uses for backports. Even today, it is here: http://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-15-SP3:/Update/standard/ If you want to get this addressed, you have to contact SUSE. And I do not see a problem that the file is expired. I guarantee that the content of the file is unchanged. But you still have to check if the key is not expired. Or revoked. Is all of the content and status change in comment#2 before or after the comment/realization in https://github.com/xsuchy/distribution-gpg-keys/issues/91#issuecomment-1521382875 upstream? If before, should this ticket be re-evaluated @msuchy? FEDORA-EPEL-2023-b5c6bb26d7 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-b5c6bb26d7 FEDORA-2023-aceb7fc54a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-aceb7fc54a FEDORA-EPEL-2023-b1ae265e04 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-b1ae265e04 FEDORA-EPEL-2023-2b24d13a34 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2b24d13a34 FEDORA-2023-d43304bab0 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d43304bab0 FEDORA-2023-d43304bab0 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-d43304bab0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d43304bab0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-315f8a5ff1 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-315f8a5ff1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-315f8a5ff1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-aceb7fc54a has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-aceb7fc54a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-aceb7fc54a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-2b24d13a34 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-2b24d13a34 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-b1ae265e04 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-b1ae265e04 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-b5c6bb26d7 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-b5c6bb26d7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-aceb7fc54a has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-d43304bab0 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2023-b1ae265e04 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2023-b5c6bb26d7 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2023-2b24d13a34 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-315f8a5ff1 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |