Making QEMU utilization an option instead of forced. Still defaulting behavior to using it.
Open question on handling this in the future. You can tell if the binary is instrumented by checking for afl naming conventions (as I'm doing in autoPwn). It would make sense to do that in fuzzer and just have it default to the correct choice. Only problem is that it doesn't load up the project by default, and loading the project could add a decent load time overhead.
Interested in your thoughts on that tradeoff. For now, I'm fine controlling that choice from autoPwn. I would rather have the smarts be built into fuzzer though.
Making QEMU utilization an option instead of forced. Still defaulting behavior to using it.
Open question on handling this in the future. You can tell if the binary is instrumented by checking for afl naming conventions (as I'm doing in autoPwn). It would make sense to do that in fuzzer and just have it default to the correct choice. Only problem is that it doesn't load up the project by default, and loading the project could add a decent load time overhead.
Interested in your thoughts on that tradeoff. For now, I'm fine controlling that choice from autoPwn. I would rather have the smarts be built into fuzzer though.