Skip to content

Conversation

@arthurscchan
Copy link
Contributor

@arthurscchan arthurscchan commented Oct 21, 2024

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.

@DavidKorczynski
Copy link

Just noticed #17 -- apologies for the double issue/PR @LeoDog896

Copy link
Owner

@pyfisch pyfisch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for adding an additional fuzzer! I don't think there is a need for continuous fuzzing by Google as this is a really small crate but if one issue is found that is great.

Signed-off-by: Arthur Chan <[email protected]>
@arthurscchan
Copy link
Contributor Author

@pyfisch I have fixed the name of the fuzzing harness and remove the misleading license. Is it OK to add your email of your github account to OSS-Fuzz thus you could receive notification when OSS-Fuzz does discover some issues?

@arthurscchan arthurscchan requested a review from pyfisch December 10, 2024 19:47
@pyfisch pyfisch merged commit 53df520 into pyfisch:main Dec 22, 2024
2 checks passed
@pyfisch
Copy link
Owner

pyfisch commented Dec 22, 2024

@arthurscchan Thank you for adding the fuzzer! You can add my email address to OSS-Fuzz.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants