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
afl-qemu-trace-32 and afl-qemu-trace-64 #1928
Comments
and how would afl-fuzz know which qemu binary to call? and what if someone wants that for arm64, mips etc.?
and then when fuzzing your simply set |
Hi @vanhauser-thc agreed with your point of considering other architectures. but having an binary selection method (dynamically) would work for this. lets say having a configuration setting for the users to configure the archi's they want to target. give it a thought ✌️ |
Hi, @vanhauser-thc, I think afl-fuzz can automatically select a specific afl-qemu-trace(eg. afl-qemu-trace-arm, afl-qemu-trace-aarch64) by checking the file architecture of the target binary. |
Yeah that would be possible. I have no time for this though as I work on something for a presentation at the ccc congress. |
Hi @ele7enxxh, are you working on this ? |
No, Do you have free time to do it? |
@ele7enxxh Sure, on it! |
Hi,
Sometimes, I need to perform fuzz testing on both 32-bit and 64 bit programs simultaneously. The current compilation and installation will overwrite the previous product afl-qemu-trace binary. Can you add a suffix to distinguish between the two? For example: afl-qemu-trace-32 and afl-qemu-trace-64.
Thanks.
The text was updated successfully, but these errors were encountered: