Mailing List Archive

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

On Sat, 6 May 2000, Micah Anderson wrote:

> Date: Sat, 6 May 2000 17:45:30 -0700 (PDT)
> From: Micah Anderson <micah@riseup.net>
> To: gnupg-users@gnupg.org
> Subject: importing other keys
> Resent-Date: Sun, 7 May 2000 02:42:12 +0200
> Resent-From: gnupg-users@gnupg.org
>
>
> Hello.... I asked someone for their pgp key and they gave me a web page
> which has two different keys on it. I tried both of them and gpg would not
> import either. Here are the headers from the keys:
>
> First key:
>
> -----BEGIN PGP PUBLIC KEY BLOCK-----
> Version: PGPfreeware 5.5.3i for non-commercial use <http://www.pgpi.com>
>
> Second key:
>
> -----BEGIN PGP PUBLIC KEY BLOCK-----
> Version: 2.6.2
>
> Is there a way to make one of these work, or is this guy going to have to
> make a gpg key too? It seems sort of rediculous that you should have to
> make different keys for different implementations. PGP is hard enough for
> the average person to use without standardization.
>
> I am not on this mailing list, so please send me replies
> directly: micah@riseup.net
>
> Thanks!
> Micah
>
>

hahah.. You're wreaking havoc with my pgp4pine..

- --
"The Funk, the whole Funk, and nothing but the Funk."
Billy Donahue <mailto: billy@dadadada.net>
http://dadadada.net
GnuPG Key ID: 0219745D Billy Donahue <billy@dadadada.net>
Fingerprint: 869A 2453 36F4 09BA 1D83 1839 FB65 6FA7 0219 745D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Made with pgp4pine 1.75

iD8DBQE5FMI9+2VvpwIZdF0RAgpOAJ4naaSmqvXJcN03M4VSDaib3fyaoACbBUrn
8mQqVcLsq+4u/MKEhWNLKdg=
=1OnA
-----END PGP SIGNATURE-----

Huh?


On Sat, 6 May 2000, Billy Donahue wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sat, 6 May 2000, Micah Anderson wrote:
>
> > Date: Sat, 6 May 2000 17:45:30 -0700 (PDT)
> > From: Micah Anderson <micah@riseup.net>
> > To: gnupg-users@gnupg.org
> > Subject: importing other keys
> > Resent-Date: Sun, 7 May 2000 02:42:12 +0200
> > Resent-From: gnupg-users@gnupg.org
> >
> >
> > Hello.... I asked someone for their pgp key and they gave me a web page
> > which has two different keys on it. I tried both of them and gpg would not
> > import either. Here are the headers from the keys:
> >
> > First key:
> >
> > -----BEGIN PGP PUBLIC KEY BLOCK-----
> > Version: PGPfreeware 5.5.3i for non-commercial use <http://www.pgpi.com>
> >
> > Second key:
> >
> > -----BEGIN PGP PUBLIC KEY BLOCK-----
> > Version: 2.6.2
> >
> > Is there a way to make one of these work, or is this guy going to have to
> > make a gpg key too? It seems sort of rediculous that you should have to
> > make different keys for different implementations. PGP is hard enough for
> > the average person to use without standardization.
> >
> > I am not on this mailing list, so please send me replies
> > directly: micah@riseup.net
> >
> > Thanks!
> > Micah
> >
> >
>
> hahah.. You're wreaking havoc with my pgp4pine..
>
> - --
> "The Funk, the whole Funk, and nothing but the Funk."
> Billy Donahue <mailto: billy@dadadada.net>
> http://dadadada.net
> GnuPG Key ID: 0219745D Billy Donahue <billy@dadadada.net>
> Fingerprint: 869A 2453 36F4 09BA 1D83 1839 FB65 6FA7 0219 745D
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.1 (GNU/Linux)
> Comment: Made with pgp4pine 1.75
>
> iD8DBQE5FMI9+2VvpwIZdF0RAgpOAJ4naaSmqvXJcN03M4VSDaib3fyaoACbBUrn
> 8mQqVcLsq+4u/MKEhWNLKdg=
> =1OnA
> -----END PGP SIGNATURE-----
>
>
>
>

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

On Mon, 8 May 2000, Micah Anderson wrote:
> On Sat, 6 May 2000, Billy Donahue wrote:
>
> > On Sat, 6 May 2000, Micah Anderson wrote:
> >
> > > First key:
> > >
> > > -----BEGIN PGP PUBLIC KEY BLOCK-----
> > > Version: PGPfreeware 5.5.3i for non-commercial use <http://www.pgpi.com>
> > >
> > > Second key:
> > >
> > > -----BEGIN PGP PUBLIC KEY BLOCK-----
> > > Version: 2.6.2
> > >
> > > Is there a way to make one of these work, or is this guy going to have to
> > > Thanks!
> > > Micah
> >
> > hahah.. You're wreaking havoc with my pgp4pine..
>
> Huh?
>

The -----BEGIN blocks with no -----END block confused it.
It tried to import the keys, but there weren't any.
It didn't crash or anything...

- --
"The Funk, the whole Funk, and nothing but the Funk."
Billy Donahue <mailto:billy@dadadada.net>
http://dadadada.net
GnuPG Key ID: 0219745D Billy Donahue <billy@dadadada.net>
Fingerprint: 869A 2453 36F4 09BA 1D83 1839 FB65 6FA7 0219 745D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Made with pgp4pine 1.75

iD8DBQE5Fvl7+2VvpwIZdF0RAi1JAKCVlurQiq0xSUTypjLso0hUNhgStgCdECDB
u1snx++R8Hmn4r7D0ODkLH4=
=7eMU
-----END PGP SIGNATURE-----

>>>>> "Micah" == Micah Anderson <micah@riseup.net> writes:

Micah> Hello.... I asked someone for their pgp key and they gave me a web page
Micah> which has two different keys on it. I tried both of them and gpg would not
Micah> import either. Here are the headers from the keys:

I just got it to work, after having failed the same way Micah did.
Here's what I did:

* I visited the web page with Netscape.

* I dragged the mouse over the key blocks, thus copying the keys into
the X select buffer (or whatever it's called)

* I used GNU Emacs to visit a new file, and yanked the keys into the
file's buffer by typing control-Y.

* I saved that file as /tmp/keys, then at the shell, typed `gpg
--import /tmp/keys'. This failed with this message

gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

* Then I had a brainstorm: I deleted the trailing whitespace from the
file by typing, in Emacs,

M-x replace-regexp RET
[ SPC tab ] + $ RET RET

* Then I saved the file, and re-did gpg --import. This time it
worked.

--
PGP Fingerprint: 3E7B A3F3 96CA 8958 ACC5 C8BD 6337 0041 C01C 5276