OSS-Fuzz: OSS-Fuzz fuzzing integration #179
Open
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]>
|
Thanks for the PR, unfortunately |
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.
Hello! Would you be open to setting up fuzzing for the ttf-parser module with OSS-Fuzz?
Fuzzing can be a helpful way to uncover bugs through stress-testing, and Google’s OSS-Fuzz offers a free, continuous fuzzing service for open-source projects, which could help catch any potential memory issues in ttf-parser.
I noticed there are three cargo-afl fuzzers in the directory. Since OSS-Fuzz works with cargo-fuzz, I’ve converted these fuzzers to cargo-fuzz compatibility and added four more, hoping to expand the fuzzing scope and improve code coverage. In combination with an initial attempt in OSS-Fuzz (google/oss-fuzz#12663), this setup also enables OSS-Fuzz to fuzz the ttf-parser module while keeping the fuzzers upstream for further modification and expansion. If you’d be interested in moving forward with this integration and storing the fuzzers upstream, please let me know—I’d be happy to share more details if needed. Any feedback or suggestions would be truly appreciated.
The only requirement at this stage is a Google-linked email for receiving bug notifications.
Thank you very much!