From 146fa8d6c0ace2f9560341171a491e9ddb0361ae Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dominik=20Sch=C3=BCrmann?= Date: Mon, 16 Mar 2015 15:05:39 +0100 Subject: [PATCH] Clarify certification help screen --- OpenKeychain/src/main/res/raw/help_certification.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/OpenKeychain/src/main/res/raw/help_certification.html b/OpenKeychain/src/main/res/raw/help_certification.html index 8228a4ac1..d4aff1ad7 100644 --- a/OpenKeychain/src/main/res/raw/help_certification.html +++ b/OpenKeychain/src/main/res/raw/help_certification.html @@ -22,10 +22,10 @@ To confirm keys between more than two persons, we suggest to use the key exchang This certification is a "generic certification (0x10)" described in the standard by: "The issuer of this certification does not make any particular assertion as to how well the certifier has checked that the owner of the key is in fact the person described by the User ID."

-

Traditionally, certifications (often with higher certification levels, such as "positive certifications" (0x13)) are organized in OpenPGP's Web of Trust. +

Traditionally, certifications (also with higher certification levels, such as "positive certifications" (0x13)) are organized in OpenPGP's Web of Trust. Our model of key confirmation is a much simpler concept to avoid common usability problems related to this Web of Trust. We assume that keys are verified only to a certain degree that is still usable enough to be executed "on the go". -We also do not implement (potentially transitive) trust signatures or any other internal trust model. +We also do not implement (potentially transitive) trust signatures or an ownertrust database like in GnuPG. Furthermore, keys which contain at least one user ID certified by a trusted key will be marked as "confirmed" in the key listings.