OSS-Fuzz: OSS-Fuzz integration and new fuzzers #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Arthur Chan <[email protected]>
|
Just noticed #17 -- apologies for the double issue/PR @LeoDog896 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi! Would you be interested in setting up fuzzing via OSS-Fuzz?
I noticed that this project already has a Cargo Fuzz setup with existing fuzzers. This PR further expands the fuzzing coverage by adding a second fuzzer to the configuration. I have also created an initial integration in google/oss-fuzz#12628. If you're happy to proceed with the integration, please let me know, and I'd be happy to elaborate on any points if needed.
The only thing required at this point for integration is an email associated with a Google account, which will be used to receive notifications when bugs are found.