Overriding RPM public key database
- by pilcrow
Can rpm be persuaded to import and fetch public keys from an arbitrary pubkey database?
On the same build machine I've got two automated users who each need to verify package signatures from different sources, signed under different keys. If I rpm --import pkg-source1.pub pkg-source2.pub, each user will be able to verify packages intended for the other. I'd rather each user not know about the other's public keyring.
Is there a way I can specify an alternate or supplementary pubkey database on a per-user or per-rpm(8)-invocation basis?
