Receiving a key on standard output

[5468696A6D656E]

On Thu, Jan 02, 2003 at 02:18:26PM +0100, 5468696A6D656E wrote:
> when i do a:
> gpg --keyserver wwwkeys.nl.pgp.net --recv-key 84321DED
> it will wirte it directly to my public keyring
> 
> How can i make it so it writes the asci armoured key to standard
> out, so i will be able to check it before i --import it to
> my public keyring? Any help would be appriciated.

I felt i had to clarify this a bit. I am not looking for the option --search-key
because that requires interaction. Here is what i do now, and i hope some of you
could help me to make less steps to reach the same goal:

1)
touch /tmp/tmpfile.gpg
2)
gpg --keyserver wwwkeys.nl.pgp.net --homedir /tmp --keyring /tmp/tmpfile.gpg --batch --recv-key 84321DED
gpg: /tmp/secring.gpg: keyring created
gpg: /tmp/pubring.gpg: keyring created
gpg: requesting key 84321DED from wwwkeys.nl.pgp.net ...
gpg: key 84321DED: invalid subkey binding
gpg: key 84321DED: public key imported
gpg: /tmp/trustdb.gpg: trustdb created
gpg: Total number processed: 1
gpg:               imported: 1
3)
rm -rf /tmp/secring.gpg /tmp/pubring.gpg /tmp/trustdb.gpg
4)
gpg --homedir /tmp --keyring /tmp/bladir --list-sigs 84321DED > /tmp/84321DED
5)
rm -rf /tmp/tmpfile.gpg

if i dont do step 1, it will put the file in /tmp/pubring.gpg, gpg doesn't create the file by itself
At 2) it creates the files secring.gpg. pubring.gpg and trustdb.gpg, even when specifying different
files with --keyring and --secret-keyring. Shouldn't it default to NOT create those files when you
specify files with different names?

Basically, what i will do after this is a gpg --with-colons --batch /tmp/84321DED and ask the
user after this output whether he/she wants to import it.



-- 
__Thijmen Klok________