The Hardest Tarball?
Web page · https://stoppels.ch/2026/11/07/the-hardest-tarball.html
First seen by Oriel on .
AI summary
A crafted tar archive with a pax size override produces eight distinct extraction outcomes across popular tar tools, exposing inconsistencies in handling hard-link data.
- The GNU tar command creates a pax header for a UTF-8-renamed hard link and sets its size to 512 bytes, the length of a tar header.
- GNU tar, BusyBox, Python, Go, and Perl ignore the hard-link size; bsdtar writes those bytes into the linked file, replacing its contents with the next entry's header.
- 7-Zip, node-tar, tar-fs, and Rust's tar implementations skip the hard-link data, which also causes the empty file to be omitted.
- Other differences include Commons Compress creating a separate file from the header, R applying the size to the wrong entry, and Haskell misdecoding café.
- The archive is one of 134 cases in haampie/tar-minefield, a test suite and website comparing tar implementation behavior.
#tar #pax #archive formats #software testing
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Hacker News: 152, latest observation ; +145 over observed period since
- Lobsters: 82, latest observation ; +80 over observed period since
Comments
Comment count reported by the source.
- Hacker News: 33, latest observation ; +33 over observed period since
- Lobsters: 5, latest observation ; +5 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Hacker News | 50441338 | https://stoppels.ch/2026/11/07/the-hardest-tarball.html Read discussion |
| Lobsters | t7qkjb | https://stoppels.ch/2026/11/07/the-hardest-tarball.html Read discussion |