[prev in list] [next in list] [prev in thread] [next in thread]
List: gnupg-users
Subject: output of --check-trustdb
From: Hauke Laging <mailinglisten () hauke-laging ! de>
Date: 2012-08-19 4:25:51
Message-ID: 36364100.v2z1pehbiv () inno
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
Hello,
I am trying to understand how the trust calculations work and I think I have
made serious progress in that... ;-)
There are at least two things I have not understood yet:
1) Is it possible to have the ownertrust value shown with --list-keys?
Validity can be shown. I had expected a parameter like show-ownertrust for
‑‑list-options.
2) I do not understand the "signed" column in the output of --check-trustdb. I
read something about that but it doesn't make sense to me. It seems generally
difficult to find good information about that.
start cmd:> LC_ALL=C gpg --check-trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 17 signed: 26 trust: 0-, 0q, 0n, 0m, 0f, 17u
gpg: depth: 1 valid: 26 signed: 3 trust: 0-, 0q, 10n, 8m, 8f, 0u
gpg: depth: 2 valid: 3 signed: 0 trust: 0-, 0q, 0n, 1m, 2f, 0u
Before someone asks: Yes, of course, there are a lot of test keys.
Hauke
--
☺
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
["signature.asc" (application/pgp-signature)]
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic