fuzzit integration example #24
Closed
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
yevgenypats
force-pushed
the
fuzzit
branch
7 times, most recently
from
cdbd0d3 to
31c324c
Compare
|
@xmlking I think we need to wait for this PR to be merged dvyukov/go-fuzz#263 (comment) If this won't be merged then I'll use https://github.com/fuzzitdev/go-fuzz. anyway feel free to comment in the meanwhile. |
|
@yevgenypats thank you for helping to setup fuzzit. Sure I can wait for the go-fuzz module compatibility fix. f.y.i I am using golang 1.13 When you get a changes please rebase your PR. |
|
Closing as service is deprecated and acquired move to be part of GitLab now. |
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.
Hey @xmlking ,
This is still WIP but I just opened this so I can test weather the CI passes.
Anyway, because this is more of boilerplate project I don't see a lot of room for fuzzing here apart from the crypto wrapper that I've added a fuzzer to it. I think if it's more of a boilerplate then maybe you I can add instructions to this PR of how to add another fuzz target to encourage developer to write fuzzer for more heavy functions that have some kind of parsing behaviour.