squashfs-tools-ng.git/bin/rdsquashfs, branch v1.0.2

Fix rdsquashfs unpack under Windows if a directory exists

2020-08-26T16:23:35+00:00

Behave the same way as the POSIX port and do not treat that as an error. Signed-off-by: David Oberhollenzer

Add a "--stat" option to rdsquashfs

2020-08-11T22:25:34+00:00

This commit adds a --stat option to rdsquashfs that dumps a lot of information about and inode that tunred out to be usefull in debugging. Signed-off-by: David Oberhollenzer

Add flags to functions that might logically be expanded in the future

2020-06-11T13:36:08+00:00

Signed-off-by: David Oberhollenzer

Replace assert with propper error handling in rdsquashfs describe

2020-06-07T15:23:51+00:00

If a SquashFS archive contains file names with '..', '/' or similar nonsense in them, the unpacking code already refuses to process them, but the 'describe' code path simply triggers an assert that might not be there if the binary was compiled with NDEBUG defined. This commit replaces the assert with propper error handling that also reports on why things are failing and adds an additional check in the describe_tree function that tests if the file name is sane. Reported-by: Zachary Dremann Signed-off-by: David Oberhollenzer

Cleanup: Reorganize structure of Automake files

2020-05-30T15:49:40+00:00

- Split up the huge file in bin/ into one small file per sub directory - Remove the stub in doc/ Signed-off-by: David Oberhollenzer

Cleanup: move man pages to the respective program source directories

2020-05-30T15:49:40+00:00

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

Cleanup directory structure of the binary programs

2020-04-27T09:59:02+00:00

Instead of having the binary programs in randomly named subdirectories, move all of them to a "bin" subdirectory, similar to the utility libraries that have subdirectories within "lib" and give the subdirectories the propper names (e.g. have gensquashfs source in a directory *actually* named "gensquashfs"). Signed-off-by: David Oberhollenzer