diff options
author | Abhishek Arya <inferno@chromium.org> | 2019-08-15 16:33:07 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-08-15 16:33:07 -0700 |
commit | 65e0da812b9dfa1cefd1fd004b27d730df530882 (patch) | |
tree | 18820b58b23d82f8ae125a09f937d3474189d91e /docs/getting-started/new_project_guide.md | |
parent | 305e047e71b29db0d01f170892fb04aba03c2f8a (diff) | |
download | oss-fuzz-65e0da812b9dfa1cefd1fd004b27d730df530882.tar.gz |
Update new_project_guide.md (#2709)
Diffstat (limited to 'docs/getting-started/new_project_guide.md')
-rw-r--r-- | docs/getting-started/new_project_guide.md | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/getting-started/new_project_guide.md b/docs/getting-started/new_project_guide.md index 53854e510..61bc6ae0d 100644 --- a/docs/getting-started/new_project_guide.md +++ b/docs/getting-started/new_project_guide.md @@ -323,11 +323,10 @@ to reuse the same dictionary if they are fuzzing very similar inputs. ### Input Size By default, the fuzzing engine will generate input of any arbitrary length. -This is often useful to try unexpected use cases that lead to security -vulnerabilities. However, if your API does not expect large inputs and will -fail on parsing early-on, it is important to add those limits in your fuzz target -to avoid those errors altogether. This can also lead to significant performance -improvements. +This might be useful to try corner cases that could lead to a +security vulnerability. However, if large inputs are not necessary to +increase the coverage of your target API, it is important to add a limit +here to significantly improve performance. ```cpp if (size < kMinInputLength || size > kMaxInputLength) |