sasquatch
sasquatch copied to clipboard
devttys0
I am attempting to recover data from a flash chip removed from a proprietary device. I've dumped the chip and stripped out the OOB data. Binwalk finds multiple squashfs partitions....
- Avoid calling gcc or g++ directly, crash the compilation on several hardened systems - Change external verbose variable on error.h, crash the compilation process for redeclaration on several objects...
sasquatch is currently using an old version of squashfs-tools, which contains the bug described here: https://github.com/plougher/squashfs-tools/issues/125 that was fixed in a later version. https://github.com/ReFirmLabs/binwalk depends on this package, and after...
This is a tiny patch that fixes #36 with a code change I understand that it's possible to use `CFLAGS` to make newer versions of `gcc` accept the code "as-is"...
So over the past few days I've had some trouble getting this to build on Kali Linux but have resolved it simply by running `CFLAGS=-fcommon ./build.sh` Rather than `./build.sh` If...
On gcc-10 (and gcc-9 -fno-common) sasquatch build fails as: c++ ./LZMA/lzmalt/*.o unsquashfs.o ... -o sasquatch ld: unsquash-1.o:squashfs-tools/error.h:34: multiple definition of `verbose'; unsquashfs.o:squashfs-tools/error.h:34: first defined here gcc-10 will changed the default...
What version of debian/ubuntu can you build this on? ``` cc -g -O2 -I. -I./LZMA/lzma465/C -I./LZMA/lzmalt -I./LZMA/lzmadaptive/C/7zip/Compress/LZMA_Lib -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -DCOMP_DEFAULT=\"gzip\" -Wall -Werror -DGZIP_SUPPORT -DLZMA_SUPPORT -DXZ_SUPPORT -DLZO_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c...
This was basically done by hand by updating the rejected hunks. Indenting might be messed up (good thing C isn't whitespace-sensitive). Any testing / validation appreciated. --- Closes #33. EDIT:...
Is there any chance to fix the patch so it would be applied to squashfs-tools-4.4 ?
apt-get has been deprecated for years now, after all.
