Receiving a key on standard output

[greg@turnstep.com]

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


> At 2) it creates the files secring.gpg. pubring.gpg and 
> trustdb.gpg, even when specifying different files
..

What is wrong with this approach? Seems to me that this 
should work fine:

1) gpg --homedir /tmp --keyserver pgp.mit.edu --recv-key 84321DED

2) gpg --homedir /tmp --with-colons --list-keys 84321DED

3) Present the output to the user. 
If acceptable, import to the "real" directory:

4) gpg --keyserver pgp.mit.edu --recv-key 84321DED

The file in /tmp will end up having multiple keys, but this 
should not be a problem. If it is, use the --delete-key command 
after doing the above.


Also check out the --dry-run option, which generates all the normal 
output, but makes no physical changes. You cannot get the ascii 
armored key, but you can check the output for the key ID, name, 
email, and comment like this:

gpg -v --keyserver pgp.mit.edu --dry-run --recv-key 84321DED

This avoids worrying about which files to use. Just read the output 
and present it to the user.


Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 20021007
EICS: -D 9079f3957ed45bae12d990be5f4edf17

-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html

iD8DBQE+FEzlvJuQZxSWSsgRAu9yAKDBxBUxUqVIGeTTNOzeQ4YKK0AC1gCfdpun
lGs8J6kxb7iEIy3whymaGGo=
=KhDI
-----END PGP SIGNATURE-----