Add GPGME_CREATE_GROUP flag for gpgme_op_createkey and _createsubkey.

* src/gpgme.h.in (GPGME_CREATE_GROUP): New.
* src/engine-gpg.c (gpg_add_algo_usage_expire): Pass to engine.
* tests/run-genkey.c (parse_usage_string): Support here too.

1 files changed, 26 insertions, 0 deletions

diff --git a/doc/gpgme.texi b/doc/gpgme.texi
index ad120465..cdacd9e1 100644
--- a/doc/gpgme.texi
+++ b/doc/gpgme.texi
@@ -3645,6 +3645,10 @@ This is true if the subkey can be used for authentication.
 This is true if the subkey can be used for qualified signatures
 according to local government regulations.
 
+@item unsigned int is_cardkey : 1
+
+This is true if the secret key or subkey is stored on a smart card.
+
 @item unsigned int is_de_vs : 1
 @since{1.8.0}
 
@@ -3653,6 +3657,23 @@ information in Germany at the restricted level (VS-NfD).  This are
 currently RSA keys of at least 3072 bits or ECDH/ECDSA keys using a
 Brainpool curve.
 
+@item unsigned int can_renc : 1;
+@since {1.20.0}
+
+This is true if the key can be used for restricted encryption (ADSK).
+
+@item unsigned int can_timestamp : 1;
+@since {1.20.0}
+
+This is true if the key can be used for timestamping.
+
+@item unsigned int is_group_owned : 1;
+@since {1.20.0}
+
+This is true if the private key or subkey is possessed by more than
+one person.  Such a key is often called a ``team key''.
+
+
 @item unsigned int beta_compliance : 1;
 @since{1.24.0}
 The compliance flags (e.g. is_de_vs) are set but the software has not
@@ -4479,6 +4500,11 @@ the hexified fingerprint of the ADSK to be added; this must be a
 subkey.  If the string "default" is used for @var{algo} the engine
 will add all ADSK as it would do for new keys.
 
+@item GPGME_CREATE_GROUP
+@since{2.0.0}
+
+Set the ``group owned'' flag for the new generated key or subkey.
+
 @end table
 
 After the operation completed successfully, information about the