| Mike Aizatsky | 3986fa3 | 2016-09-14 09:44:10 -0700 | [diff] [blame] | 1 | # oss-fuzz |
| 2 | |
| Mike Aizatsky | e279ff2 | 2016-10-19 10:52:28 -0700 | [diff] [blame^] | 3 | > Fuzzing Open Source Software. |
| Mike Aizatsky | 3986fa3 | 2016-09-14 09:44:10 -0700 | [diff] [blame] | 4 | |
| Mike Aizatsky | 4407d87 | 2016-10-19 10:52:02 -0700 | [diff] [blame] | 5 | *Project Status*: We are preparing the project for the first public release. Documentation and smoothing the process is our main priority. |
| Mike Aizatsky | 3986fa3 | 2016-09-14 09:44:10 -0700 | [diff] [blame] | 6 | |
| Mike Aizatsky | ab9edb1 | 2016-10-17 13:01:00 -0700 | [diff] [blame] | 7 | [Open new issue](https://github.com/google/oss-fuzz/issues/new) for questions or feedback. |
| Mike Aizatsky | 7273285 | 2016-10-17 12:59:36 -0700 | [diff] [blame] | 8 | |
| Mike Aizatsky | 3986fa3 | 2016-09-14 09:44:10 -0700 | [diff] [blame] | 9 | ## Documentation |
| 10 | |
| 11 | * [New Library Guide](docs/new_library.md) walks through steps necessary to add fuzzers to an open source project. |
| Mike Aizatsky | 3e3dcd2 | 2016-09-27 11:59:07 -0700 | [diff] [blame] | 12 | * [Running and Building Fuzzers](docs/building_running_fuzzers.md) documents the process for fuzzers that are |
| 13 | *part of target project* source code repository. |
| 14 | * [Running and Building External Fuzzers](docs/building_running_fuzzers_external.md) documents the process for fuzzers that are |
| 15 | *part of oss-fuzz* source code repository. |
| Mike Aizatsky | ef4d3ae | 2016-10-06 13:59:17 -0700 | [diff] [blame] | 16 | * [Project List](docs/projects.md) lists OSS projects integrated with oss-fuzz. |
| Oliver Chang | 5d4f10f | 2016-10-17 10:23:28 -0700 | [diff] [blame] | 17 | * [Life of a bug](docs/life_of_a_bug.md) |
| Mike Aizatsky | 4407d87 | 2016-10-19 10:52:02 -0700 | [diff] [blame] | 18 | * [Chrome's Efficient Fuzzer Guide](https://chromium.googlesource.com/chromium/src/testing/libfuzzer/+/HEAD/efficient_fuzzer.md) while contains some chrome-specifics, is an excellent documentation on making your fuzzer better. |
| 19 | * [Guided in-process fuzzing of Chrome components](https://security.googleblog.com/2016/08/guided-in-process-fuzzing-of-chrome.html) |
| 20 | - Google Security Blog post describing the precursor work we've been doing in Chrome. |
| Mike Aizatsky | 3986fa3 | 2016-09-14 09:44:10 -0700 | [diff] [blame] | 21 | |
| Oliver Chang | a25bf35 | 2016-10-07 18:28:27 -0700 | [diff] [blame] | 22 | ## Build status |
| 23 | [Build status](https://oss-fuzz-build-logs.storage.googleapis.com/status.html) |
| 24 | |
| Mike Aizatsky | 2681964 | 2016-10-06 14:02:52 -0700 | [diff] [blame] | 25 | ## Bounties |
| 26 | |
| 27 | * freetype2: |
| 28 | [9](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9&can=1&q=&colspec=ID%20Type%20Component%20Status%20Priority%20Milestone%20Owner%20Summary), |
| Max Moroz | 539cbab | 2016-10-10 15:22:23 +0200 | [diff] [blame] | 29 | [10](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10&can=1&q=&colspec=ID%20Type%20Component%20Status%20Priority%20Milestone%20Owner%20Summary), |
| Mike Aizatsky | 2681964 | 2016-10-06 14:02:52 -0700 | [diff] [blame] | 30 | [36](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36&can=1&q=&colspec=ID%20Type%20Component%20Status%20Priority%20Milestone%20Owner%20Summary) |
| 31 | |
| 32 | |
| Mike Aizatsky | 3986fa3 | 2016-09-14 09:44:10 -0700 | [diff] [blame] | 33 | ## References |
| Kostya Serebryany | e751c6c | 2016-10-17 16:40:10 -0700 | [diff] [blame] | 34 | * [libFuzzer documentation](http://libfuzzer.info) |
| 35 | * [libFuzzer tutorial](http://tutorial.libfuzzer.info) |
| Mike Aizatsky | 4407d87 | 2016-10-19 10:52:02 -0700 | [diff] [blame] | 36 | * [Chromium Fuzzing Page](https://chromium.googlesource.com/chromium/src/testing/libfuzzer/) |
| Mike Aizatsky | 3986fa3 | 2016-09-14 09:44:10 -0700 | [diff] [blame] | 37 | |