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

[Panu Matilainen]

Splitting rpm-sequoia to a separate policy seems like a good idea indeed.

While we're hijacking :smile: - can we make expired signatures also return NOTTRUSTED?
(I guess revocation would fall into the same category too)


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

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