Rudder

Hi,

GPG Keys are identified by the Pubkey's signature, and are handled as "meta RPM packages", like these:

# rpm -qa gpg-pubkey\*
gpg-pubkey-b37b98a9-4be01a1a
gpg-pubkey-307e3d54-4be01a65
gpg-pubkey-9c800aca-4be01999
gpg-pubkey-512adb3c-544a7777
gpg-pubkey-6a89acb9-54f5c0fa
gpg-pubkey-3d25d3d9-36e12d04
gpg-pubkey-cb53db96-544a7c27

They are stored in the /var/lib/rpm Directory in flatfile-Based BDB (Berkeley Database) Files:

# file /var/lib/rpm/Packages
/var/lib/rpm/Packages: Berkeley DB (Hash, version 8, native byte-order)

# db_stat -d /var/lib/rpm/Packages
Tue Jun 30 14:08:44 2015        Local time
61561   Hash magic number
8       Hash version number
Little-endian   Byte order
        Flags
4096    Underlying database page size
0       Specified fill factor
750     Number of keys in the database
750     Number of data items in the database
4       Number of hash buckets
600     Number of bytes free on bucket pages (96% ff)
6974    Number of overflow pages
1468848 Number of bytes free in overflow pages (94% ff)
1       Number of bucket overflow pages
4007    Number of bytes free in bucket overflow pages (2% ff)
0       Number of duplicate pages
0       Number of bytes free in duplicate pages (0% ff)
744     Number of pages on the free list

There is not easy way to check for the existence of any imported GPG Key without using RPM, that's designed to handle these files, except of using some kind of DB-Manipulation self-compiled C Program using BDB Bindings, which is absolute non sense, as RPM is basically the binary to handle this format :)

And the impact of an RPM call is way below anything worth mentioning:

# time (rpm --quiet -q gpg-pubkey-6a89acb9-54f5c0fa; echo $?)
0

real    0m0.036s
user    0m0.016s
sys     0m0.016s

# time (rpm --quiet -q gpg-pubkey-6a89acb9-foobarxx; echo $?)
1

real    0m0.033s
user    0m0.016s
sys     0m0.012s

There are way bigger things that eat away performance :-)