Importing keys

[A Guy Called Tyketto]

--nFreZHaLTZJo0R7j
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 28, 2000 at 10:56:02AM +0200, Nils Ellmenreich wrote:
>=20
> >>>"AGCT" =3D=3D A Guy Called Tyketto <tyketto@wizard.com> writes:
>=20
>=20
>  AGCT>         Actually, you're doing everything right, except that the k=
ey that=20
>  AGCT> you're importing, was not signed by the person who owns it (self-s=
ignature, I=20
>  AGCT> believe). This is most common with PGP 2.6.x keys (I had to import=
 my 2.6.3a=20
>  AGCT> and 2.6.3ia keys into GnuPG, and had the same problem. Try the imp=
ort again,=20
>  AGCT> and pass the --allow-non-selfsigned-uid option to gpg, and you sho=
uld be okay.
>=20
> We should really be starting a FAQ. I had the same problem and thought
> this to be an unsolvable compatibility issue. Thanks.

        Smeg. I just remembered something, too. For this, you may need to h=
ave=20
the rsa and idea extensions loaded into GnuPG. There's a nice kludge about=
=20
this, and support for PGP 2.x keys with GnuPG, as part of the GnuPG=20
Documentation Project. 'ave a look at=20
http://www.gnupg.org/gph/en/pgp2x/t1.html . that should clear it up. :)

                                                        BL.
--=20
Brad Littlejohn                         | Email:        tyketto@wizard.com
Unix Systems Administrator,             |           tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! :)   |   http://www.wizard.com/~tyketto
  PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569  F620 C819 199A E319 F0BF


--nFreZHaLTZJo0R7j
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE44IPWyBkZmuMZ8L8RAmj7AJwNsZ7Ce8eNjc2mbGXtfUtFJXDBcQCeOVd4
54P2URDIy3uwm1g3eZcWJ5A=
=+Upm
-----END PGP SIGNATURE-----

--nFreZHaLTZJo0R7j--