PGP 8.1 message
scc4fun at spamcop.net
Thu May 26 22:28:19 CEST 2005
Perhaps the problem is that the sender is enclosing the public key block in an
inline signed portion of the email. When that happens the sending system will
modify the headers of the block by adding a hyphen and space "- " before the
other dashes. e.g.:
- -----BEGIN PGP PUBLIC KEY BLOCK-----
Comment: Key stored at www.biglumber.com
- -----END PGP PUBLIC KEY BLOCK-----
It does this so as not to confuse the receiving system when trying to check the
I'm sure others here can tell you how to get around this depending on what mail
program you use.
"We must become the change we seek." -- Mohatma Ghandi
> ----- Message from sohailm01 at gmail.com ---------
> Date: Thu, 26 May 2005 13:31:48 -0400
> From: Sohail Mamdani <sohailm01 at gmail.com>
> Reply-To: Sohail Mamdani <sohailm01 at gmail.com>
> Subject: PGP 8.1 message
> To: General discussion and help forum for GnuPG <gnupg-users at gnupg.org>
> I am having some problems with messages and keys created/encrypted
> using PGP 8.1. I was, for example, sent a public key block exported
> from PGP 8.1 and gnupg refused to import that key into my keyring,
> giving me the message "gpg: no valid OpenPGP data found". I had to
> install PGP 9.0, import the keys into that, export them from PGP 9.0
> and then was able to import it into gnupg.
> Similarly, for the message sent by the same user, I got an error
> saying "gpg: no valid OpenPGP data found.gpg: decrypt_message failed:
> eof" when I tried to decrypt a text file he had sent to me containt an
> ASCII-armored PGP 8.1 message.
> I'm running GNUPG 1.4.1 on Mac OS X.
> Appreciate the help...
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> ----- End message from sohailm01 at gmail.com -----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: PGP Digital Signature
Url : /pipermail/attachments/20050526/c7fb8ccd/attachment.pgp
More information about the Gnupg-users