fuzzpackage is organized into subpackages which are named after the
lndpackage they test. Each subpackage has its own set of fuzz targets.
This section will cover setup and installation of the fuzzing binaries.
- The following is a command to build all fuzzing harnesses:⛰ make fuzz-build
- This may take a while since this will create zip files associated with each fuzzing target.
- The following is a command to run all fuzzing harnesses for 30 seconds:⛰ make fuzz-run
go-fuzzwill print out log lines every couple of seconds. Example output:
2017/09/19 17:44:23 workers: 8, corpus: 23 (3s ago), crashers: 1, restarts: 1/748, execs: 400690 (16694/sec), cover: 394, uptime: 24s
Corpus is the number of items in the corpus.
go-fuzzmay add valid inputs to the corpus in an attempt to gain more coverage. Crashers is the number of inputs resulting in a crash. The inputs, and their outputs are logged by default in:
go-fuzzalso creates a
suppressionsdirectory of stacktraces to ignore so that it doesn't create duplicate stacktraces. Cover is a number representing edge coverage of the program being fuzzed.
Several parameters can be appended to the end of the make commands to tune the build process or the way the fuzzer runs.
run_timespecifies how long each fuzz harness runs for. The default is 30 seconds.
timeoutspecifies how long an individual testcase can run before raising an error. The default is 20 seconds.
processesspecifies the number of parallel processes to use while running the harnesses.
lndpackages to build or fuzz. The default is to build and run all available packages (
brontide lnwire wtwire zpay32). This can be changed to build/run against individual packages.
base_workdirspecifies the workspace of the fuzzer. This folder will contain the corpus, crashers, and suppressions.
Fuzzing generally works best with a corpus that is of minimal size while achieving the maximum coverage.
go-fuzzautomatically minimizes the corpus in-memory before fuzzing so a large corpus shouldn't make a difference.