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

[Panu Matilainen]

> To be clear: this change returns a different error code and prints something on stderr.

Yup, understood. Just musing whether breaking the principle (of not printing to stderr) is worth the added information, and in the bugzilla case I don't think it really is. Key import is one place where it would make a big difference ... but mostly just for the internal parser which verifies on import. 

I'd leave the stderr out for now. This is already quite an improvement, we just need to add the relevant rpm side checks for the "new" return code (NOTTRUSTED is ages old technically, but it's never been used for anything)

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

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