Thu May 16 20:05:01 2002
Not quite what I meant. They can encrypt either text (ASCII) or binary data
(spreadsheets, programs, pictures, etc). However, the output from the
encryption will be binary (unless you use the --armour option).
So, after the file has been encrypted and until the file has been decrypted,
treat it as binary in all file transmissions.
From: Mark Brettin [mailto:email@example.com]
Sent: Thursday, May 16, 2002 10:36 AM
Subject: Re: compatibility issues
So the client should be encrypting binary?
I forgot to mention that we haven't tried any signatures
yet so signing is not (yet) an issue.
Thanks for all the suggestions, I'll check em out and
keep you all posted.
Steve Butler wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> We at First Choice Health have had some interesting times with clients
> using PGP. Usually we've been able to overcome them. Here is what I'd
> suggest you check:
> 1. the preferences on your key do not reference BLOWFISH or TWOFISH
> anywhere in the list.
> 2. the client isn't trying to override and encrypt to IDEA.
> 3. the client (or your internal) file copy (via FTP) did not use
> ASCII. [We had to educate a couple of clients.]
> 4. Is the client using WS_FTP on a Windows box and your FTP server is
> a Linux box? Specifically we have a problem with one client using
> WS_FTP talking to our RedHat 6.2EE ftp server. The client side appears
> to drop random <CR> bytes (not all of them as would be the case if it
> was an ASCII transfer). Any other ftp client at their site appears to
> work flawlessly. But they "like" WS_FTP <<sigh>>.
> - From your description, I would lean toward #3 or #4. The presumes that
> they were able to correctly import your public key are are really
> encrypting to it. Are you able to encrypt a file to your public key
> and then decrypt it?
> - --Steve
> Oracle Administrator
> First Choice Health Network
> - -----Original Message-----
> From: Mark Brettin [mailto:firstname.lastname@example.org]
> Sent: Thursday, May 16, 2002 8:45 AM
> To: email@example.com
> Subject: compatibility issues
> Can any tell me if there is a known compatibility issue with
> PGP v7.0 and GnuPG 1.0.6?
> I'm having problems decrypting a clients message. I am using
> GnuPG 1.0.6 and the client is using PGP 7.0. The client is
> able to decrypt my messages. The error I get when trying
> to decrypt the 7.0 message is as follows:
> gpg: decryption failed: bad key
> Any ideas?
> Thank you in advance.
> Gnupg-users mailing list
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6-2 (MingW32) - WinPT 0.5.12
> -----END PGP SIGNATURE-----
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies
of the original message.
Custom Programming Group
954-426-2445 ext 195
Gnupg-users mailing list
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.