libtorrent fuzzing

Fuzzing of various libtorrent APIs (both internal and external), inspired by Kostya Serebryany's cppcon 2017 presentation_

This project requires:

.. _cppcon 2017 presentation: https://www.youtube.com/watch?v=k-Cv8Q3zWNQ&index=36&list=PLHTh1InhhwT6bwIpRk0ZbCA0N2p1taxd6

clang .....

A version of clang that supports libFuzzer (clang 6.0 or later).

boost-build ...........

Also known as b2. To configure boost build with clang, create a file named user-config.jam in your home directory (~/user-config.jam) with the following content (adjusting for your specific version if necessary)::

using clang : : clang++-18 ;

corpus ......

The corpus is the set of inputs that has been built by libFuzzer. It's the seed for testing more mutations. The corpus is not checked into the repository, before running the fuzzer it is advised to download and unzip the corpus associated with the latest release on github.

https://github.com/arvidn/libtorrent/releases/download/libtorrent_1_2_0/corpus.zip

Uzip the corpus in the fuzzers directory::

unzip corpus.zip

building ........

To build the fuzzers, use the toolset=clang property::

b2 toolset=clang stage

The fuzzer binaries will be placed in the fuzzers directory.

running .......

To run the fuzzers, there's a convenience run.sh script that launches all fuzzers in parallel. By default, each fuzzer runs for 48 hours. This can be adjusted in the run.sh script.

contribute ..........

Please consider contributing back any updated corpuses (amended by more seed inputs) or fuzzers for more APIs in libtorrent.