Skip to content

libbson fuzzer for OSS-Fuzz integration. #706

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

Merged
merged 2 commits into from
Dec 15, 2020

Conversation

DavidKorczynski
Copy link
Contributor

@DavidKorczynski DavidKorczynski commented Dec 8, 2020

Hi

I have integrated fuzzing into libbson and was thinking that it would be nice to set up continuous fuzzing by way of OSS-Fuzz. In this PR: google/oss-fuzz#4808 I have done exactly that, namely created the necessary logic from an OSS-Fuzz perspective to integrate. In that PR you also see the fuzzer attached, but it would be nicer to have the fuzzer integrated into the upstream project itself rather than keeping it in OSS-Fuzz - so if this PR gets merged I will remove it from OSS-Fuzz

Essentially, OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects. The only expectation of integrating into OSS-Fuzz is that bugs will be fixed. This is not a "hard" requirement in that no one enforces this and the main point is if bugs are not fixed then it is a waste of resources to run the fuzzers, which we would like to avoid.

If you would like to integrate, could I please have an 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 and they also need to be linked with a Google account to get the detailed reports.

David

@kevinAlbs
Copy link
Collaborator

Hi @DavidKorczynski, thank you for your the PR! That's really awesome. We have used the LLVM fuzzer in one-off trials to find bugs in libbson, but I do think it'd be valuable to have to it run continuously. I will discuss it with our team.

Copy link
Contributor

@rcsanchez97 rcsanchez97 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kevinAlbs
Copy link
Collaborator

Thank you again @DavidKorczynski! I contacted you via the email listed on your GitHub profile with an account I created for receiving OSS-Fuzz reports.

Also noteworthy in case you are interested, we do have fuzz testing in our backlog for the libmongocrypt project (https://github.com/mongodb/libmongocrypt).

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

Successfully merging this pull request may close these issues.

3 participants