unable to configure maxlength

[0xalpharush]

  -G maxlength  - set max length of generated fuzz input (default: 1048576)

When I pass the flag

afl-fuzz++4.30c based on afl by Michal Zalewski and a large online community

[-] PROGRAM ABORT : Option -G max value is 1048576, change by editing config.h and recompiling afl-fuzz.
         Location : main(), src/afl-fuzz.c:692


If you see an error message like `shmget() failed` above, try running the following command:

    cargo afl system-config

Is there an out-of-the-box way to update the build cargo afl uses?

[smoelius]

Is there an out-of-the-box way to update the build cargo afl uses?

Short answer: no.

The only way to do this right now is to clone this repo, checkout the AFLplusplus submodule, modify the submodule, and install cargo-afl from the cloned repo. (Please let me know if you would like me to be more precise/specific).

To be completely honest, the issue of wanting to test cargo-afl with a modified AFLplusplus has come up a few times for me. Hence, I think we need an ergonomic way to do this.

Within the next few days, I will open an issue with my thoughts on what a solution might look like.

[smoelius]

To be completely honest, the issue of wanting to test cargo-afl with a modified AFLplusplus has come up a few times for me. Hence, I think we need an ergonomic way to do this.

Within the next few days, I will open an issue with my thoughts on what a solution might look like.

Here it is: #605

In particular:

Note: cargo-afl config --build would not attempt to update the contents of the AFLplusplus directory, or verify its integrity. Rather, cargo-afl config --build would treat the directory "as is". Thus, users could make changes to the directory's contents and run cargo-afl config --build --force to test them.

Should you have thoughts on this, I would be interested to hear them.