Skip to content

Randomize scheduler/mutator for secondary instances#1

Open
wizche wants to merge 1 commit intofekir:masterfrom
wizche:patch-1
Open

Randomize scheduler/mutator for secondary instances#1
wizche wants to merge 1 commit intofekir:masterfrom
wizche:patch-1

Conversation

@wizche
Copy link

@wizche wizche commented Jan 12, 2021

When starting a slave instance it randomly select a power scheduler and if to use the MOpt mutator (-L 0)

When starting a slave instance it randomly select a power scheduler and if to use the MOpt mutator (`-L 0`)
@wizche wizche changed the title Randomize scheduler Randomize scheduler/mutator for secondary instances Jan 12, 2021
@fekir
Copy link
Owner

fekir commented Jan 13, 2021

Hello @wizche , thank you for your PR.

I just looked at the man page of afl (never used the scheduler), AFAIK the parameter you added can be passed to the main instance too, correct?

Edit: for clarification

I'm asking because the intent of afl-pfuzz is to be as thin as possible.
I would prefer leaving those options out, unless those are necessary for working correctly.

Even the help of afl-pfuzz is a wrapper around afl-fuzz, and parameter parsing tries to ignore everything that it does not care about.

I currently see no reason why the caller of afl-pfuzz could not provide -p scheduler (as as far I understood its supported by the master too), this way afl-pfuzz remains compatible with the original afl, and does not need to know what scheduler are actually implemented.

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

Successfully merging this pull request may close these issues.

2 participants