Input binary
Elothis opened this issue · 2 comments
Elothis commented
Hey,
Im currently looking into using Driller via this python wrapper, and cannot quite answer the following question from just the readme:
What kind of binary has to be specified via the command line for it to work? Is it just the normally compiled binary (standard gcc/g++) and AFL then works via qemu mode on it, or does it have to be instrumented and compiled with the AFL compiler (afl-cc)?
Thanks :)
zardus commented
It's the former, but keep in mind that angr's environment model is ...
lacking, so if your binary makes complex syscalls (with a very loose
definition of complex), there will be dragons.
…On Fri, Dec 21, 2018 at 4:46 AM Elothis ***@***.***> wrote:
Hey,
Im currently looking into using Driller via this python wrapper, and
cannot quite answer the following question from just the readme:
What kind of binary has to be specified via the command line for it to
work? Is it just the normally compiled binary (standard gcc/g++) and AFL
then works via qemu mode on it, or does it have to be instrumented and
compiled with the AFL compiler (afl-cc)?
Thanks :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#37>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADSzl6yN-WTZCYmLerUG9zWW5_xNxzTeks5u7MovgaJpZM4Zd3EC>
.
Elothis commented
Thanks!