-
-
Notifications
You must be signed in to change notification settings - Fork 312
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
OSSFuzz Integration #744
Comments
If you want, you can do it. Please in a separate Github task, so that it can run independently from normal build. |
@gittiver Sounds great, I will submit it for review! All I need is an email address to serve as the primary contact (preferably a GMail account). This email will receive access to the ClusterFuzz dashboard to review crashing testsuites and discovered bugs. |
@gittiver Just pinging again, I could utilize my email as the primary POC if you want. However, if you would like access to the dashboard that displays the discovered crashes, a gmail account will be needed |
use your own for first POC. I try to find out what and how email-addresses are used. |
@gittiver Can do, thank you! |
@gittiver If you're curious what the email is used for, you can read more here: https://google.github.io/oss-fuzz/getting-started/accepting-new-projects/ |
Hello!
I am curious if the project maintainers would be open to me proposing this project for integration into Google's OSS-Fuzz project? I would develop the build script and fuzz targets necessary to integrate this repository for nightly fuzz-testing and would just need the eventual PR review. My current thoughts would be in adding fuzz-testing for crow's handling and parsing of incoming HTTP requests, but am open to any other points of entry into the library that you might think would benefit from fuzz-testing.
Thank you for your time!
The text was updated successfully, but these errors were encountered: