[PATCH] correct "trusted" to "valid" for trust-model always

Daniel Kahn Gillmor dkg at fifthhorseman.net
Fri Oct 3 18:52:11 CEST 2014


On Tue 2014-04-22 18:46:15 -0400, Daniel Kahn Gillmor wrote:
> With --trust-model=always, all keys and user IDs are considered
> automatically valid; they are not automatically trusted (setting
> universal ownertrust to anything other than "ultimate" would be
> insufficient to acheive the effect of --trust-model=always, due to
> --max-cert-depth and certificate path reachability).
>
> Thanks to Nicolai Josuttis for pointing out this documentation error.
> ---
>  doc/gpg.texi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/gpg.texi b/doc/gpg.texi
> index 26179bd..8274da5 100644
> --- a/doc/gpg.texi
> +++ b/doc/gpg.texi
> @@ -1428,7 +1428,7 @@ Set what trust model GnuPG should follow. The models are:
>    @item always
>    @opindex trust-mode:always
>    Skip key validation and assume that used keys are always fully
> -  trusted. You generally won't use this unless you are using some
> +  valid. You generally won't use this unless you are using some
>    external validation scheme. This option also suppresses the
>    "[uncertain]" tag printed with signature checks when there is no
>    evidence that the user ID is bound to the key.
> -- 
> 1.9.2

Any followup on this?  This patch appears to be still unapplied on
STABLE-BRANCH-1-4, STABLE-BRANCH-2-0, and master.

                   --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 948 bytes
Desc: not available
URL: </pipermail/attachments/20141003/f058ab13/attachment.sig>


More information about the Gnupg-devel mailing list