[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]

See https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c15 for details.

`rpm-sequoia` could easily try to validate a signature using two different policies ([here](https://github.com/rpm-software-management/rpm-sequoia/blob/main/src/lib.rs#L574)): the system policy and a legacy policy.  If the signature doesn't validate with the system policy, but does with the legacy policy, it could return a different error.  @panu: Is this something that would be useful?

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

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