Given how fast crypto stuff becomes obsolete and even inaccessible these days,
a key imported today might not be loadable at all in a few years. There needs
to be a way to get rid of such keys without resorting to 'rm -rf' tactics, and
to be deletable they need to be listable. For rpmdb keystore, the gpg-pubkey
headers can be alternatively removed through the transaction API, thus
side-skirting the issue, but that's not really a sane design.
So rpmkeys needs to have means to list the underlying keystore contents
(presumably by fingerprint) without even trying to load them, and it needs to
be able to delete a key found this way. And of course to do that it'll need
corresponding APIs in librpm.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3375
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-maint
