kAFL
kAFL copied to clipboard
kAFL/Nyx alignment
The goal of this issue is to spark the discussion on the current state of kAFL compared to the Nyx project, how we might want to align kAFL to match Nyx's future evolutions.
TODO
- [x] Generate
cargo docdocumentation for libnyx (see attachments: libnyx_doc.zip)- [x] ensure libnyx can be compiled (https://github.com/nyx-fuzz/libnyx/pull/21, https://github.com/nyx-fuzz/libnyx/pull/20)
- [ ] Document kAFL's fuzzer interface to QEMU (
qemu_aux_buffer.py, ...) - [ ] Document differences between kAFL and Nyx project
- [ ] Sketch out a new design for libnyx API
- [ ] Collect requirements from all possible use cases, and consider future evolutions
- [ ] How to propagate kafl configuration to libnyx
- [ ] Hold design session
- [ ] Collect requirements from all possible use cases, and consider future evolutions
cc @schumilo for the brainstorming
Updating this ticket, i've managed to write some documentation on the current Fuzzer <=> QEMU interface in kAFL: fuzzer_qemu_interface.zip
We should have another quick sync on this @schumilo and determine the next steps !