Re: GPG key-fetching

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

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

Michael Richardson <mc...@sa...> writes:
 
>   Can't you just reuse the whole pgp2 interface that talks to finger and
> to the key servers? You just need to call "gpg --import" instead of "pgp"
> to suck the key in at the end of the dialogue.

In the finger case this is exactly what I planned to do ;-) But for the
keyserver case I agree with Simon and think that it is better to let gpg
do all the error handling and stuff like that. It would unnecessarily blow
our code if we write an own function for every possible protocol. To finger
I would make an exception because it is widely used and up to now (to my
knowledge) not directly supported by gpg.

I hope within a few weeks I can send some results here.

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/Tgx6MdSnPCFfnIcRAiGSAJ9AzrwOgq2fR9BCGaU+v9XxmQQIlACfSiEg
R8Eq76LdI0b59+gVZ28bZN8=
=zzTA
-----END PGP SIGNATURE-----