From 0c52bfa3955b629038a6ac42c48356b88fce181e Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Fri, 3 Oct 2014 20:19:08 +0200 Subject: [PATCH] doc: Minor fix. -- Due to todays reminder: 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. --- NEWS | 9 ++++++++- doc/gpg.texi | 2 +- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 4d533ce7e..fe80aabcf 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,10 @@ +Noteworthy changes in version 2.1.0 (unreleased) +------------------------------------------------ + + * For a complete list of changes see the lists of changes for the + 2.1.0 beta versions below. + + Noteworthy changes in version 2.1.0-beta864 (2014-10-03) -------------------------------------------------------- @@ -11,7 +18,7 @@ Noteworthy changes in version 2.1.0-beta864 (2014-10-03) * gpg: Default keyring is now created with a .kbx suffix. - * gpg: Add a shortcut to key capabilies menu (e.g. "=e" sets the + * gpg: Add a shortcut to the key capabilies menu (e.g. "=e" sets the encryption capabilities). * gpg: Fixed obsolete options parsing. diff --git a/doc/gpg.texi b/doc/gpg.texi index 33329a130..002e888ce 100644 --- a/doc/gpg.texi +++ b/doc/gpg.texi @@ -1425,7 +1425,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. Note that this