From 65e0da812b9dfa1cefd1fd004b27d730df530882 Mon Sep 17 00:00:00 2001 From: Abhishek Arya Date: Thu, 15 Aug 2019 16:33:07 -0700 Subject: Update new_project_guide.md (#2709) --- docs/getting-started/new_project_guide.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'docs/getting-started/new_project_guide.md') 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) -- cgit v1.2.3