placing trust in imported keys

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

placing trust in imported keys

John A. Wallace
placing trust in imported keys

Where can I find an explanation of how to interpret these lines of output we saw while importing a key onto a persons keyring:

gpg: key DED64EBB2BA87C5C: public key "OTR Dev Team <[hidden email]>" imported

gpg: Total number processed: 1

gpg:               imported: 1

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

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

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

- Public keyring updated. -

- Trust DB updated. -

Time: 3/8/2013 5:58:34 PM (3/8/2013 11:58:34 PM UTC)


_______________________________________________
Gnupg-users mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Reply | Threaded
Open this post in threaded view
|

Re: placing trust in imported keys

Werner Koch
On Sat,  9 Mar 2013 02:26, [hidden email] 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.


Shalom-Salam,

   Werner

--
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


_______________________________________________
Gnupg-users mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-users