summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorWerner Koch <wk@gnupg.org>2024-06-11 15:39:00 +0200
committerWerner Koch <wk@gnupg.org>2024-06-11 15:39:00 +0200
commit12ac129a709c24ec661a9dec02f2c25c1b6e9450 (patch)
treefe0f6b446f2d75772b9bf7a11e97381aa7dec161 /doc
parentgpg: Do not bail out on secret keys with an unknown algo (diff)
downloadgnupg2-12ac129a709c24ec661a9dec02f2c25c1b6e9450.tar.xz
gnupg2-12ac129a709c24ec661a9dec02f2c25c1b6e9450.zip
gpg: Allow shortcut algo string "pqc" for --quick-gen-key.
* g10/keygen.c (PQC_STD_KEY_PARAM): New. (quickgen_set_para): Always store the provided NBITS. (parse_key_parameter_string): Detect the special value "pqc". (quick_generate_keypair): Ditto. -- With this change we can finally do a gpg --quick-gen-key --batch --passphrase='' foo@example.org pqc and get a full key. Currently with a brainpoolp386r1 primary key and a Kyber768_brainpoolp256 subkey.
Diffstat (limited to 'doc')
-rw-r--r--doc/gpg.texi14
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/gpg.texi b/doc/gpg.texi
index 203f3339f..b69f39fe9 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -686,12 +686,14 @@ force the creation of the key will show up.
If @var{algo} or @var{usage} are given, only the primary key is
created and no prompts are shown. To specify an expiration date but
-still create a primary and subkey use ``default'' or
-``future-default'' for @var{algo} and ``default'' for @var{usage}.
-For a description of these optional arguments see the command
-@code{--quick-add-key}. The @var{usage} accepts also the value
-``cert'' which can be used to create a certification only primary key;
-the default is to a create certification and signing key.
+still create a primary and a subkey use ``default'',
+``future-default'', or ``pqc'' for @var{algo} and ``default'' for
+@var{usage}. For a description of these optional arguments see the
+command @code{--quick-add-key}; the value ``pqc'' create a key with a
+quantum-resistant encryption encryption subkey. The @var{usage}
+accepts also the value ``cert'' which can be used to create a
+certification only primary key; the default is to a create
+certification and signing key.
The @var{expire} argument can be used to specify an expiration date
for the key. Several formats are supported; commonly the ISO formats