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

Continuous fuzzing by way of Google's OSS-Fuzz #155

Open
DavidKorczynski opened this issue Sep 5, 2022 · 1 comment
Open

Continuous fuzzing by way of Google's OSS-Fuzz #155

DavidKorczynski opened this issue Sep 5, 2022 · 1 comment

Comments

@DavidKorczynski
Copy link

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.

@MatthieuDartiailh
Copy link
Member

Thanks for reaching out. That sounds interesting, you can use the public email on my profile.

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