summaryrefslogtreecommitdiff
path: root/website
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>2008-09-05 00:20:27 -0400
committerDaniel Kahn Gillmor <dkg@fifthhorseman.net>2008-09-05 00:20:27 -0400
commit9352a728617d422f5b86100efdcbc72a6d3ca78a (patch)
treea46dc52da5688ec5f439b79b3ab336a3f2ffca36 /website
parent9556a2f1659aa6432cc74469a25d401319d74e79 (diff)
changed intro to trust model docs.
Diffstat (limited to 'website')
-rw-r--r--website/trust-models.mdwn10
1 files changed, 5 insertions, 5 deletions
diff --git a/website/trust-models.mdwn b/website/trust-models.mdwn
index 8fee5cb..789e3a3 100644
--- a/website/trust-models.mdwn
+++ b/website/trust-models.mdwn
@@ -6,11 +6,11 @@ Monkeysphere relies on GPG's definition of the OpenPGP web of trust,
so it's important to understand how GPG calculates User ID validity
for a key.
-The basic question asked is: For a given User ID on a specific key,
-given some set of valid certifications (signatures), and some explicit
-statements about whose certifications you think are trustworthy
-(ownertrust), should we consider this User ID to be legitimately
-attached to this key (a "valid" User ID)?
+The basic question that a trust model tries to answer is: For a given
+User ID on a specific key, given some set of valid certifications
+(signatures), and some explicit statements about whose certifications
+you think are trustworthy (ownertrust), should we consider this User
+ID to be legitimately attached to this key (a "valid" User ID)?
It's worth noting that there are two integral parts in this
calculation: