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

Enable simple monolith fuzzing #4155

Closed
zebambam opened this issue Oct 14, 2019 · 4 comments
Closed

Enable simple monolith fuzzing #4155

zebambam opened this issue Oct 14, 2019 · 4 comments
Assignees
Labels
A-fuzzer Area: The fuzzers and fuzzing infrastructure. I-SECURITY Problems and improvements related to security.

Comments

@zebambam
Copy link

Write a simple harness for AFL fuzzing any part of the C++ monolith. Specifically, developers should only have to read input from stdin and provide that input to wherever they desire in the codebase by writing a small main function to replace the daemon's usual main.

It should be integrated into the zcash codebase in such a way that future CI systems can require that written fuzzers continue to work across merges into the main (currently master) branch, even though the results of the fuzzing don't necessarily break the merge.

The ultimate goal of this work is to normalize the creation of fuzzers alongside simple unit tests for new or modified code that is considered to be relevant - parsers, network message handlers, etc.. should be covered.

The infrastructure and tending to running continuous security integration can then be owned and operated across the devinf and security teams.

@zebambam zebambam added the I-SECURITY Problems and improvements related to security. label Oct 14, 2019
@zebambam zebambam self-assigned this Oct 14, 2019
zebambam pushed a commit to zebambam/zcash that referenced this issue Oct 15, 2019
@leto
Copy link
Contributor

leto commented Oct 19, 2019

This is a good idea 👍

@defuse
Copy link
Contributor

defuse commented Oct 22, 2019

PR: #4167

@oxarbitrage
Copy link
Contributor

It seems this issue can be closed with the merge of #4167 ?

@daira daira added the A-fuzzer Area: The fuzzers and fuzzing infrastructure. label Mar 30, 2020
@daira
Copy link
Contributor

daira commented Mar 30, 2020

Yes I think so.

@daira daira closed this as completed Mar 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-fuzzer Area: The fuzzers and fuzzing infrastructure. I-SECURITY Problems and improvements related to security.
Projects
None yet
Development

No branches or pull requests

5 participants