Mathieu Tarral

I agree that `make deploy` should result in a defined state, and ignoring a dirty repo is not a defined state. I don't want to duplicate deployment / installation knowledge...

The PR #81 introduces a `build` tag that does just that (rebuild qemu, radamsa and reinstall the fuzzer) 

> ansible asks for BECOME password without reason. Maybe we can make it a dependency of the tasks that actually need sudo? Asking for BECOME password is done by a...

> I think make open_docs this won't work on Windows remote terminal On Windows you don't have make by default, so kafl's dev environment is not targeting Windows users anyway....

> I know how it works, just saying that it may not exist on a server install On a server install I assume you are running kAFL, not developing. >...

- you are correct that the remote deployment still needs to reworked in terms of which workflow we want to enable in the end. The goal is not to enable...

The Ci takes ages to execute the Linux Security hook workflow ! we are at +50min here and not ending ! I don't really understand what is happening

Issue is opened on volatility3 repo: https://github.com/volatilityfoundation/volatility3/issues/242

Looking at `kcc`, it doesn't have `JSON` output format, so it woud be difficult to load the data in the security hook, like we do with `checksec`: https://github.com/Wenzel/oswatcher/blob/master/hooks/security.py#L31 However, `kcc`...

Actually this one is more maintained: https://github.com/a13xp0p0v/kconfig-hardened-check I opened an issue there https://github.com/a13xp0p0v/kconfig-hardened-check/issues/20