You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if you would like to integrate continuous fuzzing by way of OSS-Fuzz? Fuzzing is a way to automate test-case generation and can be used to find unexpected exceptions in Python and memory corruption issues in native code. In this PR google/oss-fuzz#8237 I did an initial integration into OSS-Fuzz. The initial fuzzer creates a constraint based on
data extracted from the fuzz engine and the goal is to catch memory corruption issues in the native code. I think there is room to extend the fuzzing and would be happy to do so down the line.
OSS-Fuzz is a service run by Google for important open source projects. If you would like to integrate, the only thing I need is a list of email(s) that will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. Notice the emails affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.
The text was updated successfully, but these errors were encountered:
Hi,
I was wondering if you would like to integrate continuous fuzzing by way of OSS-Fuzz? Fuzzing is a way to automate test-case generation and can be used to find unexpected exceptions in Python and memory corruption issues in native code. In this PR google/oss-fuzz#8237 I did an initial integration into OSS-Fuzz. The initial fuzzer creates a constraint based on
data extracted from the fuzz engine and the goal is to catch memory corruption issues in the native code. I think there is room to extend the fuzzing and would be happy to do so down the line.
OSS-Fuzz is a service run by Google for important open source projects. If you would like to integrate, the only thing I need is a list of email(s) that will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. Notice the emails affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.
The text was updated successfully, but these errors were encountered: