On Fri, 4 Oct 2024 12:45, Mike Schleif said: > gpg (GnuPG) 2.3.3
> BEFORE taking your actions: > > -rw-r--r--. 1 root root 0 Oct 3 10:45 .gpg-v21-migrated Which means that you already migtated from 2.0 or 1.4 to 2.1 or later. That is the private keys are now stored in separate file below the > drwx------. 2 root root 4096 Oct 3 10:45 private-keys-v1.d directory. > -rw-------. 1 root root 273017 Jul 22 15:03 pubring.gpg > -rw-------. 1 root root 273017 Jul 22 15:03 pubring.gpg~ > -rw-------. 1 root root 600 Oct 3 11:03 random_seed > -rw-------. 1 root root 5726 Jul 10 2017 secring.gpg Take care - that secring.gpg is only used by older gpg versions. > NOTE: NO .kbx files. Right, you still use the pubring.gpg - not a real problem but no so common. Something with the migration didn't worked out. The pubring.gpg can't be used for gpgsm (S/MIME) and thus a pubring.kbx should have been created during the migration. > [ROOT@russell ~/.gnupg ] # /bin/gpg --import < exported.gpg > . . . > gpg: Total number processed: 189 > gpg: w/o user IDs: 1 > gpg: imported: 188 > gpg: public key of ultimately trusted key 0000000000000000 not found Your trustdb has an ultimately trusted PGP-2 key. gpg can't disaply the fingerprint anymore and thus you see the zeroes. > gpg: marginals needed: 3 completes needed: 1 trust model: classic > gpg: depth: 0 valid: 82 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 82u > gpg: next trustdb check due at 2033-09-13 You should gpg --edit-key YOURKEY and enter "trust" to set your key back to ultimately trusted. This will given you back the WoT. > gpg: key 0000000000000000 occurs more than once in the trustdb You have several PGP-2 keys in your trustdb. Salam-Shalom, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein
openpgp-digital-signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users
