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

Monitor thread #2

Open
GrosQuildu opened this issue Apr 8, 2020 · 0 comments
Open

Monitor thread #2

GrosQuildu opened this issue Apr 8, 2020 · 0 comments

Comments

@GrosQuildu
Copy link

Good morning,
I have question regarding the paper. More precisely: monitoring thread.

Lets assume there are two base fuzzers: A and B. Monitor try to sync some seed s. It checks coverage with A, update GlobalCover (!) and push the seed to A queue. Then checks coverage with B. It is most probably exactly the same as for fuzzer A (because for example both A and B are afl-based fuzzers). So newCover is empty and s will not be pushed to B queue.

It my understanding of the monitor algorithm correct? If yes, is the algorithm correct? Because intuitively we want diverse fuzzers to share that seed s. It should be fuzzed by both A and B as they may implement different mutations for example.

In other words, shouldn't GlobalCover be per-fuzzer variable (each fuzzer's coverage would be kept by monitor). Or if we really want to push s to only one fuzzer at a loop iteration (sync cycle), then in the next cycle it should be pushed again, but to different fuzzer maybe?

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

No branches or pull requests

1 participant