Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TAR does not have enough EOF blocks #13

Closed
dsoprea opened this issue Aug 22, 2013 · 0 comments
Closed

TAR does not have enough EOF blocks #13

dsoprea opened this issue Aug 22, 2013 · 0 comments
Assignees
Labels
bug tar Related to TAR file format

Comments

@dsoprea
Copy link

dsoprea commented Aug 22, 2013

WriteEofBlock() only writes one empty record to represent EOF. Wikipedia's entry (http://en.wikipedia.org/wiki/Tar_(computing)) states the following:

The end of an archive is marked by at least two consecutive zero-filled records.

As a result, these TARs may experience compatibility problems.

@McNeight McNeight added the bug label Apr 14, 2016
@McNeight McNeight self-assigned this Apr 14, 2016
@McNeight McNeight added tar Related to TAR file format and removed tar Related to TAR file format labels Apr 15, 2016
kungfubozo pushed a commit to explodingbarrel/SharpZipLib that referenced this issue Oct 17, 2018
* icsharpcode/master: (168 commits)
  Update readme with State of the Union August 2017 link + looking for new maintainer
  -alpha2 preview package with latest fixes from @siegfriedpammer
  Remove metrics
  Fix icsharpcode#13 - TAR does not have enough EOF blocks
  [BZip2] Enforce baseStream to be non-null in BZip2InputStream and BZip2OutputStream (constructor now throws an ArgumentNullException).
  fix icsharpcode#11 - BZip2InputStream CanSeek should be false
  Minimal build server is back online (only build & run unit tests)
  For testing purposes, rename appveyor.yml
  Minimal text to direct developers to either generated API documentation, Wiki or other important URLs.
  Help building instructions (intentionally atm not checking in api/*.yml)
  Fix all warnings
  Fix XML comment warnings
  "docfx metadata" currently failing
  docfx init -q
  Switch samples from source reference to Nuget package reference (currently alpha1)
  Remove old SHFB-generated help file (.chm)
  Enable Nuget package generation as well as Xml doc gen
  Zip: Move tests to separate files
  Disable PasswordCheckingWithDateInExtraData test
  Disable ReadingOfLockedDataFiles test
  ...

# Conflicts:
#	.gitignore
#	README.md
#	src/ICSharpCode.SharpZLib.csproj
#	src/ICSharpCode.SharpZipLib/Zip/ZipFile.cs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug tar Related to TAR file format
Projects
None yet
Development

No branches or pull requests

2 participants