Skip to content

Commit b4ac719

Browse files
committed
_content/doc/security/fuzz: update OSS-Fuzz documentation
Replace outdated future reference with current information and link to OSS-Fuzz for continuous fuzzing setup. Signed-off-by: Julien Pivotto <[email protected]>
1 parent 3989c3b commit b4ac719

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

_content/doc/security/fuzz/index.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,8 +85,9 @@ issues that would already be caught by an existing test.
8585

8686
Note that it is up to you to decide how long to run fuzzing. It is very possible
8787
that an execution of fuzzing could run indefinitely if it doesn't find any errors.
88-
There will be support to run these fuzz tests continuously using tools like OSS-Fuzz
89-
in the future, see [Issue #50192](/issue/50192).
88+
You can run these fuzz tests continuously using tools like OSS-Fuzz. See
89+
[OSS-Fuzz](https://google.github.io/oss-fuzz/) for more information on setting up
90+
continuous fuzzing for your project.
9091

9192
**Note:** Fuzzing should be run on a platform that supports coverage
9293
instrumentation (currently AMD64 and ARM64) so that the corpus can meaningfully

0 commit comments

Comments
 (0)