Skip to content
#

fuzz-testing

Here are 97 public repositories matching this topic...

fitzgen
fitzgen commented Nov 22, 2019

This is something that hasn't been super clear to me, and I haven't really seen it discussed anywhere ever.

The corpus

  • can end up getting sizable (see also #163)
  • often isn't human readable

Committing it to the project-being-fuzzed's repo seems like it could add a bunch of git overhead and even make merges difficult.

But, it is needed to "pick up where you left off" when doing time

kjk
kjk commented Aug 5, 2019

Currently, the user has 2 to create a .tar.gz archive of the corpus in order to submit it with --seed arg.

To save this step --seed arg should also take a directory name. If it's a directory, it does the creating of .tar.gz itself.

Also, should validate that there are no subdirectories (which is probably a mistake) and that there is at least 1 file.

cyplo
cyplo commented Apr 25, 2017

Hello !
I tried to follow the tutorial on Fedora 25, default installation.
I believe docker needs additional mount flag to behave properly on SELinux systems -Z
Not sure what does this flag do if the systems is not SELinux-enabled tbh, can find out.

I can try writing a PR for the docs to mention that case, please let me know if that would be ok.

thanks a lot and have a great day !

Improve this page

Add a description, image, and links to the fuzz-testing topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the fuzz-testing topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.