Problem with Import of ultimate trusted key

David Shaw dshaw@jabberwocky.com
Mon May 5 15:47:03 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, May 05, 2003 at 11:19:31AM +0200, Sebastian Wiesinger wrote:

> I have a problem here with the import of my own public key into
> another keyring (the key is in pubring.gpg and in mykey.asc):
> 
> I use gpg 1.2.1 with the following options:
> 
> gpg --no-options --armor --no-default-keyring --keyring mykey.gpg --import mykey.asc
> 
> If I do so, the import resets the trust of my key to "unkown", also in
> my main keyring (well it just updates the trustdb).

Yes.  This is intentional since GnuPG sees you importing a key that
doesn't currently exist... but at the same time sees that key has
ultimate trust in the trustdb.  Since GnuPG normally deletes trust
when a key is deleted, this means there is a mismatch between the
trustdb and the keyring(s).

> Is it possible to stop gpg from updating the trustdb for specific
> imports?

gpg --trustdb-name ./temp.trustdb .......
rm ./temp.trustdb

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.2-cvs (GNU/Linux)
Comment: http://www.jabberwocky.com/david/keys.asc

iD8DBQE+tmt04mZch0nhy8kRAhdrAKC8aY9E90eE6loq9r0Rf+ukvD7xTACfWB6y
OhqQn5qVnieAFCS8TxqZSEs=
=41MO
-----END PGP SIGNATURE-----