-
Notifications
You must be signed in to change notification settings - Fork 129
problem about call driller to do symbolic execution job in shellphuzz #24
Comments
Are you using the docker container ( |
@zardus Thanks, in the container driller works, but it seems driller can not generate inputs for non cgc binaries, is that right? |
There are various issues with proper environment modeling in angr, that hampers driller's operation on non-CGC binaries. Extremely simple ones should work, but anything that uses some syscall not modeled by angr (or a summarized library function that's incorrectly summarized) will fail. |
there is no input testcase parameter in shellphuzz , did the initial input for calling afl is auto constructed by itself? |
Was the issue with environment modeling in angr resolved? No matter what non-cgc binaries I pass to shellphuzz it always outputs one or another error happening in Thanks. |
It is a forever-ongoing problem. We are slowly chipping away at the issues but we are a three-person team, after all. |
I'm a little confused about how can shellphuzz call driller, I can not find anywhere import driller module .
Also, I encountered a problem about using shellpuzz to do drilling job, while testing a simple program, the fuzzer get stuck and drilling began. Hower, I got the error as below:
The text was updated successfully, but these errors were encountered: