From 8d6d825b9f228333ccc937f31cd25477838ff7ec Mon Sep 17 00:00:00 2001 From: DavidKorczynski Date: Wed, 3 Nov 2021 20:09:56 +0000 Subject: [PATCH] docs: remove statement on naming seed with sha1 values as it is no longer valid (#6754) --- docs/getting-started/new_project_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/new_project_guide.md b/docs/getting-started/new_project_guide.md index 7ac0d2ae0..6b3ae3223 100644 --- a/docs/getting-started/new_project_guide.md +++ b/docs/getting-started/new_project_guide.md @@ -416,7 +416,7 @@ target]({{ site.baseurl }}/reference/glossary/#fuzz-target)'s coverage. To provide a corpus for `my_fuzzer`, put `my_fuzzer_seed_corpus.zip` file next to the [fuzz target]({{ site.baseurl }}/reference/glossary/#fuzz-target)'s binary in `$OUT` during the build. Individual files in this -archive will be used as starting inputs for mutations. The name of each file in the corpus is the sha1 checksum (which you can get using the `sha1sum` or `shasum` command) of its contents. You can store the corpus +archive will be used as starting inputs for mutations. You can store the corpus next to source files, generate during build or fetch it using curl or any other tool of your choice. (example: [boringssl](https://github.com/google/oss-fuzz/blob/master/projects/boringssl/build.sh#L41)).