1
0
mirror of git://git.gnupg.org/gnupg.git synced 2024-12-22 10:19:57 +01:00
Werner Koch e1e35db510
gpg: Fix the use of future-default with --quick-add-key.
* g10/keygen.c (parse_key_parameter_part): Add arg clear_cert.
(parse_key_parameter_string): Add arg suggested_use and implement
fallback.  Change callers to pass 0 for new arg.
(parse_algo_usage_expire): Pass the parsed USAGESTR to
parse_key_parameter_string so that it can use it in case a subkey is
to be created.
--

The problem here was that future-default gives the primary and subkey
algorithm.  However, when using future-default for adding a key, the
second part was always used which is for encryption.  If the caller
now wanted to create a signing subkey using the future-default
parameters this did not worked.

  gpg --batch --passphrase "" --quick-add-key FPR future-default encr

aready worked as did

  gpg --batch --passphrase "" --quick-add-key FPR ed25519 sign

but

  gpg --batch --passphrase "" --quick-add-key FPR future-default sign

does only work with this fix.

GnuPG-bug-id: 3747
Signed-off-by: Werner Koch <wk@gnupg.org>
2018-01-18 13:39:19 +01:00
..
2017-03-07 20:25:54 +09:00
2017-03-07 20:25:54 +09:00
2017-11-22 20:54:47 +01:00
2017-03-07 20:25:54 +09:00
2017-03-07 20:25:54 +09:00
2017-12-13 10:07:30 +01:00
2015-02-04 09:15:34 +01:00
2015-02-04 09:15:34 +01:00
2017-03-07 20:25:54 +09:00
2017-09-13 09:18:15 +02:00
2017-03-07 20:25:54 +09:00
2017-03-07 20:25:54 +09:00
2017-03-07 20:25:54 +09:00
2017-08-08 11:43:22 +02:00
2017-03-07 20:25:54 +09:00
2017-12-13 11:03:06 +01:00
2017-03-07 20:25:54 +09:00
2017-03-07 20:25:54 +09:00
2017-03-07 20:25:54 +09:00
2017-01-23 19:16:55 +01:00
2017-02-21 13:11:46 -05:00
2017-03-07 20:32:09 +09:00
2017-03-07 20:25:54 +09:00
2017-04-28 10:06:33 +09:00
2017-08-24 20:26:19 +02:00
2016-03-08 14:08:49 +01:00
2017-04-28 10:06:33 +09:00
2017-03-31 20:07:20 +02:00
2017-03-07 20:25:54 +09:00
2016-12-06 12:16:56 +01:00
2017-12-04 19:26:49 +09:00
2017-04-28 10:06:33 +09:00