In the past, I have had issues with tar files where
the block size
wasn't specified, and the file was a multiple of 512 but not of 10240.
My solution was to pad out to a multiple of 10240.
On 30 April 2012 13:22, Dave Thompson <dthompson@...> wrote:
>> From: owner-openssl-users@... On Behalf Of jb-openssl@...
>> Sent: Thursday, 26 April, 2012 19:37
>> On 26-04-2012 15:05, Thomas J. Hruska wrote:
>> > ... This archive under 7-Zip 9.20 (latest
>> > stable) displays a "There are no trailing zero-filled
>> > error dialog but then proceeds to work just fine. ...
>> This is not limited to 7-Zip, see also the post by Mr. Bergeron
>> of IBM.
> I didn't see that one, but a few more data points:
> Ancient Solaris (5.)8 says "tar: read error: unexpected EOF"
> but has in fact extracted or listed last file (VMS/WISHLIST.TXT)
> okay. Ancient AIX 4.3 goes into an apparently infinite loop on
> the last 8 files (!) but seems to have extracted/listed okay.
> Of the downloads I have at hand (about a year), the others
> with less than 2x512 zero at the end are 0.9.8q and 1.0.0-beta4 .
> 0.9.8q produces same symptoms but 1.0.0-beta4 does not. Blech.
> WinZip 12 is happy. As is gnu tar 1.13.19 1.14 1.15.1.
> I'm not startled by that; gnu programs in general usually
> tolerate slight nonstandardness, and often not-so-slight.
> This may be exchange for the nonstandardness they create.
>> I have looked closer at the tar.gz file (my download matches the
>> checksums and digital signature from Dr. Henson), and the file
>> is not valid according to the tar file format specifications that
>> I have looked at.
>> According to the basic tar specification, each file is prefixed
>> a 512 byte header with filename, size etc. and zero padded to
>> multiple of 512 bytes, and the last file is followed by at least
>> 2x512 bytes of all-zero bytes to indicate end of file. ...
>> But the tar file inside the gzip file "openssl-1.0.1b.tar.gz"
>> lacks those last 1024 bytes of zeroes. ...
User Support Mailing List
Automated List Manager