summaryrefslogtreecommitdiffstats
path: root/src/keylist.c
diff options
context:
space:
mode:
authorWerner Koch <[email protected]>2025-05-05 15:52:08 +0200
committerWerner Koch <[email protected]>2025-05-05 16:01:10 +0200
commitbfd320abfeaf0c7a16af3057279c77a45bfa961a (patch)
treef5d006d0bd9eeb672bafe6c4ec17a5756c66cadf /src/keylist.c
parentMark the subkey used to find a key. (diff)
downloadgpgme-bfd320abfeaf0c7a16af3057279c77a45bfa961a.tar.gz
gpgme-bfd320abfeaf0c7a16af3057279c77a45bfa961a.zip
Allow signing using an exactly specified subkey.
* src/engine-gpg.c (append_args_from_signers): Detect exactly specified keys and apped the '!' suffix. -- Due to the ABI break which removed long long deprecated functions we can also risk to introduce a slight semantic change in the way signer keys are specified. The change is that iff a subkey-fingerprint with the '!' suffix was used to lookup a signer's key we now use this specific subkey and not any key gpg considers to be a good signing subkey. Most people would have considered the old behaviour anyway as a bug because it differs from what gpg uses at the command line. GnuPG-bug-id: 3325 Suggested-by: Benjamin Kibbey
Diffstat (limited to 'src/keylist.c')
-rw-r--r--src/keylist.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/keylist.c b/src/keylist.c
index 11b68408..c0bf2155 100644
--- a/src/keylist.c
+++ b/src/keylist.c
@@ -1359,7 +1359,7 @@ gpgme_op_keylist_ext_start (gpgme_ctx_t ctx, const char *pattern[],
err = maybe_setup_for_requested_subkey (opd, pattern[i]);
if (err)
return TRACE_ERR (err);
- /* We can only handle one exact subnkey request. Thus we
+ /* We can only handle one exact subkey request. Thus we
* stop after the first seen. */
if (opd->requested_subkey)
break;