434b
434b
> Maybe you can provide a minimal configuration to reproduce it I’ll be on vacation for a while now. Maybe @HUGO-castell or @noname2001 can chip in. Otherwise I’ll see what...
Base64 has no special delimiter symbol. Also there are multiple possible and valid B64 encodings as listed in: https://en.wikipedia.org/wiki/Base64#Variants_summary_table Unpacking b64 is trivial. However determining if a string sequence is...
I can imagine a `aflr cov` sub-command that would aggregate the coverage data across all runs and just outputs it in some form, probably the HTML report would be best.....
I'll try to work on this in a timely manner. PRs are very much appreciated though!
One way I could think of would be introducing something like `afl_flags_partial`, similar to the already existing `afl_flags`. The format could either be based on AFL environment variables like `AFL_USE_QASAN=X:0.3`,...
Good observation regarding the cases where you need multiple env vars and/or more complex parameters.. I couldnt come up with something that fits nicely for an environment variable yet but...
Something like this could work. I would like to keep the option to have AFL_Runner parse the AFL_* flags, which could be useful for quick tests or similar where it’s...
I just thought about something. I updated some of the implementations in #52 [[1](https://github.com/0xricksanchez/AFL_Runner/blob/168778d85a7115d7ff696b330e80350165a48d89/src/afl_cmd_gen.rs#L121)] and #53 [[2](https://github.com/0xricksanchez/AFL_Runner/blob/168778d85a7115d7ff696b330e80350165a48d89/src/afl_cmd_gen.rs#L154)] for how arguments are added to the command, either independently or mutually exclusive....
> I guess I need to rebase my feature branch... Sorry for that :smile: > Do you have or plan to write the same function for env variable? In that...
@wizche I rewrote most if not all the core-logic of the code to hopefully increase maintainability and having easier access for adding new features. That said, the bad news is...