87098d3324
This is something I hadn't previously done, but there are cases where it's needed, e.g., building 'wlantest' and then one of the tests/fuzzing/*/ projects, they use a different configuration (fuzzing vs. not fuzzing). Perhaps more importantly, this gets rid of the last thing that was dumped into the source directories, apart from the binaries themselves. Note that due to the use of thin archives, this required building with absolute paths. Signed-off-by: Johannes Berg <johannes.berg@intel.com> |
||
|---|---|---|
| .. | ||
| ap-mgmt | ||
| asn1 | ||
| dpp-uri | ||
| eap-aka-peer | ||
| eap-mschapv2-peer | ||
| eap-sim-peer | ||
| eapol-key-auth | ||
| eapol-key-supp | ||
| eapol-supp | ||
| json | ||
| p2p | ||
| sae | ||
| tls-client | ||
| tls-server | ||
| wnm | ||
| x509 | ||
| build-test.sh | ||
| fuzzer-common.c | ||
| fuzzer-common.h | ||
| README | ||
| rules.include | ||
hostap.git fuzz testing ----------------------- These tools can be used for fuzz testing of various components used within wpa_supplicant and hostapd. Each directory contains a fuzzing tool that focuses on one input handler. Each tool can be compiled either to work with the libFuzzer or as a separate tool that reads the input from a file specified on the command line, e.g., for American fuzzy lop (afl-fuzz). Example test corpus is included in */corpus directory. Example fuzzing with libFuzzer cd @TOOL@ make clean make LIBFUZZER=y ./@TOOL@ corpus Example fuzzing with afl-fuzz cd @TOOL@ make clean CC=afl-gcc make afl-fuzz -i corpus -o findings -- $PWD/@TOOL@ @@