squashfs-tools-ng.git, branch v0.9.1

Actually run the directory pack test if corpora tests are desired

2020-05-03T18:35:20+00:00

Signed-off-by: David Oberhollenzer

Bump version number

2020-05-03T18:35:20+00:00

Signed-off-by: David Oberhollenzer

Update README.md

2020-05-03T18:35:20+00:00

Signed-off-by: David Oberhollenzer

Update CHANGELOG.md

2020-05-03T18:35:20+00:00

Signed-off-by: David Oberhollenzer

Update man pages

2020-05-03T16:51:59+00:00

Add missing options, rephrase some things to be a bit more clear and fix a bunch of typos. Signed-off-by: David Oberhollenzer

Add a simple test script for the gensquashfs packdir + allroot use case

2020-05-03T12:36:16+00:00

Since this is a fairly common use case, it deserves a simple test case to check out that e.g. option processing hasn't been botched up (again). As input directory, the licenses directory is used as it contains no intermediate build output and should change fairly infrequently. The test is enabled irregardless of the corpora-test option. Signed-off-by: David Oberhollenzer

Fix: unify extra argument rejection in tar2sqfs & gensquashfs

2020-05-03T12:00:55+00:00

Signed-off-by: David Oberhollenzer

Fix: the --all-root option does not take an arugment

2020-05-03T11:58:38+00:00

Change the "required_argument" to the correct "no_argument". Signed-off-by: David Oberhollenzer

Fix: use 0644 as default permissions when creating files

2020-05-02T23:43:11+00:00

Until now, when packing or unpacking a SquashFS image, files where created with paranoid permissions (i.e. 0600). The rational behind this was that otherwise, the tools may inadvertently expose secrets, e.g. if a root user packs files that that aren't world readable, such as the /etc/shadows file, but the packed SquashFS image is, we have accidentally leaked this file to other users that can access the newly created SquashFS image. The same line of reasoning also applies when unpacking files. Unfortunately, this breaks a list of other, more common standard use cases (e.g. a build server where the an image is built by a deamon running as user X but then has to be accessed by another deamon running as Y). This commit changes to a more standard approach of using permissive file permissions by default and asking paranoid users to simply use a paranoid umask. For tar2sqfs & gensquashfs this simply means chaning the default permissions in the libsquashfs file implementation. For rdsquashfs on the other hand there is still the use case where the unpacked files get the permissions from the [secret] image, so setting a strict umask is not applicable and changing to permissive file mode leaks something. For this case a second code path needs to be added that derives the permissions from the ones in the image. Signed-off-by: David Oberhollenzer

Fix gitignore binary paths

2020-04-27T18:43:26+00:00

Only ignre them if they are in the top most directory, i.e. built in the source tree. Do not ignore directories named after the binaries! Signed-off-by: David Oberhollenzer