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

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

I think the diagnostics would show up when the user directly invokes `rpm`, which is what the reporter did [here](https://bugzilla.redhat.com/show_bug.cgi?id=2170878#c0) .  I think you are right that in other cases, the message would get lost, but if they don't harm in those cases, it seems like a net win.

Ideally, rpm-sequoia would have a way to call `rpmlog`, but that's not yet the case.

What should we do?

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

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