Re: [PATCH] GPG key-fetching

[Kevin B. <kb...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brian Warner <wa...@lo...> writes:

> I like it.

Glad to hear this ;-)

> Can the --recv-keys option accept arbitrary names? Or can it only
> take hex keyids? If so, we should document that limitation heavily: none of
> the other keyfetching code has it.

It can only take hex keyids. For full names there exists the option
- --search-keys, but with this you end up in a dialog which lets you
select the desired one from the matching keys. Furthermore it works
_only_ with real names not with ids. I guess using this instead of
- --recv-key would introduce trouble with mc-gpg-always-fetch.

How does pgp solve the problem?

> If it succeeds, it should list the number of keys imported (although really
> what would be useful is the full name that's attached to the key, so you can
> check to see if you got the right one).

The current patch should report the full name on success (I think this
works only with one id right now, needs testing).

> If it fails, perhaps we could just (message) the contents of
> stderr-buf?

Yes, I will do this.

> thanks!
>  -Brian

Kevin

- -- 
publickey: http://www.icbm.de/~bube/publickey.txt
fingerprint: 607B 39BC C9E9 0F5E EF7F  4557 31D4 A73C 215F 9C87
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQE/XDd6MdSnPCFfnIcRAp2vAJ9FktuUJs6eu9hvQdffIBnryZE5+gCfal1K
X/X/bsi6lHgpnJdiQb2RIB8=
=KQrr
-----END PGP SIGNATURE-----