Differing File Sizes & GPG Symmetric Decryption Failure After ~4G

Packard, Matthew Matthew.Packard@Umassmed.edu
Tue Jul 1 22:47:02 2003


--------------040905040401030308090106
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Everyone,

    I just ran into a very odd issue with GPG 1.2.1. I had previously 
created a ~10G tar file, GPG'd it using a symmetric passphrase, (gpg -c 
file.tar) and I ended up with a ~8G compressed GPG file. Immediately 
after I created the GPG file, I decrypted it (gpg -d file.tar.gpg > 
file.tar) and let it run for a few seconds - just to make sure that I 
could at least decrypt it (quick test). I got a partial tar file and I 
thought everything was OK. Well, I went to decrypt the entire GPG file 
today as I had more stuff to add to the tar file. When the tar file got 
to 4,033,946,112 bytes (~3.75G) in size, the GPG decryption stopped, and 
I received the following error message:

        gpg: [don't know]: invalid packet (ctb=1b)
        :unknown packet: type 59, length 57
        dump: 3e 88 e4 ad f0 fd f8 18  04 3d 3e 57 3d 9f d7 7b  14 3e 1f 
5f 88 b0 db bd
          24: 48 1e 82 57 c7 57 23 c2  41 f2 0e f1 f6 8f e2 df  05 7a 7c 
fb a8 3f 17 0d
          48: de 1f 3f 4f 7c 46 e5 0f  4f
        gpg: onepass_sig with unknown version 234
        gpg: decryption okay

    So, I went back and performed a packet-list on the GPG file and 
received the following information:

            :symkey enc packet: version 4, cipher 3, s2k 3, hash 2
                salt 50cddd890017df06, count 96

            gpg: CAST5 encrypted data
            :encrypted data packet:
                length: unknown
            :compressed packet: algo=1
            :literal data packet:
                mode b, created 1055599766, name="Software.tar",
                raw data: 4033946112 bytes
            gpg: original file name='Software.tar'

    But the file on disk is 8195780694 bytes. Has anyone else run into 
this issue? I'm running GPG on a SPARC, Solaris 9 (original revision), 
and large file support appears to be available to GPG. If anyone has any 
ideas, I'd greatly appreciate some advice. BTW, I found no reference to 
the keywords above in the archives, so if you do happen to find a 
previously submitted question (with answer), please let me know as well.

Thanks in advance,
Matthew Packard
matthew.packard@umassmed.edu

--------------040905040401030308090106
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000" link="#0000ee" alink="#0000ee"
 vlink="#551a8b">
Everyone,<br>
<br>
&nbsp;&nbsp;&nbsp; I just ran into a very odd issue with GPG 1.2.1. I had previously created
a ~10G tar file, GPG'd it using a symmetric passphrase, (gpg -c file.tar)
and I ended up with a ~8G compressed GPG file. Immediately after I created
the GPG file, I decrypted it (gpg -d file.tar.gpg &gt; file.tar) and let
it run for a few seconds - just to make sure that I could at least decrypt
it (quick test). I got a partial tar file and I thought everything was OK.
Well, I went to decrypt the entire GPG file today as I had more stuff to
add to the tar file. When the tar file got to 4,033,946,112 bytes (~3.75G)
in size, the GPG decryption stopped, and I received the following error message:<br>
<br>
<tt>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; gpg: [don't know]: invalid packet (ctb=1b)<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; :unknown packet: type 59, length 57<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; dump: 3e 88 e4 ad f0 fd f8 18&nbsp; 04 3d 3e 57 3d 9f d7 7b&nbsp; 14 3e 1f
5f 88 b0 db bd<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; 24: 48 1e 82 57 c7 57 23 c2&nbsp; 41 f2 0e f1 f6 8f e2 df&nbsp; 05 7a 7c
fb a8 3f 17 0d<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; 48: de 1f 3f 4f 7c 46 e5 0f&nbsp; 4f<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; gpg: onepass_sig with unknown version 234<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; gpg: decryption okay<br>
</tt><br>
&nbsp;&nbsp;&nbsp; So, I went back and performed a packet-list on the GPG file and received
the following information:<br>
<br>
<tt>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; :symkey enc packet: version 4, cipher 3, s2k 3, hash 2<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; salt 50cddd890017df06, count 96<br>
<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; gpg: CAST5 encrypted data<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; :encrypted data packet:<br>
&nbsp; &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp; length: unknown<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; :compressed packet: algo=1<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; :literal data packet:<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mode b, created 1055599766, name="Software.tar",<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; raw data: <b><font color="#000000">4033946112</font></b>
bytes<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; gpg: original file name='Software.tar'</tt><br>
<br>
&nbsp;&nbsp;&nbsp; But the file on disk is <b>8195780694</b> bytes. Has anyone else run
into this issue? I'm running GPG on a SPARC, Solaris 9 (original revision),
and large file support appears to be available to GPG. If anyone has any
ideas, I'd greatly appreciate some advice. BTW, I found no reference to the
keywords above in the archives, so if you do happen to find a previously
submitted question (with answer), please let me know as well.<br>
<br>
Thanks in advance,<br>
Matthew Packard<br>
<a class="moz-txt-link-abbreviated" href="mailto:matthew.packard@umassmed.edu">matthew.packard@umassmed.edu</a><br>
</body>
</html>

--------------040905040401030308090106--