(From a quick perusal of your rust code)
You may need bindings for a FD_t since certain routines in the rpmlib API take
a FD_t.
There is also (in RPM4) a key ring object, basically a container for pubkeys.
However RPM avoided handling private keys last century "munitions" and
externalized signing operations in a helper.
The attempts to do hardware signing for *.rpm are pretty much ad hoc
slice-and-dice in external custom code. There are some hard design issues
locating a key store when chroot(2) is routinely used as in rpm.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/429#issuecomment-380867813
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
