> @andrewclausen The Sequoia backend should process revocation certificates
> correctly. The internal backend does not, which is one of multiple reasons it
> is deprecated.
It's not just a question of the backend. For example, how would the revocation
certificates be distributed?
My main point here is: security is hard, and users (like me) definitely
appreciate seeing that everything has been thought through.
If so, I think @nwalfield's proposal should work well.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2577#issuecomment-1652685398
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2577/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-maint
