This is clearly saying google-chrome-stable is not installed, while it is (you can run it just fine from your app menu). Package google-chrome-stable is not installed Header V4 DSA/SHA1 Signature, key ID 7fac5991: BAD
= 1) System doesn't show affected RPMs as installed =Įrror: rpmdbNextIterator: skipping h# 2525 Unless otherwise noted, the following examples are from Fedora 37 Workstation with Google Chrome installed (from their official repo) and then upgraded to Fedora 38 Workstation: However, people who *upgrade* to F38 and already have some affected RPMs installed will see serious consequences:ġ) System doesn't show affected RPMs as installed (in `rpm -qa` or `rpm -q`)Ģ) System can't remove the affected RPMs (with `rpm -e` or `dnf remove` or PackageKit)ģ) System can't be updated, if an affected RPM is in the transaction (`dnf update`, PackageKit)Ĥ) System will not fix itself even if vendor fixes their RPMs, a manual intervention is necessary But overall there seems to be no negative impact on the OS in general. RPM rejects them based on their RPM signature or the repo key signature (as far as I understand it). Please read the problem description here first:įor fresh F38 installations, the only consequence seems to be that many popular third-party software can't be installed. This is an attempt to summarize the impact of an F38 change to enforce security policies in RPM on our user base, and describe the discovered problems. Redhat-crypto fedora-crypto-policies merge_requests 129ĭraft: DEFAULT: allow SHA-1 and DSA in sequoia () Microsoft (Release signing) GPG key uses SHA-1 signature Microsoft linux-package-repositories issues 47
Output of `RPM_TRACE=1 rpm -q -querybynumber 30` Trying to remove Chrome in GNOME Software Trying to update system in GNOME Software
0 kommentar(er)
