How to use a keyserver
Ingo Klöcker
ingo.kloecker@epost.de
Thu Jan 16 02:01:02 2003
--Boundary-02=_gLgJ+z+qDlIwVoy
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline
On Wednesday 15 January 2003 15:12, Charly Avital wrote:
> Actual example:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
> [---------]% gpg --keyserver x-hkp://keyserver.kjsl.com --search-keys
> Ingo Kloecker gpg: searching for "Ingo Kloecker" from HKP server
> keyserver.kjsl.com Keys 1-2 of 2 for "Ingo Kloecker"
> (1) Ingo Kl\xf6\x63ker <Kloecker@ESIK.de>
> 1024 bit DSA key F661F608, created 2002-01-24
> (2) Ingo Kloecker <ingo@matha.rwth-aachen.de>
> 1024 bit RSA key AC0EB35D, created 1997-03-12
> Enter number(s), N)ext, or Q)uit >
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>
> Please note that "Kl\xf6\x63ker" is, I think, the server's rendition
> of: Kl[o+umlaut]cker.
Actually "Kl\xf6\x63ker" is what you get when you list a key which was=20
generated with PGP since PGP doesn't encode non-ASCII characters with=20
the utf-8 encoding (which is a must according to the OpenPGP specs).=20
Instead PGP simply uses latin1.
And JFYI, the first key above is not my key. It belongs to a name-clone.=20
The second key is my old key and shouldn't be used anymore.
To get the keys I currently use try 'gpg --search-keys ingo.kloecker'.
Regards,
Ingo
--Boundary-02=_gLgJ+z+qDlIwVoy
Content-Type: application/pgp-signature
Content-Description: signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQA+JgLgGnR+RTDgudgRAs1WAKCu75tI/gTiPKS5RwWrSJj5sDKegQCgiYZa
SmUmUBrEiDGWGOgMDbbH5zQ=
=DmQq
-----END PGP SIGNATURE-----
--Boundary-02=_gLgJ+z+qDlIwVoy--