GnuPG 0.9.2

dwpalmer at dwpalmer at
Wed Feb 10 14:27:43 CET 1999

Ouch!  This is even worse.  PGP 5.5 crashes on decrypting the GnuPG
generated file.  Silly thing followed a NULL pointer to the land of
pure madness.  GnuPG, however, is quite happy with the file.

Unfortunately, I still require compatibility with PGP (sigh).  I'd
rather avoid hacking GnuPG to work around what appears to be a PGP
bug.  I'll try a few ways of doing conventional encryption.

Variables to try:

1. Cipher:     --cipher-algo [3des|cast5]
2. Hash:       --digest-algo [md5|sha1|ripemd160])
3. Passphrase: --s2k-mode [0|1|3]

That gives me 2*3*3 = 18 tests.  I'll let you know how it goes.  Any
suggestions on what else I could try?

BTW, the changes in the command line make the two look more alike:

dwpalm:dwpalmer$ gpg --list-packets xxx.gpg 
gpg (GnuPG) 0.9.1; Copyright (C) 1999 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.

gpg: Warning: using insecure memory!
:symkey enc packet: version 4, cipher 3, s2k 0, hash 1
:encrypted data packet:
        length: unknown
gpg: decryption failed: bad key

PS: Why the "decryption failed: bad key" message?  I'm using the right


> Date:    Wed, 10 Feb 1999 19:16:07 +0100
> From:    Werner Koch <wk at>

> Try this line:
> $ gpg -c --s2k-mode 0 --digest-algo md5 -o xxx --cipher-algo cast5 
> and you should see the same as PGP 5.5 produces:
> :symkey enc packet: version 4, cipher 3, s2k 0, hash 1
> Please tell me whether this works.
>    Werner
> -- 
> ceterum censeo RSA esse delendam

More information about the Gnupg-devel mailing list