Added first fuzzer with oss-fuzz build script #306
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a fuzzer and a build script to integrate Pelikan with oss-fuzz for continuous fuzzing.
The fuzzer is implemented by way of LibFuzzer. Fuzzing is a way of testing programs whereby pseudo-random data is passed to a target function with the goal of finding bugs and vulnerabilities. Continuous fuzzing contributes to this in several ways, some of which are:
By setting up continuous fuzzing through oss-fuzz, maintainers are notified if and when bugs are found. Notifications include detailed reports with stacktraces and test cases. oss-fuzz is a free service for open source projects that is offered with an implied expectation that bugs are fixed, so that the resources spent on fuzzing Pelikan are put to good use.
I have the build scripts for the oss-fuzz side as well and will be happy to complete the integration.
The location of the fuzzer and the oss-fuzz build script in the
test/fuzz
dir is a suggestion.