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

Setup fuzzing with afl #166

Open
slaperche-scality opened this issue Feb 10, 2018 · 0 comments
Open

Setup fuzzing with afl #166

slaperche-scality opened this issue Feb 10, 2018 · 0 comments

Comments

@slaperche-scality
Copy link
Contributor

afl is a kind of "intelligent" fuzzer that feeds "random-not-so-random" inputs to a software to test its robustness.
It uses compile time instrumentation to monitor in real time which code path is covered by the input, and then works by mutating the input to try to reach new uncovered code path.
When it trigger a crash, it saves the input (so we can replay it to debug).
It's kind of compiler-guided fuzzing, which is more efficient than random fuzzing and cover more code than manual fuzzing.

Codec are a very good target for this (since they are supposed to accept almost anything in input without crashing).

As fuzzing is a long-running process (i.e not sth that can be done in the CI) we could imagine having a VM that run continuously a fuzzer on some specific tag (like a beta of our next release ot sth like that).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant