Skip to content
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

Integration with oss-fuzz fuzzing service #90

Open
manunio opened this issue Oct 3, 2022 · 1 comment
Open

Integration with oss-fuzz fuzzing service #90

manunio opened this issue Oct 3, 2022 · 1 comment

Comments

@manunio
Copy link

manunio commented Oct 3, 2022

Hi @hsivonen, I would like to help integrate this project into OSS-Fuzz.

  • As an initial step for integration I have created this PR: encoding_rs: initial integration google/oss-fuzz#8652, it contains necessary logic from an OSS-Fuzz perspective to integrate encoding_rs.

  • OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects.

  • As encoding_rs already have cargo-fuzz based fuzzing implemented, this makes it easily compatible with oss-fuzz out of box.

  • If you would like to integrate, the only thing I need is a list of email(s), it must be associated with a google account like
    gmail (why?). by doing that, the provided email(s) will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats.

  • As an alternative, if you don't have a google/gmail id, but still wish to integrate. I can add my mail id for time being and monitor bug/crashes.

  • Notice the email(s) affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.

@hsivonen
Copy link
Owner

hsivonen commented Oct 4, 2022

It's OK to list hsivonen at both gmail.com and mozilla.com as notice emails, but as noted on the OSS-Fuzz PR, given my expectation level of a fuzzer finding something at this point, I feel bad about using resources for continuous fuzzing of encoding_rs at this time. (fuzz_labels should be excluded at least; the probability of it finding something is pretty much zero at this point.)

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

No branches or pull requests

2 participants