[git] GnuPG - branch, master, updated. gnupg-2.2.7-200-g420dc2b

[by Werner Koch]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The GNU Privacy Guard".

The branch, master has been updated
       via  420dc2b49ad816bdd27b40db45d900551c71476f (commit)
      from  ed8fe21e6612401846fc4af8631f0136dc633c67 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 420dc2b49ad816bdd27b40db45d900551c71476f
Author: Werner Koch <wk at gnupg.org>
Date:   Wed Aug 29 15:04:44 2018 +0200

    doc: Minor additions to the gpg man page
    
    --
    
    Includes a fix for
    GnuPG-bug-id: 3906
    
    Signed-off-by: Werner Koch <wk at gnupg.org>

diff --git a/doc/gpg.texi b/doc/gpg.texi
index c4bc354..7f55cc7 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -675,6 +675,10 @@ supplied passphrase is used for the new key and the agent does not ask
 for it.  To create a key without any protection @code{--passphrase ''}
 may be used.
 
+Note that it is possible to create a primary key and a subkey using
+non-default algorithms by using ``default'' and changing the default
+parameters using the option @option{--default-new-key-algo}.
+
 @item --quick-set-expire @var{fpr} @var{expire} [*|@var{subfprs}]
 @opindex quick-set-expire
 With two arguments given, directly set the expiration time of the
@@ -702,7 +706,8 @@ and other ECC curves.  For example the string ``rsa'' adds an RSA key
 with the default key length; a string ``rsa4096'' requests that the
 key length is 4096 bits.  The string ``future-default'' is an alias
 for the algorithm which will likely be used as default algorithm in
-future versions of gpg.
+future versions of gpg.  To list the supported ECC curves the command
+ at code{gpg --with-colons --list-config curve} can be used.
 
 Depending on the given @var{algo} the subkey may either be an
 encryption subkey or a signing subkey.  If an algorithm is capable of
@@ -3353,13 +3358,14 @@ user.
 @opindex override-session-key
 Don't use the public key but the session key @var{string} respective
 the session key taken from the first line read from file descriptor
- at var{fd}.  The format of this string is the same as the one printed
-by @option{--show-session-key}. This option is normally not used but
+ at var{fd}.  The format of this string is the same as the one printed by
+ at option{--show-session-key}. This option is normally not used but
 comes handy in case someone forces you to reveal the content of an
 encrypted message; using this option you can do this without handing
 out the secret key.  Note that using @option{--override-session-key}
 may reveal the session key to all local users via the global process
-table.
+table.  Often it is useful to combine this option with
+ at option{--no-keyring}.
 
 @item --ask-sig-expire
 @itemx --no-ask-sig-expire

-----------------------------------------------------------------------

Summary of changes:
 doc/gpg.texi | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
The GNU Privacy Guard
http://git.gnupg.org