| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-09-03 | Fix integer bounds checking in GNU tar sparse format 1.0 parser | David Oberhollenzer | |
| - Make sure the file actually has that many records before trying to read one and fail if not. - Use the helper macros for size_t overflow checking instead of assuming size_t == uint64_t. - Impose a "reasonable" upper bound on the number of data segments and insist that there is at least one entry. Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at> | |||
| 2020-09-02 | Fix nonexistant gnu tar sparse format 1.0 support | David Oberhollenzer | |
| Contrary to previous claims, support for the GNU tar sparse format 1.0 was missing entirely (the newest of their 3 different sparse mapping formats). This oversight wasn't caught, because the unit test was compiling the wrong source file and tar2sqfs had no problem processing the test file because it is still a valid POSIX-ish tar archive (but the sparse part was missing and the mapping embedded in the file). Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at> | |||
 |
index : squashfs-tools-ng.git | |
| A new set of tools and libraries for working with SquashFS images | David Oberhollenzer |
| summaryrefslogtreecommitdiff |