/usr/share/doc/gnupg-doc/GNU_Privacy

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Validating other keys on your public keyring</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="The GNU Privacy Handbook"
HREF="book1.htm"><LINK
REL="UP"
TITLE="Key Management"
HREF="c236.htm"><LINK
REL="PREVIOUS"
TITLE="Key Management"
HREF="c236.htm"><LINK
REL="NEXT"
TITLE="Distributing keys"
HREF="x464.htm"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The GNU Privacy Handbook</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="c236.htm"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Key Management</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="x464.htm"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN335"
>Validating other keys on your public keyring</A
></H1
><P
>In Chapter <A
HREF="c15.htm"
>1</A
> a procedure was given to validate your
correspondents' public keys: a correspondent's key is validated by
personally checking his key's fingerprint and then signing his public
key with your private key.
By personally checking the fingerprint you can be sure that the
key really does belong to him, and since you have signed they key, you
can be sure to detect any tampering with it in the future.
Unfortunately, this procedure is awkward when either you must validate
a large number of keys or communicate with people whom you do not
know personally.</P
><P
>GnuPG addresses this problem with a mechanism popularly known
as the <I
CLASS="FIRSTTERM"
>web of trust</I
>.
In the web of trust model, responsibility for validating public
keys is delegated to people you trust.
For example, suppose
<P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>Alice has signed Blake's key, and</P
></LI
><LI
><P
>Blake has signed Chloe's key and Dharma's key.</P
></LI
></UL
>

If Alice trusts Blake to properly validate keys that he signs, then
Alice can infer that Chloe's and Dharma's keys are valid without
having to personally check them.
She simply uses her validated copy of Blake's public key to
check that Blake's signatures on Chloe's and Dharma's are good.
In general, assuming that Alice fully trusts everybody to properly
validate keys they sign, then any key signed by a valid key is also
considered valid.
The root is Alice's key, which is axiomatically assumed to be valid.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN346"
>Trust in a key's owner</A
></H2
><P
>In practice trust is subjective.
For example, Blake's key is valid to Alice since she signed it, but she
may not trust Blake to properly validate keys that he signs.
In that case, she would not take Chloe's and Dharma's key as valid
based on Blake's signatures alone.
The web of trust model accounts for this by associating with each
public key on your keyring an indication of how much you trust the
key's owner.
There are four trust levels.

<P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>unknown</DT
><DD
><P
>Nothing is known about the owner's judgment in key signing.
Keys on your public keyring that you do not own initially have
this trust level.</P
></DD
><DT
>none</DT
><DD
><P
>The owner is known to improperly sign other keys.</P
></DD
><DT
>marginal</DT
><DD
><P
>The owner understands the implications of key signing and
properly validates keys before signing them.</P
></DD
><DT
>full</DT
><DD
><P
>The owner has an excellent understanding of key signing,
and his signature on a key would be as good as your own.</P
></DD
></DL
></DIV
>

A key's trust level is something that you alone assign to the
key, and it is considered private information.
It is not packaged with the key when it is exported; it is even
stored separately from your keyrings in a separate database.</P
><P
>The GnuPG key editor may be used to adjust your trust in a key's owner.
The command is <B
CLASS="COMMAND"
>trust</B
>.
In this example Alice edits her trust in Blake and then updates
the trust database to recompute which keys are valid based on her new
trust in Blake.

<PRE
CLASS="SCREEN"
><TT
CLASS="PROMPT"
>alice%</TT
> <KBD
CLASS="USERINPUT"
>gpg --edit-key blake</KBD
>

pub  1024D/8B927C8A  created: 1999-07-02 expires: never      trust: q/f
sub  1024g/C19EA233  created: 1999-07-02 expires: never
(1)  Blake (Executioner) &lt;blake@cyb.org&#62;

<TT
CLASS="PROMPT"
>Command&#62;</TT
> <KBD
CLASS="USERINPUT"
>trust</KBD
>
pub  1024D/8B927C8A  created: 1999-07-02 expires: never      trust: q/f
sub  1024g/C19EA233  created: 1999-07-02 expires: never
(1)  Blake (Executioner) &lt;blake@cyb.org&#62;

Please decide how far you trust this user to correctly
verify other users' keys (by looking at passports,
checking fingerprints from different sources...)?

 1 = Don't know
 2 = I do NOT trust
 3 = I trust marginally
 4 = I trust fully
 s = please show me more information
 m = back to the main menu

<TT
CLASS="PROMPT"
>Your decision?</TT
> <KBD
CLASS="USERINPUT"
>3</KBD
>

pub  1024D/8B927C8A  created: 1999-07-02 expires: never      trust: m/f
sub  1024g/C19EA233  created: 1999-07-02 expires: never
(1)  Blake (Executioner) &lt;blake@cyb.org&#62;

<TT
CLASS="PROMPT"
>Command&#62;</TT
> <KBD
CLASS="USERINPUT"
>quit</KBD
>
[...]</PRE
>

Trust in the key's owner and the key's validity are indicated to the
right when the key is displayed.
Trust in the owner is displayed first and the key's validity is
second<A
NAME="AEN378"
HREF="#FTN.AEN378"
><SPAN
CLASS="footnote"
>[1]</SPAN
></A
>.
The four trust/validity levels are abbreviated: unknown (<TT
CLASS="LITERAL"
>q</TT
>),
none (<TT
CLASS="LITERAL"
>n</TT
>), marginal (<TT
CLASS="LITERAL"
>m</TT
>), and
full (<TT
CLASS="LITERAL"
>f</TT
>).
In this case, Blake's key is fully valid since Alice signed it herself.
She initially has an unknown trust in Blake to properly sign other keys
but decides to trust him marginally.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN385"
>Using trust to validate keys</A
></H2
><P
>The web of trust allows a more elaborate algorithm to be used to
validate a key.
Formerly, a key was considered valid only if you signed it personally.
A more flexible algorithm can now be used: a key <I
CLASS="EMPHASIS"
>K</I
> is considered valid
if it meets two conditions:
<P
></P
><OL
COMPACT="COMPACT"
TYPE="1"
><LI
><P
>it is signed by enough valid keys, meaning
<P
></P
><UL
COMPACT="COMPACT"
><LI
><P
>you have signed it personally,</P
></LI
><LI
><P
>it has been signed by one fully trusted key, or</P
></LI
><LI
><P
>it has been signed by three marginally trusted keys; and</P
></LI
></UL
></P
></LI
><LI
><P
>the path of signed keys leading from <I
CLASS="EMPHASIS"
>K</I
> back
to your own key is five steps or shorter.</P
></LI
></OL
>

The path length, number of marginally trusted keys required, and number
of fully trusted keys required may be adjusted.
The numbers given above are the default values used by GnuPG.</P
><P
><A
HREF="x335.htm#WOT-EXAMPLES"
>Figure 3-1</A
> shows a web of trust rooted at Alice.
The graph illustrates who has signed who's keys.
The table shows which keys Alice considers valid based on her
trust in the other members of the web.

This example assumes that two marginally-trusted keys or one
fully-trusted key is needed to validate another key.
The maximum path length is three.</P
><P
>When computing valid keys in the example, Blake and Dharma's are
always considered fully valid since they were signed directly
by Alice.
The validity of the other keys depends on trust.
In the first case, Dharma is trusted fully, which implies
that Chloe's and Francis's keys will be considered valid.
In the second example, Blake and Dharma are trusted marginally.
Since two marginally trusted keys are needed to fully validate a
key, Chloe's key will be considered fully valid, but Francis's
key will be considered only marginally valid.
In the case where Chloe and Dharma are marginally trusted,
Chloe's key will be marginally valid since Dharma's key is
fully valid.
Francis's key, however, will also be considered marginally
valid since only a fully valid key can be used to validate
other keys, and Dharma's key is the only fully valid key
that has been used to sign Francis's key.
When marginal trust in Blake is added, Chloe's key becomes
fully valid and can then be used to fully validate Francis's
key and marginally validate Elena's key.
Lastly, when Blake, Chloe, and Elena are fully trusted, this is
still insufficient to validate Geoff's key since the maximum
certification path is three, but the path length from Geoff
back to Alice is four.</P
><P
>The web of trust model is a flexible approach to the problem of safe
public key exchange.
It permits you to tune GnuPG to reflect how you use it.
At one extreme you may insist on multiple, short paths from your
key to another key <I
CLASS="EMPHASIS"
>K</I
> in order to trust it.
On the other hand, you may be satisfied with longer paths and
perhaps as little as one path from your key to the other
key <I
CLASS="EMPHASIS"
>K</I
>.
Requiring multiple, short paths is a strong guarantee
that <I
CLASS="EMPHASIS"
>K</I
> belongs to whom your think it does.
The price, of course, is that it is more difficult to validate keys
since you must personally sign more keys than if you accepted fewer
and longer paths.</P
><DIV
CLASS="FIGURE"
><A
NAME="WOT-EXAMPLES"
></A
><DIV
CLASS="MEDIAOBJECT"
><P
><IMG
SRC="signatures.jpg"></P
></DIV
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN421"
></A
><TABLE
BORDER="1"
FRAME="border"
RULES="all"
CLASS="CALSTABLE"
><COL
WIDTH="1*"
TITLE="ONE"><COL
WIDTH="1*"
TITLE="TWO"><COL
WIDTH="1*"
TITLE="THREE"><COL
WIDTH="1*"
TITLE="FOUR"><THEAD
><TR
><TH
COLSPAN="2"
ALIGN="CENTER"
>trust</TH
><TH
COLSPAN="2"
ALIGN="CENTER"
>validity</TH
></TR
><TR
><TH
ALIGN="CENTER"
>marginal</TH
><TH
ALIGN="CENTER"
>full</TH
><TH
ALIGN="CENTER"
>marginal</TH
><TH
ALIGN="CENTER"
>full</TH
></TR
></THEAD
><TBODY
><TR
><TD
>&nbsp;</TD
><TD
>Dharma</TD
><TD
>&nbsp;</TD
><TD
>Blake, Chloe, Dharma, Francis</TD
></TR
><TR
><TD
>Blake, Dharma</TD
><TD
>&nbsp;</TD
><TD
>Francis</TD
><TD
>Blake, Chloe, Dharma</TD
></TR
><TR
><TD
>Chloe, Dharma</TD
><TD
>&nbsp;</TD
><TD
>Chloe, Francis</TD
><TD
>Blake, Dharma</TD
></TR
><TR
><TD
>Blake, Chloe, Dharma</TD
><TD
>&nbsp;</TD
><TD
>Elena</TD
><TD
>Blake, Chloe, Dharma, Francis</TD
></TR
><TR
><TD
>&nbsp;</TD
><TD
>Blake, Chloe, Elena</TD
><TD
>&nbsp;</TD
><TD
>Blake, Chloe, Elena, Francis</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
><B
>Figure 3-1. A hypothetical web of trust</B
></P
></DIV
></DIV
></DIV
><H3
CLASS="FOOTNOTES"
>Notes</H3
><TABLE
BORDER="0"
CLASS="FOOTNOTES"
WIDTH="100%"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN378"
HREF="x335.htm#AEN378"
><SPAN
CLASS="footnote"
>[1]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>GnuPG overloads the word ``trust'' by using it to mean
trust in an owner and trust in a key.
This can be confusing.
Sometimes trust in an owner is referred to as
<I
CLASS="FIRSTTERM"
>owner-trust</I
> to
distinguish it from trust in a key.
Throughout this manual, however, ``trust'' is used to
mean trust in a key's
owner, and ``validity'' is used to mean trust that a key
belongs to the human associated with the key ID.</P
></TD
></TR
></TABLE
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="c236.htm"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="book1.htm"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="x464.htm"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Key Management</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="c236.htm"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Distributing keys</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
gnupg-doc 2003.04.06+dak1-1ubuntu1 / usr / share / doc / gnupg-doc / GNU_Privacy_Handbook / html / x335.htm
