placing trust in imported keys

Werner Koch wk at
Sat Mar 9 09:37:47 CET 2013

On Sat,  9 Mar 2013 02:26, jw72253 at said:

> gpg: Total number processed: 1
> gpg:               imported: 1

That should be self-explaining.

> gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model

This is the configuration of the WoT; see the man page for options to
change it.

> gpg: depth: 0  valid:   8  signed:  25  trust: 0-, 0q, 0n, 0m, 0f, 8u
> gpg: depth: 1  valid:  25  signed:   1  trust: 0-, 4q, 0n, 20m, 1f, 0u

You would need to look at the source.  However, if you known the WoT
well, you should be able to figure out what this is.  For example at
depth 0, you see 8 ultimately trusted keys.  At the next level you
obviously find no ultimately trusted keys but 20 marginal trusted and 1
fully trusted key.  You should consider this a debugging output.

> gpg: next trustdb check due at 2013-12-31

The check run found that due to key or signature expiration a new trust
check is due on that date.  It is informational only, because that date
is stored in the trustdb and a gpg --check-trustdb --batch before that
date will conclude that this time it can be lazy and exit immediately.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

More information about the Gnupg-users mailing list