summaryrefslogtreecommitdiff
path: root/website
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>2008-09-03 11:39:28 -0400
committerDaniel Kahn Gillmor <dkg@fifthhorseman.net>2008-09-03 11:39:28 -0400
commit623aef0f5ac9e56d9654d96bdeb3b096592f611e (patch)
treeadb627387ecf9c54680eca65e0bb1b775bf45004 /website
parent0adb6964e3876fdc79a2b43db1c9073c696d952a (diff)
added ridiculously scant first draft of document about gpg trust model.
Diffstat (limited to 'website')
-rw-r--r--website/trust-models.mdwn21
1 files changed, 21 insertions, 0 deletions
diff --git a/website/trust-models.mdwn b/website/trust-models.mdwn
new file mode 100644
index 0000000..60aa680
--- /dev/null
+++ b/website/trust-models.mdwn
@@ -0,0 +1,21 @@
+[[meta title
+You can see your trust database parameters like this:
+
+ gpg --with-colons --list-key bogusgarbagehere 2>/dev/null | head -n1
+
+for me, it looks like this:
+
+ tru::1:1220401097:1220465006:3:1:5
+
+These colon-delimited records say (in order):
+
+ * `tru`: this is a trust database record
+ * `<empty>`: the trust database is not stale (might be 'o' for old, or 't' for "built with different trust model and not yet updated")
+ * `1`: uses new "PGP" trust model: this is just the old trust model plus trust signatures. I'll go into trust signatures later.
+ * `1220401097`: seconds since the epoch that i created the trust db.
+ * `1220465006`: seconds after the epoch that the trustdb will need to be rechecked (usually due to the closest pending expiration, etc)
+ * `3`: Either 3 certifications from keys with marginal ownertrust are needed for full User ID+Key validity
+ * `1`: Or 1 certification from a key with full ownertrust is needed for full User ID+Key validity
+ * `5`: max_cert_depth (not sure exactly how this is used)
+
+