Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compare against QSYM #5

Open
DonggeLiu opened this issue Aug 19, 2019 · 1 comment
Open

Compare against QSYM #5

DonggeLiu opened this issue Aug 19, 2019 · 1 comment
Labels
Baseline Issues related to running baselines Docker Issues related to using Dockers

Comments

@DonggeLiu
Copy link
Owner

We do have the docker of QSYM, but:

  1. Cannot do it on MUPPET without solving the rootless docker first
  2. Although they use Tracer, which is from ANGR, I am not too sure if it's a fair comparison as they have multiple optimisations that we did not adopt.
@DonggeLiu DonggeLiu added Baseline Issues related to running baselines Docker Issues related to using Dockers labels Aug 19, 2019
@DonggeLiu
Copy link
Owner Author

Not quite sure if this the right way:

AFL_ROOT="/AFL/afl"
INPUT="/AFL/INPUTS"
OUTPUT="/AFL/OUTPUTS"
AFL_CMDLINE="/replace/replace.afl @@"
QSYM_CMDLINE="/replace/replace"

# run AFL master
$AFL_ROOT/afl-fuzz -M afl-master -i $INPUT -o $OUTPUT -- $AFL_CMDLINE &
# run AFL slave
$AFL_ROOT/afl-fuzz -S afl-slave -i $INPUT -o $OUTPUT -- $AFL_CMDLINE  &
# run QSYM
bin/run_qsym_afl.py -a afl-slave -o $OUTPUT -n qsym -- $QSYM_CMDLINE

It did not give too many inputs, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Baseline Issues related to running baselines Docker Issues related to using Dockers
Projects
None yet
Development

No branches or pull requests

1 participant