GPG decryption error

[Dutta, Sudip]

Hello,

 

I'd really appreciate if someone can provide feedback with a
decryption-related error we're getting. 

 

For an encrypted file of size approx. 2 - 4 gigs, encrypted by a user
using the same key that is being used for decrypting it, there are
errors, as listed below - however there are no errors on decrypting a
smaller file of size less than 1 gig -

 

sdutt at gl5705rk02
[/work/ew11/IS/Data/CreditArchives/mainframe/gpgtest/test] $ --> gpg
--output r02_allvar_il --decrypt r02_allvar_il.pgp

gpg: WARNING: using insecure memory!

gpg: please see http://www.gnupg.org/faq.html for more information

 

You need a passphrase to unlock the secret key for

user: "sdutt <sdutt at allstate.com>"

2048-bit ELG-E key, ID CAB7C3F4, created 2009-08-11 (main key ID
D36BE972)

 

gpg: encrypted with 2048-bit ELG-E key, ID CAB7C3F4, created 2009-08-11

      "sdutt <sdutt at allstate.com>"

gpg: [don't know]: invalid packet (ctb=41)

gpg: [don't know]: invalid packet (ctb=20)

gpg: mdc_packet with invalid encoding

gpg: decryption failed: invalid packet

gpg: [don't know]: invalid packet (ctb=41)

sdutt at gl5705rk02
[/work/ew11/IS/Data/CreditArchives/mainframe/gpgtest/test] $ -->

________________________________________________________________________
______________________________________

 

 

Not sure if there are restrictions on size of a file that can be
encrypted or decrypted, or if there are separate options that need to be
used for large files.

 

The file encrypted by us with the key of a user, is sent by remote ftp
to that user, who after decrypting it, and a few necessary modifications
to the data in the file, encrypts it using our key, which then is
received by us by remote ftp - this process, with the same keys, works
without any issues for smaller files less than a gig. 

 

We are using the latest version of GPG on a UNIX Solaris server.  

 

Your help on this will be appreciated. 

 

Thanks,

Sudip 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20090910/568d9d8c/attachment-0001.htm>