Details here http://superuser.com/questions/1064701/how-to-specify-exact-
matching-in-gnupg-2-1s-quick-sign-key#1064701
TL;DR: matching is always fuzzy. Specifying name signs all keys that contain
name as a substring. = doesn't work to restrict to exact matching. uid
hashes (as listed with -k --with-colons) don't work (in specifing an exact
uid to --quick-sign-key) at all.
Please do not refer to another web site - write your report here.
Why don't you use the entire user id? This quarantees that you select the right
one (match is case insensitive). Note that this matching is different from the
key selection mechanism becuase it is inteded to be used by other tools.
The problem is that using an entire uid that is a substring of another
uid selects both uids. This makes it impossible to select a uid that is
a substring of another.
On 04/14/2016 04:18 PM, Werner Koch via BTS wrote:
Werner Koch <wk@gnupg.org> added the comment:
Please do not refer to another web site - write your report here.
Why don't you use the entire user id? This quarantees that you select the right
one (match is case insensitive). Note that this matching is different from the
key selection mechanism becuase it is inteded to be used by other tools.
status: unread -> chatting
GnuPG's BTS <gnupg@bugs.g10code.com>
<T2315>
commit d02de6c should fix that.
Use '=' for an exact match and optionally '*' for a substring match.