Jörg Stucke

Not all distributions that we support come with a packaged version of checksec.sh (i.e. Ubuntu 18.04) and we want to avoid separate installations for each distribution when possible (as all...

This sounds more like a path problem of FACT_docker: The extractor runs in its own docker container (to spare the user from having to install all unpackers) and the file...

`/tmp/extractor/input` is not the problem, it exists only inside the extractor container. The problem seems to be the file that is mounted there. It is mounted from inside the FACT...

You are right, it should be configured correctly. I will try to rebuild the container to reproduce the problem.

OK I found the problem: the `start.py` script should mount the config directory in the FACT_docker folder (the repository folder on the host) into the container and you should make...

PR #696 is currently open and should hopefully fix all remaining FACT docker path issues. Also what I wrote was not entirely correct: The path in the config doesn't have...

You could only transfer the complete database to another machine. At the moment, there is no import functionality for analysis results. In theory, you could merge the files and add...

The extractor container needs "privileged mode" to be able to mount file systems (to extract files from those). Maybe there is some way to accomplish this without relying on privileged...

You can find the call to the extractor container in `src/unpacker/unpack_base.py:26` but it uses the Docker Python API. The corresponding option here seems to be `userns_mode`. Replacing `privileged=True` with `userns_mode='host'`...

So the way I understand it now, we could set `userns_mode='host'` (to disable user namespace remapping) in combination with `privileged=True` to fix the issues you are experiencing with the extractor...