Receiving a key on standard output

[Thomas Arend]

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

Am Freitag, 3. Januar 2003 20:47 schrieb David Shaw:
> On Fri, Jan 03, 2003 at 08:41:47PM +0100, Thomas Arend wrote:
> > Am Freitag, 3. Januar 2003 01:54 schrieb David Shaw:
> > > On Thu, Jan 02, 2003 at 01:30:44PM -0500, Jason Harris wrote:
> > > > On Thu, Jan 02, 2003 at 02:19:57PM -0000, greg@turnstep.com wrote=
:
> > > >
> > > > NB:  The PGP signature on your message is bad.
> > > >
> > > > [fetching a key to a file]
> > > > Run gpgkeys_* directly (it has been covered on one of these lists
> > > > before).  See ./code/lget[.asc] on my website for an example.
> > >
> > > The only difficulty with this is that versions of GnuPG less than 1=
=2E3
> > > don't have a gpgkeys_hkp - only gpgkeys_ldap and gpgkeys_mailto.
> > > Without gpgkeys_hkp, I think the easiest way to fetch a key from a
> > > keyserver into a file is with wget or similar programs:
> > >
> > >  wget -O thefile.asc
> > > 'http://keyserver.kjsl.com:11371/pks/lookup?op=3Dget&search=3D0x992=
42560'
> > >
> > > 'thefile.asc' now has the key.
> > >
> > > David
> >
> > The following command will receive and import the key
> >
> > wget -O - \
> > 'http://keyserver.kjsl.com:11371/pks/lookup?op=3Dget&search=3D0x99242=
560' |
> > gpg \ - --import
>
> Why bother with that?  Just do 'gpg --recv-keys 99242560'
>
> The reason to retrieve it to a file first was so that the original
> poster could then examime the file before importing the key.
>
> David

You arre right. I thougt of this myself. But you were faster.=20
(BTW I learned the -O - option of wget)

But I think it's better to view the keys with gpg --edit-keys than to vie=
w it=20
in a file. The file is a little bit cryptic.

Mit freundlichen Gr=FC=DFen

Thomas Arend
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+Fevu2TqsmTFMxwkRAvF7AKCgVE09hjZGkkTKJnWiJA2EDIjexwCgnwrx
cP58T+jKw9ZqMMxUrR1Bxxc=3D
=3DjIyE
-----END PGP SIGNATURE-----