GnuPG Keyring Issue Across Systems. Where is pubring.kbx?

[Ming Kuang]

On Wed, 2024-10-09 at 15:50 +0200, Alejandro via Gnupg-users wrote:
> Hi,
> 
> I’m using the default GnuPG package from `pacman -S gnupg` on my Arch 
> system. For security reasons, I copied my GNUPGHOME to a USB drive, 
> which worked well when I mounted it as GNUPGHOME.
> 
> However, I recently needed to use my keys on another machine running 
> Pop!_OS 22.04. After decrypting my LUKS USB drive and exporting the 
> GNUPGHOME to my .gnupg directory on the USB, I ran `gpg --list-keys`. 
> This created a new `pubring.kdx`. Upon checking my main .gnupg 
> directory, I noticed it doesn’t contain a `pubring.kbx`,
> `pubring.gpg`, 
> or `secring.gpg`.
> 
> I suspect this is because Arch, being a rolling release, uses a newer 
> version of GnuPG that doesn't require a pubring, while Pop!_OS is
> using 
> an older version.
> 
> Here’s what my .gnupg directory looks like:
> 
> ```
> 
> ls .gnupg
> 
> common.conf  openpgp-revocs.d/   public-keys.d/  sshcontrol
> crls.d/      private-keys-v1.d/  random_seed     trustdb.gpg
> ```
> 
> Thanks for your help!

Hello,

As far as I know, the latest version of GPG use keyboxd to manage public
keys (essentially a sqlite database, which supposedly offers better
performance), and the database files are located in the public-keys.d
directory

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20241010/3731081d/attachment.sig>