Damian Gryski

If you read the AFL mailing list, there are lots of patches /papers that improve AFL's coverage fuzzing in certain cases. It might be interesting to see which of those...

The proper thing to do from GitHub's perspective is to transfer ownership of the existing repo to the organization. This has the benefit that GitHub will handle redirects when people...

@josharian Breaking changes are probably easier before we get integrated into the standard tooling. I wonder if it *does* make sense to leave `dvyukov/go-fuzz` stable and push a clone to...

AFL has a few tools for this: afl-cmin and afl-tmin, but of course neither can be applied directly. It would be nice to have go-fuzz equivalents.

If I spent a lot of effort to construct a corpus, I would be annoyed if go-fuzz deleted some of my samples. Removing files from a corpus on disk should...

I saw this mentioned in https://www.youtube.com/watch?v=n6kP-CWO_0Q with regards to libxml. I had no specific failing use case that this would solve.

Maybe having an external tool similar to "go tool bug" is the right approach here.

Ah yes, missed the reduction in scope to simply adding/running a single test case for a package that already has a full fuzzing infrastructure. I think it will be addressed...

http://resources.sei.cmu.edu/library/asset-view.cfm?assetid=28043 Not sure if that algorithm is applicable since we don't always have a pristine seed file.

It appears the standard algorithm that applies here is https://www.st.cs.uni-saarland.de/papers/tse2002/tse2002.pdf