starred/sharpcompress
1
0
Fork 0
mirror of https://github.com/adamhathcock/sharpcompress.git synced 2026-02-03 21:23:38 +00:00
Code Issues 975 Packages Projects Releases 20 Wiki Activity

Extra bytes written when set to zip64 #420

New Issue
Closed
opened 2026-01-29 22:11:39 +00:00 by claunia · 3 comments
claunia commented 2026-01-29 22:11:39 +00:00
Owner
Copy Link

Originally created by @brecollog on GitHub (Oct 13, 2020).

I have seen various flavors of this issue, some event claim this issue is fixed but I have downloaded the most recent version of sharpcompress and the issue is still there. When writing out a large file, i.e. >2GB, and using the zip64 flag set to true, extra bytes get written in the header that cause issues when decompression. Very repeatable. Create a single file entry > 2GB and add it to the archive and save. If you have 7zip you can right click on the archive and select 'test archive' and you will get the error.

Does anyone have a fix as to how to combat this issue? My apologies if I have missed how this has been addressed.

Originally created by @brecollog on GitHub (Oct 13, 2020). I have seen various flavors of this issue, some event claim this issue is fixed but I have downloaded the most recent version of sharpcompress and the issue is still there. When writing out a large file, i.e. >2GB, and using the zip64 flag set to true, extra bytes get written in the header that cause issues when decompression. Very repeatable. Create a single file entry > 2GB and add it to the archive and save. If you have 7zip you can right click on the archive and select 'test archive' and you will get the error. Does anyone have a fix as to how to combat this issue? My apologies if I have missed how this has been addressed.
claunia added the bugup for grabs labels 2026-01-29 22:11:39 +00:00
claunia commented 2026-01-29 22:11:40 +00:00
Author
Owner
Copy Link

@adamhathcock commented on GitHub (Oct 19, 2020):

As far as I can remember, I don't know if there's been anything specific done to fix this.

The error is extra bytes in the header? Can you give text or screen shots for details?

@adamhathcock commented on GitHub (Oct 19, 2020): As far as I can remember, I don't know if there's been anything specific done to fix this. The error is extra bytes in the header? Can you give text or screen shots for details?
claunia commented 2026-01-29 22:11:41 +00:00
Author
Owner
Copy Link

@brecollog commented on GitHub (Oct 19, 2020):

Using this code after adding SharpCompress:

using System;
using SharpCompress.Common;
using SharpCompress.Writers;
using System.IO;
namespace SharpCompressConsoleTest
{
class Program
{
static void Main(string[] args)
{
string filename = Path.Combine(@"c:\temp", Guid.NewGuid().ToString() + ".zip");
using (FileStream fs = new FileStream(filename, FileMode.Create, FileAccess.Write))
{
var options = new SharpCompress.Writers.Zip.ZipWriterOptions(CompressionType.Deflate)
{
UseZip64 = true
};

            using (var writer = WriterFactory.Open(fs, ArchiveType.Zip, options))
            {
                //dummy.txt is 4GB text file.  it doesn't have to be > 4GB.
                //this can be a 1kb file.  Simply selecting UseZip64 creates a header error
                writer.Write(@"c:\temp\abc.txt", new FileInfo(@"c:\temp\abc.txt"));
            }
        }
    }
}

}
This is simply creating a zip file with the UseZip64 flag set, which you must do when creating files >4GB or sharpcompress will generate an error "System.NotSupportedException: 'Attempted to write a stream that is larger than 4GiB without setting the zip64 option'

This code above will create a zip file but will generate a header error. If you have 7z installed you can right click the file and select 7 Zip/Test Archive and see that it has the header error.

@brecollog commented on GitHub (Oct 19, 2020): Using this code after adding SharpCompress: using System; using SharpCompress.Common; using SharpCompress.Writers; using System.IO; namespace SharpCompressConsoleTest { class Program { static void Main(string[] args) { string filename = Path.Combine(@"c:\temp", Guid.NewGuid().ToString() + ".zip"); using (FileStream fs = new FileStream(filename, FileMode.Create, FileAccess.Write)) { var options = new SharpCompress.Writers.Zip.ZipWriterOptions(CompressionType.Deflate) { UseZip64 = true }; using (var writer = WriterFactory.Open(fs, ArchiveType.Zip, options)) { //dummy.txt is 4GB text file. it doesn't have to be > 4GB. //this can be a 1kb file. Simply selecting UseZip64 creates a header error writer.Write(@"c:\temp\abc.txt", new FileInfo(@"c:\temp\abc.txt")); } } } } } This is simply creating a zip file with the UseZip64 flag set, which you must do when creating files >4GB or sharpcompress will generate an error "System.NotSupportedException: 'Attempted to write a stream that is larger than 4GiB without setting the zip64 option' This code above will create a zip file but will generate a header error. If you have 7z installed you can right click the file and select 7 Zip/Test Archive and see that it has the header error.
claunia commented 2026-01-29 22:11:41 +00:00
Author
Owner
Copy Link

@adamhathcock commented on GitHub (Feb 14, 2021):

Released https://github.com/adamhathcock/sharpcompress/releases/tag/0.28

@adamhathcock commented on GitHub (Feb 14, 2021): Released https://github.com/adamhathcock/sharpcompress/releases/tag/0.28
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
duplicate
enhancement
feedback requested
not bug
pull-request
Mirrored from GitHub Pull Request
 question
up for grabs
wontfix
No Label bug up for grabs
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/sharpcompress#420
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?