Page MenuHome GnuPG

Cannot decrypt file - encrypts ok [Don't know]:
Closed, ResolvedPublic

Description

see attached. found some similar, but no resolutions.

Below events are latest to earliest. One thing I did notice is that when
manually decrypting using pgp, it created 3 files. 1 2g and 2 4gb exactly.

Rec counts were
1569956
2781746
2781747
Respectively
It may be 46 and 46 or 47 and 47.

I took the file and put all 3 sections together and gpg’d. I tried to ungpg and
got the error. (see below)

I gpg’d the file I created and I have the same problem with I try to un-gpg/pgp

it. This has to be a bug in the gnupg.

By hook or crook, I’ve managed to get a .txt file. It has 7133449 records.

Record size is 1542 + 2 for crlf.

Created originally with:
Version info

 GnuPG - The GNU Privacy Guard
-------------------------------
                 Version 1.4.2

You need a passphrase to unlock the secret key for
user: "MedInitiatives <mtucker@medinitiatives.com>"
2048-bit ELG-E key, ID E7516BF6, created 2002-03-28 (main key ID EDCA68A5)

gpg: encrypted with 2048-bit ELG-E key, ID E7516BF6, created 2002-03-28

"MedInitiatives <mtucker@medinitiatives.com>"

File `x.txt' exists. Overwrite (y/N)? y
gpg: [don't know]: invalid packet (ctb=20)
gpg: [don't know]: invalid packet (ctb=20)
gpg: WARNING: encrypted message has been manipulated!
gpg: [don't know]: invalid packet (ctb=20)
gpg: no valid OpenPGP data found.


CONFIDENTIALITY NOTE: This e-mail, and any attachment to it, may contain
privileged and confidential information intended only for the use of the
individuals or entities named on the e-mail. If you are not the intended
recipient, or the employee or agent responsible for delivering it to the
intended recipient, you are hereby notified that reading it is strictly
prohibited. If you have received this e-mail in error, please immediately
return it to the sender and delete it from your system. Thank you.

Details

Version
1.4.11 (all?)

Event Timeline

mattmer added a subscriber: mattmer.

NOTE file contains data restricted by HIPPA.

Please write a proper error report or ask for advise on a mailing list.
Do not upload files in a proprietary format (doc); we will only look at plain
text bug reports. see http://bugs.gnupg.org

gpg: WARNING: encrypted message has been manipulated!

Clearly indicates the message has been manipulated or corrupted during transport.

Without a real example file, I don't think that the problem can be
reproduced. Thus I'm closing this issue because of the lack of activity
for more than 12 months.

Matter: Thanks for the report! As Werner suggested: Please ask on the
mailinglist if you continue to have problems, until we can somehow produce a
test case and then somebody is able to file a new report.

bernhard claimed this task.