3 ms·
Awesome! I work on an embedded project that could benefit _enormously_ from having AFL run against it, but I've never taken the time to do it, because it would
by bjackman 11y ago
Awesome! I work on an embedded project that could benefit _enormously_ from having AFL run against it, but I've never taken the time to do it, because it would take several engineer-weeks to even investigate if it could be done. Their approach to "porting AFL to the kernel" makes me think that yes, it would cost perhaps an engineer-month but at least the outcome wouldn't be "nope, not practical". Thumbs up.
- jonhohle 11y agoIf you know the build system for your project, have some way of getting input via stdin, and existing test corpus, it's surprisingly simple. I was able to set it up in a few hours for a moderately sized library. Along with valgrind, I was able to find and fix all of the bugs it uncovered after over a CPU month of testing.
- wyldfire 11y agoArguably llvm's libFuzzer is around the same magnitude of complexity and delivers similar results. I used it to create a fuzzer for CPython [1] and it didn't take terribly long to get something going. Majority of my time's been focusing on new test cases. [1] https://bitbucket.org/ebadf/fuzzpy https://bitbucket.org/ebadf/fuzzpy