-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate initial OSS-Fuzz support #5850
Comments
I've wondered about fuzzing but whats not too clear to me is what would provide the best value, or in other words, what are the high risk areas. Like in #5851, its parsing strings (not |
Thanks for your response. I agree that the fuzzer in #5851 is unlikely to uncover anything of interest, but I’d like to emphasize that that this is more about integrating OSS-Fuzz support than the specific fuzzers themselves at this stage. We need to ensure that we have the necessary approvals from both parties before diving deep into the fuzzers. The aim is to eventually reach 100% fuzzing coverage through an iterative process of constant refinement. I've updated #5851 to parse I am open to any further suggestions you may have. |
An For me, the big question is "will this be worth it" which is dependent on what a proposed fuzzer looks like. |
@initializedd, I'm sorry, I over-reacted based on my own bad experience with some unknown 3rd party actor. I realize now that it sounds like I am accusing you of malicious behavior. I know nothing about you, and so I cannot fairly comment on your intentions. In retrospect, I don't think my original comment has any value, so I will delete it. |
Thanks for understanding. @epage Are there any specific examples that you would suggest drawing inspiration from to improve the proposed fuzzer? |
I don't know of an example that would be relevant for fuzzing. What I'm asking of you is to propose fuzzing that would provide enough value to be worth it. |
Please complete the following tasks
Clap Version
master
Describe your use case
Initial support for fuzzing clap to discover and fix bugs.
If my fuzzer is merged, I will open a pull request in the OSS-Fuzz repository to run the fuzzers for this library on Google's infrastructure. Maintainers of clap will be notified if any bugs are discovered.
Please see the OSS-Fuzz documentation and Bug disclosure guidelines before merging.
Thanks!
Describe the solution you'd like
PR #5851
Alternatives, if applicable
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: