Is there a command-line equivalent to "Only return exact matches"?
David Shaw
dshaw at jabberwocky.com
Sun Jun 29 18:38:15 CEST 2003
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Jun 25, 2003 at 05:12:53PM +0930, jonathan soong wrote:
> >
> >
> >How do you know what exact match to search for then? If you don't know the
> >key ID in advance, I assume you are talking about a key defined by some
> >other parameter like user ID, and then you can not be sure that there will
> >be only one exact match.
> >
> >
> Yes this is exactly the situation i am talking of.
>
> :) This is for a custom application we are actually writing. So we
> wanted the users the option to
> change their keys, and our encryption tool would then get their new keys
> off the PKS server.
> E.g. user ID, could be "Jon-789", which we would specify, but this user
> could create new keys.
> - we always want to get the latest keys for 'Jon-789'
>
> The --search-keys option would think of 'Jon-789' as two words, rather
> than one ..
Not the --search-keys command. Whatever you enter for the search
argument gets passed to the keyserver. The PKS keyserver treats
hyphens as word separators.
The keyserver does have a "exact match" command, but GnuPG does not
currently have a way to set it. In any event, the exact meaning of
"exact match" is dependent on the keyserver, so it might not be
supported in a given keyserver.
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3rc1 (GNU/Linux)
Comment: Key available at http://www.jabberwocky.com/david/keys.asc
iD8DBQE++lZk4mZch0nhy8kRAp+rAKDSiwGmu9LdHbAvbTq/abR0wAiPmACfcnFk
NJKpozAdfIqmjlU9DAvA9Jo=
=lYMz
-----END PGP SIGNATURE-----
More information about the Gnupg-devel
mailing list