[Rpm-maint] [rpm-software-management/rpm] Distinguish whether a signature failure is due to legacy crypto or a bad signature (Issue #2402)

[Neal H. Walfield]

Thanks for testing, panu.  One thing (and sorry for hijacking this issue), we decided to have [a dedicated configuration for rpm-sequoia](https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/merge_requests/129#note_1297002360), which enables 1024 bit DSA and SHA-1.  I'm going to add that first (try `rpm-sequoia.config`, if that is not present, fallback to `sequoia.config`), and then make a release.  If you have any thoughts, please let me know.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2402#issuecomment-1451448512
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/2402/1451448512 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20230302/5a6319ae/attachment.html>