From 1c64da7314e944d2d42866e3e99df2b9ce28e040 Mon Sep 17 00:00:00 2001 From: Corey Farwell Date: Thu, 16 Aug 2018 16:23:38 -0700 Subject: [PATCH] Add goals of trophy case to the README. Fixes https://github.com/rust-fuzz/trophy-case/issues/42. --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 1a485a8..fb54958 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,11 @@ # 🏆 Trophy Case 🏆 +A showcase of bugs found via fuzz testing Rust codebases. It serves multiple purposes: + +- Help the community see what issues are common in Rust codebases (useful when e.g. designing APIs) +- Increase visibility of effective fuzz testing targets so people can reuse testing strategies +- Provide insight into common issues they can expect to find if they use a certain fuzzer + These bugs aren't nearly as serious as the [memory-safety issues afl has discovered](http://lcamtuf.coredump.cx/afl/#bugs) in C and C++ projects. That's because Rust is memory-safe by default, but also because not many people have tried fuzzing yet! Over time we will update this section with the most interesting bugs, whether they're logic errors or memory-safety problems arising from `unsafe` code. Pull requests are welcome! Security issues are marked with a ❗️ in the "Security?" column. Denial of service, including panics and out-of-memory, are not considered security issues.