Enkelmann

Well, we disabled the CWE-78 check on a standard run for a reason: It was leading to runtime explosion on a lot of binaries when enabled. Since then a lot...

FACT aborts the cwe_checker when a timeout is reached. And if that happens you do not get any results for any of the cwe_checker checks for the corresponding binary. So...

I see that you took route b) in your PR, which should result in a better CFG than route a). I approve, although it makes it more difficult to be...

I am always happy for contributions, although I am not entirely sure what the question is. I will try to answer it anyway, but you may need to clarify your...

To be more precise we look for the call that prints the version string (and not only the basic block where it happens). And then we follow the other parameters...

@yamiyugi123 If this turns out to be a Docker-specific certificate error, I cannot help you. But it also might be just a temporary problem on the `crates.io` side. Have you...

I might have an idea why the old code did not catch the case: We use the CFG to check for incoming edges when removing blocks, right? But if a...

Your updated `ToJsonCompact` format looks very good! Right now, your option a) would probably result in the best CFG that we can generate. Just make sure to mention it prominently...

The most common causes for these error messages in the log are corrupted ELF binaries and timeouts. Corrupted ELF binaries are quite commonly generated if the unpacking algorithm (incorrectly) unpacks...

For the file in your screenshot the file type is identified as `data`. The cwe_checker plugin only runs on files that are identified as ELF executables. That is why it...