Protocol fuzzing #21
Merged
Protocol fuzzing #21
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
rus-alex
force-pushed
the
testing/protocol-fuzz
branch
3 times, most recently
from
e065de5 to
6ab1061
Compare
rus-alex
force-pushed
the
testing/protocol-fuzz
branch
from
8a26d4d to
cbe8d6b
Compare
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.
Fuzzing is mainly applicable to packages that parse complex inputs (both text and binary), and is especially useful for hardening of systems that parse inputs from potentially malicious users (e.g. anything accepted over a network).
Also fuzzing was used for go-ethereum testing.
Gossip ProtocolManager fuzzer is here. No matter changes here, fuzzing tools only.
Note:
replace github.com/dvyukov/go-fuzz => github.com/guzenok/go-fuzzis till PR dvyukov/go-fuzz#311 merged.