Rooba
/
oss-fuzz
mirror of https://github.com/google/oss-fuzz.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update ideal_integration.md

This commit is contained in:
Kostya Serebryany 2016-11-18 15:30:46 -08:00 committed by GitHub
parent da9d0ce53a
commit 395fdc9b28
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/ideal_integration.md
View File

@ -91,11 +91,11 @@ a) may change and b) are different depending on the fuzzing target and the sanit
## Not a project member? ## Not a project member?
If you are a member of the project you want to fuzz, most of the steps above are simple. If you are a member of the project you want to fuzz, most of the steps above are simple.
However in some cases someone outside the project team may want to fuzz the code. However in some cases someone outside the project team may want to fuzz the code
If so, and the project members are not interested in coopearation, the easiest is to create a and the project maintainers are not interested in helping.
separate GitHub project with the fuzz target, corpus, dictionary, etc.
In simple cases we can even host the fuzz target in this repository In such cases we can host the fuzz targets, dictionaries, etc in this repository.
(examples: [libxml2](../targets/libxml2), [c-ares](../targets/c-ares), [expat](../targets/expat)), Examples: [libxml2](../targets/libxml2), [c-ares](../targets/c-ares), [expat](../targets/expat).
but this is the pattern we **strongly discourage**
because it is harder to maintain and is not tied to the project's continuos integration testing. Please note that if you are not the project maintainer
we may not be able to CC you to security bugs found by OSS-Fuzz.