Integration with oss-fuzz fuzzing service
manunio opened this issue · comments
Hi @sunng87, I would like to help integrate this project into OSS-Fuzz.
-
As an initial step for integration I have created this PR: google/oss-fuzz#8649, it contains necessary logic from an OSS-Fuzz perspective to integrate handlebars-rust.
-
OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects.
-
As handlebars-rust 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.
@manunio Thank you for your proposal! Although we had some fuzz test config but we did not pass the test. As a template engine our input is typically something looks like a handlebars template. At least for now, I think fuzz test does little help to improve the library.
I just moved our unmaintained fuzz tests.
Anyway, thank you very much for investigating oss-fuzz for handlebars-rust.
@manunio Thank you for your proposal! Although we had some fuzz test config but we did not pass the test. As a template engine our input is typically something looks like a handlebars template. At least for now, I think fuzz test does little help to improve the library.
I just moved our unmaintained fuzz tests.
Anyway, thank you very much for investigating oss-fuzz for handlebars-rust.
Hi, Thanks for your response and taking your time to consider this proposal, Will you be interested in this proposal again, if fuzzing finds some bugs or helps someway in improving this library?