PGP 7.0.3 gpg 1.0.4

[Karol Pietrzak]

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

i feel your pain :)  i gave up on PGP 7.0.3 when it refused to import
one of my two secret keys.  i've had hell even with previous versions
of pgp: similar situation, gpg would work perfectly with pgp; not
vice-versa.
here's my options file:
force-v3-sigs # need this; even version 7.0.3 doesn't support v4 sigs
escape-from-lines    # recommended
utf8-strings    # recommended
compress-algo 1  # uses zlib compression, which was (is?) used by pgp;
haven't tried RFC1950 compression with pgp 7.0.3
cipher-algo RIJNDAEL256        # as previously stated, i'm a big
advocate of standards; chosen as AES by the NSA; used CAST5 before.
s2k-cipher-algo RIJNDAEL256

the error message you receive i also received if i used the BLOWFISH,
the gpg default (?)l since pgp doesn't support it, all my encrypted
files would NOT decrypt with pgp (i got the same exact error message
as you do now).  fixed by using CAST5 instead.
two in short, two suggestions:
1. use compression type 1
2. switch to CAST5 / AES


Giorgos Pallas wrote:

> I Cant get them work together. The files encrypted with PGP are
handled
> correctly by gpg but the files encrypted with gpg are not handled
correctly
> be PGP. I get a message : an error has occured : bad packet.
> 
> I use in options :
> cipher-algo TWOFISH
> #force-v3-sigs
> 
> What about compression? Should i de-activate it?
> And what is the "best" from the available algos??
> 
> Thanks for your time

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4-1 (MingW32) - GnuPGshell v1.20
Comment: http://www.gnupg.org

iD8DBQE6gfkPsrWxGyu+UFcRAgFIAKClHwpBiPrJyMt6HVPE7oH2ApWHBQCfTOlN
vn0iIV22raTHFxHUTVg8R8Y=
=cK2w
-----END PGP SIGNATURE-----

--
noodlez:   Karol Pietrzak
GPG/PGP-KeyID: 0x2BBE5057