This repository was archived by the owner on May 18, 2024. It is now read-only.
Added 3 fuzzers #53
Open
Added 3 fuzzers #53
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 3 fuzzers.
Since stringencoders is a security-critical library for Chromium, it might be worth it to integrate it into oss-fuzz to setup continuous fuzzing. I can confirm that these 3 fuzzers run on their infrastructure.
oss-fuzz is a free service, however it is expected that the found bugs are fixed, so Googles resources are well spent.
I will be happy to setup continuous integration of stringencoders.
If there aren't resources to fix the bugs found by the fuzzers, we may ask Google if they are interested in fuzzing the library anyway, as they currently use it. In this case, it would be helpful to have the fuzzers on the upstream repository as well.