>Message: 3 >Date: Sat, 27 May 2006 15:02:45 +0200 (MET DST) >From: Johan Wevers <[EMAIL PROTECTED]> >Subject: Re: 1.4.3 problem with decrypting pgp2.6.3 symmetrically > encrypted
>[EMAIL PROTECTED] wrote: > >>symmetrically encrypted message when the cipher algo is set to >>anything else besides IDEA in Disastry's version, >>and 1.4.3 also cannot, and 'assumes' IDEA is used, and upon >>decryption, > >I'll try to test this. You'll have to explicitly state the >encryption algo >used since the pgp 2 file format doesn't specify it anywhere (and >assumes >just IDEA). > >>here is the symmetrically encrypted file using IDEA: > >I have no problems decrypting it with gpg (self compiled version >on Linux). ok, Thanks! this is very helpful, then the problem is not gnupg, only me ;-) (much easier for me to try to debug my setup ;-) ) >Perhaps the Cygwin version is the problem? no, tested on cygwin, and also from gnupg mingw32 pre-compiled binary at the windows command prompt results identical, but *did* find, and workaround the problem the problem was that my gpg.conf had these options: cipher-algo twofish digest-algo SHA256 s2k-cipher-algo twofish s2k-digest-algo SHA256 ( i put them in because i didn't want new keys to be self-signed with sha-1, and because i prefer twofish) once these were # commented out, the file decrypted perfectly with the following gnupg command: gpg --pgp2 --decrypt filename *but* when Disastry's build is configured intentionally to used twofish and sha-256 then there is nothing i can tweak in gnupg to get it to decrypt ;-(( here is the file: -----BEGIN PGP MESSAGE----- Version: 2.6.3ia-multi06 comment: (symmetric encryption, twofish) (passphrase: s) pgAAACf8AkWW05d5cxJZMREI8uZxtVsHq07rSnCLLYaRYGTBXAi6bw8HJSo= =Z5/z -----END PGP MESSAGE----- the pgp command to generate this was: pgp -cat filename -jtju if anyone has any ideas on how to decrypt this in gnupg, please post, Thanks! ( i don't consider this a 'problem' in gnupg, and, fwiw, it doesn't decrypt in pgp 9 either, or even in ckt builds, pgp 2.x users are quite happy to communicate only with other pgp 2.x users and don't really need gnupg to try to cover all possiblities to remain compatible (although it *is* compatible with 'ordinary' (classic) pgp 2.x as long as the above listed option types are not used during decryption attempts,) it is also of some interest ;-) that users of Disastry's version may have found a simple way to communicate symmetrically, so that even if someone 'overhears' the passphrase, they will still be unable to decrypt unless they use Disastry's version, and will more likely think, that they were 'misled' into thinking they had the correct passphrase ... vedaal Concerned about your privacy? Instantly send FREE secure email, no account required http://www.hushmail.com/send?l=480 Get the best prices on SSL certificates from Hushmail https://www.hushssl.com?l=485 _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
