Added fuzzer #279
Open
Added fuzzer #279
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I was wondering if there were updates on this? If you would like for the Ejdb to be fuzzed we would be happy to put more efforts into it - if not then we can just close this PR! @adamansky perhaps? |
Hi! Thank you for this patch! I will apply changes anyway but need more tight integration with cmake and test cases. So I need some spare time to do that. |
|
Are there updates on this PR? A route can be to run the fuzzer in the CI with ClusterfuzzLite. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dear maintainers and contributors of ejdb,
I have worked on the security of your project and set it up such that it can be fuzzed. As such, I thought it could be useful to set ejdb up on the OSS-Fuzz infrastructure, which will allow the current fuzzer to run on Googles infrastructure continuously. If a bug is discovered, the maintainers receive an email with a link to a detailed bug report. This is done free of charge, although there is an expectation that the bugs are fixed so the fuzzers can go on and find new bugs.
The current fuzzer will be enough to integrate with OSS-Fuzz and looking forward if you are happy to receive contributions in this domain then I would be glad to put more efforts into fuzzing ejdb.
If you would like this then please merge in and I will set things up on the OSS-Fuzz end. To complete this initial setup the only thing I need is an email address from you which will receive the bug reports - notice this email address will be public on the OSS-Fuzz repo.