-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 13 Apr 2000, L. Sassaman wrote:
>Be sure you are using a cipher that both products can understand. 3DES is
>the most logical, since it is required by RFC 2440. CAST is the default
>cipher in PGP, and Blowfish in GnuPG. PGP does not implement Blowfish, so
>this is most likely your problem.
So, why does GPG default to something that pgp cant handle?
/johan
__________________________________________________
MAIL:p99jlu@physto.se Johan Lundberg
HTTP://www.physto.se/~p99jlu 17764 Jarfalla
+46(0)8-580 17259 PGP: 0xD3A0A0E5 Vibblabyv. 28
B847 687B 8971 0AAC 1C29 DBA1 AB5F 664F D3A0 A0E5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE49i8Aq19mT9OgoOURAsseAJ4q8wd80u92qcQFrfDMt2RIpQL+OgCfazeq
VJyopdHquN+rLjY9osLdK/0=
=Elz7
-----END PGP SIGNATURE-----
Hash: SHA1
On Thu, 13 Apr 2000, L. Sassaman wrote:
>Be sure you are using a cipher that both products can understand. 3DES is
>the most logical, since it is required by RFC 2440. CAST is the default
>cipher in PGP, and Blowfish in GnuPG. PGP does not implement Blowfish, so
>this is most likely your problem.
So, why does GPG default to something that pgp cant handle?
/johan
__________________________________________________
MAIL:p99jlu@physto.se Johan Lundberg
HTTP://www.physto.se/~p99jlu 17764 Jarfalla
+46(0)8-580 17259 PGP: 0xD3A0A0E5 Vibblabyv. 28
B847 687B 8971 0AAC 1C29 DBA1 AB5F 664F D3A0 A0E5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE49i8Aq19mT9OgoOURAsseAJ4q8wd80u92qcQFrfDMt2RIpQL+OgCfazeq
VJyopdHquN+rLjY9osLdK/0=
=Elz7
-----END PGP SIGNATURE-----