afl-tmin and afl-cmin - in which order?

[hessno...@mail.com]

Does it counts that when I want to minimize my testcases I run:

afl-tmin
afl-cmin

or in opposite order:

afl-cmin
afl-tmin

Would I end up with the same results when fuzzing? Do the order count?

In my logic, maybe first afl-tmin to minimize file sizes, then afl-cmin to remove the duplicated minimized files. But what is the reality?

[Vincent LE GARREC]

The result should be the same.

Start with afl-cmin. afl-tmin is very slow.

[Jakub Wilk]

* hessno...@mail.com, 2018-05-05, 05:17:

>Does it counts that when I want to minimize my testcases I run:
>
>afl-tmin
>afl-cmin
>
>or in opposite order:
>
>afl-cmin
>afl-tmin
>
>Would I end up with the same results when fuzzing? Do the order count?

tmin+cmin might produce smaller inputs, but it's also likely to be
significantly slower. I would recommend cmin+tmin.

--
Jakub Wilk

[Brandon Perry]

FWIW I wrote a bash script that I use to parallelize afl-tmin to X cores.

https://gist.github.com/brandonprry/4305328f069f7a951ccc

It should be important to note why you should run afl-cmin first. If you start with afl-tmin, you will waste time minimizing inputs that are functionally equivalent. If you minimize the corpus first with afl-cmin, then you will have only functionally unique inputs that you can then minimize.

--
Jakub Wilk

--
You received this message because you are subscribed to the Google Groups "afl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to afl-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.