This repository has been archived by the owner on May 21, 2022. It is now read-only.
Added a fuzzer #405
Open
Added a fuzzer #405
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
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 a fuzzer for the parser.
If there is interest for fuzzing jwt-go, I will be happy to add more fuzzers and setup continuous fuzzing through oss-fuzz. This will allow Google to run the fuzzers continuously and send bug reports if bugs are found. It is a free service that is offered with an implied expectation that bugs are fixed, so that the resources spent on fuzzing jwt-go are well spent.
To setup continuous fuzzing, all I need are the emails for the bug reports. These will be added to a public list that can be changed anytime.