An Error Has Occurred Encrypted Session Key Is Bad Pgp
Contents |
GnuPG Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Okay, here's your answer. The test keys and message tht William gave me helped a lot. It looks key pad like GnuPG is listing Twofish, then Blowfish, then CAST as preferred algorithms. For some reason, GnuPG
Key Bar
is encrypting to Blowfish, instead of Twofish. (Bug, Werner?) To be decrypted in PGP 6.5.x, the message must use CAST, IDEA, or 3DES as the ESK. To be the most compatable with all implementations of OpenPGP, one should 3DES, as this will be present in all OpenPGP compliant programs. (IDEA and CAST5 are "shoulds", 3DES is a "must".) You are taking a chance with the others, if you plan to move the secret keys to a different program in the future. Note that this incompatability only applies to keys generated in one program, and imported and used in another. You could keep the old key and work around this by adding a new UID with a different preferred algorithm specified, and encrypting to that. - --Len. On Fri, 17 Mar 2000, Chris Ruvolo wrote: > On Thu, 16 Mar 2000, William X. Walsh wrote: > > >>>Well, I don't know about this. I've had a large problem with PGP 6.x not > >>>being > >>>able to decrypt messages encrypted by GnuPG, regardless if they key it is > >>>encrypting to was created in GnuPG or PGP. > >> > >> So you're saying that GnuPG and PGP are *not* compatible and people > >> using one may not be able to successfully exchange encrypted > >> documents with users of the other? > > > >The problem is persistant, and anytime I encrypt a message using GnuPG, users > >of PGP 6.5.x (for windows at least) cannot decrypt the message. It gives an > >error. I've reported this a few times in the past over the last few months. > > > >This is not an intermittent problem. > > > I can confirm this problem. I was one of the people that emailed William. > I tested it with GPG 1.0.1 and PGP Freeware for Windows 6.5.2. Perhaps > there is some kind of option I am missing or something? > > I have the following settings in my options file: > > no-greeting > force-v3-sigs > escape-from-lines > lock-once > load-extension rsa > load-extension idea > rfc1991 > keyserver wwwkeys.us.pgp.net > > Any suggestions? Thanks. > > -Chris > __ L. Sassaman System Administrator | "All of the chaos Technology Consultant | Makes perfect sense..." icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Joe Diffie -----BEGIN
Post #1 of 3 (1014 views) Permalink Problems with PGP user decrypting GPG files Hi everyone, We are in the process of testing our encryption / decrytion with some trading partners that are using PGP 7.0.1 on windows 2000 advanced server. We are using gpg 1.0.6 on tru64 unix v5.1 on a DS10. I have imported into GPG their public keys, and our private/public pair that were exported from PGP 6.5.8 https://lists.gnupg.org/pipermail/gnupg-users/2000-March/005167.html on a PC. I encrypt files by using the following shell script: #!/bin/ksh # # Program Name: /usr/bin/encryptgpguser # # Author: Mike Kirkland # Date: 11-28-01 # # Purpose: This script will encrypt files past to it from server lyra # after encryption lyra will ftp files from this directory to be sent to payer # This http://www.gossamer-threads.com/lists/gnupg/users/7690 script will be rexec from lyra with 2 parameters passed to it # # 1 the filename to be encrypted # 2 the payer's public key identifier to be used for encryption # # Modifications: N/A cd /gpguser USAGE="Usage: `basename $0`
difference in the problem I'm about todescribe)I've been using his public key (Diffie-Hellman) to send him encryptedmessages. Some messages have been sent, where the session key used wasAES256. Some messages, the session key has been 3DES. http://alt.security.pgp.narkive.com/f8c6nbMV/can-t-decrypt-aes256-pgp-ckt All of themessages have been encrypted to both my default key, and his publickeyWhen he receives a message from me where the session key was encryptedusing AES256, he gets the following message after entering hispassword:"An Error Has Occurred: Encrypted Session Key Is Bad"When he receives a message from me where the session key was encryptedusing 3DES, the message decrypts just fine.I've asked him to make sure that in an error his PGP Options (Advanced tab), hehas all of the available algorithms listed. Of course, he's using ckt,so he has available all the same algorithms that I have available onmy machine. I don't understand why using 3DES works for him, whenAES256 doesn't.All of the messages he's sent me have used 3DES on the session key,and I've been decrypting them fine.I have not yet tested any other algorithms with him an error has yet, as I knowthat he's busy and I don't want to bother him with more testing if Ican figure out what may be wrong from anyone in this group first.Thanks,Johnny Casey Klc 2005-08-07 17:27:44 UTC PermalinkRaw Message Post by Johnny KapikkiWe are both using PGP 6.5.8cktHe's using version 08I'm using version 09b3(this *shouldn't* make a difference in the problem I'm about todescribe)I've been using his public key (Diffie-Hellman) to send him encryptedmessages. Some messages have been sent, where the session key used wasAES256. Some messages, the session key has been 3DES. All of themessages have been encrypted to both my default key, and his publickeyWhen he receives a message from me where the session key was encryptedusing AES256, he gets the following message after entering his"An Error Has Occurred: Encrypted Session Key Is Bad"When he receives a message from me where the session key was encryptedusing 3DES, the message decrypts just fine.I've asked him to make sure that in his PGP Options (Advanced tab), hehas all of the available algorithms listed. Of course, he's using ckt,so he has available all the same algorithms that I have available onmy machine. I don't understand why using 3DES works for him, whenAES256 doesn't.All of the