From aff9aaac68450e76f84d0f9a3feabffe9e82dd7e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ingo=20Kl=C3=B6cker?= Date: Wed, 27 Apr 2022 16:57:17 +0200 Subject: core: Support --locate-external-keys command of gpg * src/gpgme.h.in (GPGME_KEYLIST_MODE_FORCE_EXTERN): New. (GPGME_KEYLIST_MODE_LOCATE_EXTERNAL): New. * src/gpgme.c (gpgme_set_keylist_mode): Check for invalid mode. * src/engine-gpg.c (gpg_keylist_build_options): Use "--locate-external-keys" instead of "--locate-keys" if flag is set. * src/gpgme-json.c (op_keylist): New flag "force-extern". * src/gpgme-tool.c (gt_get_keylist_mode, cmd_keylist_mode): Handle new mode. -- GnuPG-bug-id: 5951 --- doc/gpgme.texi | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 'doc') diff --git a/doc/gpgme.texi b/doc/gpgme.texi index a7392d78..7f178158 100644 --- a/doc/gpgme.texi +++ b/doc/gpgme.texi @@ -2872,6 +2872,26 @@ validity information from an internal cache. This might be an expensive operation and is in general not useful. Currently only implemented for the S/MIME backend and ignored for other backends. +@item GPGME_KEYLIST_MODE_FORCE_EXTERN +@since{1.18.0} + +The @code{GPGME_KEYLIST_MODE_FORCE_EXTERN} symbol specifies that only +external sources should be searched for keys in the keylisting +operation. If used in combination with @code{GPGME_KEYLIST_MODE_LOCATE}, +the keylisting results in a @code{--locate-external-keys} for +@code{GPGME_PROTOCOL_OpenPGP}. The combination with +@code{GPGME_KEYLIST_MODE_LOCAL}, but without @code{GPGME_KEYLIST_MODE_EXTERN} +is not allowed. Currently only implemented for the OpenPGP backend and +ignored for other backends. + +@item GPGME_KEYLIST_MODE_LOCATE_EXTERNAL +@since{1.18.0} + +This is a shortcut for the combination of +@code{GPGME_KEYLIST_MODE_LOCATE} and @code{GPGME_KEYLIST_MODE_FORCE_EXTERN}, +which results in a @code{--locate-external-keys} for +@code{GPGME_PROTOCOL_OpenPGP}. + @end table At least one of @code{GPGME_KEYLIST_MODE_LOCAL} and -- cgit v1.2.1