Bug #9529

TarHeader (Gem::Package) doesn't parse size correctly for +8GB entries

Added by eranhirsch (Eran Hirsch) almost 6 years ago. Updated 5 months ago.

Third Party's Issue
Target version:
ruby -v:
ruby 1.9.3p448 (2013-06-27 revision 41675) [x86_64-darwin13.0.0]


  • The current TAR header parsing code assumes the size is represented as an octal string
  • Because this is a 12-byte, null-terminated field, effectively this can represent up to 8GB (811).
  • For bigger files the standard allows to define the field as a 12-byte INTEGER instead.
  • When using this form, the first bit of the field should be turned on to signal that it is used.

Currently, TAR files containing files larger then 8GB in this format would fail parsing because size would be computed as 0.

(Wiki with some description of the logic, couldn't find a more "formal" document:

The problem is with this code:

The line that assigns the value to size should be conditioned on the value of the first bit, and should treat the two cases differently


Updated by luislavena (Luis Lavena) almost 6 years ago

  • Status changed from Open to Assigned
  • Assignee set to drbrain (Eric Hodel)

Updated by ruby_learner (Jay Mav) 6 months ago

Is there plan to fix this issue? Need this Windows because there is no native support for extracting tar contents. Is there any workaround for is there any other rubygem which can extract archived_file >= 8gb?

Updated by hsbt (Hiroshi SHIBATA) 5 months ago

  • Backport deleted (1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN)
  • Assignee changed from drbrain (Eric Hodel) to hsbt (Hiroshi SHIBATA)
  • Status changed from Assigned to Third Party's Issue

I'm not sure what usecase of this issue.

Can you file the details into the upstream repository?


Also available in: Atom PDF