You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
hostap/tests/fuzzing
Tom Barthe 12c14a8dd5 Replace some vlan_ids with vlan_descriptions
It should ease the integration of PPSK.

Signed-off-by: Tom Barthe <jeltz+hostap@auro.re>
3 years ago
..
ap-mgmt build: Put archive files into build/ folder too 4 years ago
asn1 build: Put archive files into build/ folder too 4 years ago
dpp-uri build: Put archive files into build/ folder too 4 years ago
eap-aka-peer tests: Limit maximum number of frames in fuzzing tests 3 years ago
eap-mschapv2-peer build: Put archive files into build/ folder too 4 years ago
eap-sim-peer tests: Limit maximum number of frames in fuzzing tests 3 years ago
eapol-key-auth Replace some vlan_ids with vlan_descriptions 3 years ago
eapol-key-supp build: Put archive files into build/ folder too 4 years ago
eapol-supp build: Put archive files into build/ folder too 4 years ago
json build: Put archive files into build/ folder too 4 years ago
p2p tests: Fix p2p fuzzer build after API change 3 years ago
sae build: Put archive files into build/ folder too 4 years ago
tls-client build: Put archive files into build/ folder too 4 years ago
tls-server build: Put archive files into build/ folder too 4 years ago
wnm wpa_supplicant: Move wpa_config_get_line() into utils 3 years ago
x509 build: Put archive files into build/ folder too 4 years ago
README tests: New style fuzzing tool for wpa_supplicant WNM handling 5 years ago
build-test.sh tests: Build test for new fuzzer tools 5 years ago
fuzzer-common.c tests: New style fuzzing tool for wpa_supplicant WNM handling 5 years ago
fuzzer-common.h tests: New style fuzzing tool for wpa_supplicant WNM handling 5 years ago
rules.include build: Put archive files into build/ folder too 4 years ago

README

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@ @@