| /external/oss-fuzz/ |
| D | README.md | 1 # OSS-Fuzz: Continuous Fuzzing for Open Source Software
16 OSS-Fuzz aims to make common open source software more secure and stable by
32 Currently, OSS-Fuzz supports C/C++, Rust, Go, Python and Java/JVM code. Other languages
33 supported by [LLVM] may work too. OSS-Fuzz supports fuzzing x86_64 and i386
39 
42 Read our [detailed documentation] to learn how to use OSS-Fuzz.
47 As of January 2021, OSS-Fuzz has found over [25,000] bugs in [375] open source
54 * 2016-12-01 - [Announcing OSS-Fuzz: Continuous fuzzing for open source software]
55 * 2017-05-08 - [OSS-Fuzz: Five months later, and rewarding projects]
56 * 2018-11-06 - [A New Chapter for OSS-Fuzz]
[all …]
|
| D | METADATA | 1 name: "OSS-Fuzz"
2 description: "OSS-Fuzz: Continuous Fuzzing for Open Source Software"
|
| /external/oss-fuzz/docs/oss-fuzz/ |
| D | architecture.md | 6 parent: OSS-Fuzz
10 
18 1. The project is [accepted to OSS-Fuzz]({{ site.baseurl }}/getting-started/accepting-new-projects/…
19 1. The OSS-Fuzz [builder](jenkins.io) builds the project from the committed configs.
20 1. The builder uploads the fuzz targets to the OSS-Fuzz GCS bucket.
23 bug, it reports the issue automatically to the OSS-Fuzz
28 1. The project developer fixes the bug upstream and credits OSS-Fuzz for the
29 discovery (the commit message should contain the string **'Credit to OSS-Fuzz'**).
|
| /external/oss-fuzz/docs/getting-started/new-project-guide/ |
| D | bazel.md | 20 build system with OSS-Fuzz is very similar to the general
35 test artifacts in the OSS-Fuzz format. Each `//path/to:fuzz_test` fuzz test
38 in the OSS-Fuzz environment variables, and (b) generates an archive containing
40 OSS-Fuzz provides a standard tool to automatically process these targets,
48 `rules_fuzzing` library with OSS-Fuzz. You can also see a complete example in the
52 The structure of the project directory in the OSS-Fuzz repository does not
60 Since the OSS-Fuzz target builds the fuzz test using the instrumentation and
61 engine specified in the OSS-Fuzz environment variables, all the engine and
67 There is no need to install Bazel in your Docker image. The OSS-Fuzz builder
78 which fuzz tests to build, (2) building their OSS-Fuzz package targets in the
[all …]
|
| D | rust_lang.md | 17 The process of integrating a project written in Rust with OSS-Fuzz is very
24 Rust integration with OSS-Fuzz is expected to use [`cargo
27 correct libFuzzer on OSS-Fuzz itself. Note that using `cargo fuzz` also makes it
38 compiled and run on OSS-Fuzz.
41 the scripts below to integrate into OSS-Fuzz.
64 The OSS-Fuzz builder image has the latest nightly release of Rust as well as
93 automatically integrated into OSS-Fuzz:
|
| D | python_lang.md | 18 The process of integrating a project written in Python with OSS-Fuzz is very
25 Python fuzzing in OSS-Fuzz depends on
27 `atheris` package, and dependencies are pre-installed on the OSS-Fuzz base
82 # over time on the OSS-Fuzz bots, we use pyinstaller to create a standalone
84 # required to keep fuzzers working properly in OSS-Fuzz.
89 # test case reproduction. Since this helper script is what OSS-Fuzz will
127 To use Hypothesis in OSS-Fuzz, install it in your Dockerfile with
135 or run with OSS-Fuzz as a fuzz harness.
|
| D | go_lang.md | 17 The process of integrating a project written in Go with OSS-Fuzz is very similar
24 OSS-Fuzz supports **go-fuzz** in the
37 The structure of the project directory in OSS-Fuzz repository doesn't differ for
62 The OSS-Fuzz builder image has the latest stable release of Golang installed. In
|
| /external/oss-fuzz/docs/ |
| D | index.md | 3 title: OSS-Fuzz
10 # OSS-Fuzz
25 OSS-Fuzz aims to make common open source software more secure and stable by
41 Currently, OSS-Fuzz supports C/C++, Rust, Go, Python and Java/JVM code. Other
42 languages supported by [LLVM] may work too. OSS-Fuzz supports fuzzing x86_64
49 This documentation describes how to use OSS-Fuzz service for your open source
59 As of January 2021, OSS-Fuzz has found over [25,000] bugs in [375] open source
|
| D | faq.md | 51 `projects/<your_project>` directory in the OSS-Fuzz repository. Note that we do
55 ## My project is not open source. Can I use OSS-Fuzz?
57 You cannot use OSS-Fuzz, but you can use [ClusterFuzz] which OSS-Fuzz is based
61 OSS-Fuzz is a production instance of ClusterFuzz, plus the code living in
62 [OSS-Fuzz repository]: build scripts, `project.yaml` files with contacts, etc.
64 [OSS-Fuzz repository]: https://github.com/google/oss-fuzz
66 …ssue tracker](https://bugs.chromium.org/p/oss-fuzz/issues/list) for reporting bugs in OSS projects?
68 Security access control is important for the kind of issues that OSS-Fuzz detects.
131 is maintained in OSS-Fuzz, you can search for contacts in the respective
186 ## Does OSS-Fuzz support AFL or honggfuzz?
[all …]
|
| /external/oss-fuzz/docs/getting-started/ |
| D | integration_rewards.md | 12 is successfully integrated with OSS-Fuzz. Please see the details in our blog post
15 Rewards are based on the quality of integration with OSS-Fuzz, which is evaluated using
19 * Regression testing in the upstream repository using fuzz targets and OSS-Fuzz corpora.
24 For each of the points above, the OSS-Fuzz rewards panel first sets up a cap of up to $5,000.
|
| D | continuous_integration.md | 11 OSS-Fuzz offers **CIFuzz**, a GitHub action/CI job that runs your fuzz targets
26 * If the crash does not occur on older OSS-Fuzz builds. Because if it does occur
30 If your project supports [OSS-Fuzz's code coverage]({{ site.baseurl }}/advanced-topics/code-coverag…
35 CIFuzz uses 30 day old/public regressions and corpora from OSS-Fuzz. This makes
40 1. Your project must be integrated with OSS-Fuzz.
49 file over from the OSS-Fuzz repository to the `workflows` directory.
50 …ain.yml` from `example` to the name of your OSS-Fuzz project. It is **very important** that you us…
51 …in the [`projects`](https://github.com/google/oss-fuzz/tree/master/projects) directory of OSS-Fuzz.
113 limit for broken fuzz targets than OSS-Fuzz's check_build. Most users should
202 You can checkout CIFuzz configs for OSS-Fuzz projects. Example -
[all …]
|
| /external/tensorflow/tensorflow/lite/micro/examples/person_detection/ |
| D | BUILD | 28 "no_oss", # TODO(b/174680668): Exclude from OSS.
43 "no_oss", # TODO(b/174680668): Exclude from OSS.
54 "no_oss", # TODO(b/174680668): Exclude from OSS.
131 "no_oss", # TODO(b/174680668): Exclude from OSS.
|
| /external/llvm-project/llvm/lib/Support/ |
| D | LockFileManager.cpp | 228 raw_string_ostream OSS(S); in LockFileManager() local
229 OSS << LockFileName.str() << " to " << UniqueLockFileName.str(); in LockFileManager()
230 setError(EC, OSS.str()); in LockFileManager()
273 raw_string_ostream OSS(Str); in getErrorMessage() local
275 OSS << ": " << ErrCodeMsg; in getErrorMessage()
276 return OSS.str(); in getErrorMessage()
|
| /external/swiftshader/third_party/llvm-10.0/llvm/lib/Support/ |
| D | LockFileManager.cpp | 228 raw_string_ostream OSS(S); in LockFileManager() local
229 OSS << LockFileName.str() << " to " << UniqueLockFileName.str(); in LockFileManager()
230 setError(EC, OSS.str()); in LockFileManager()
273 raw_string_ostream OSS(Str); in getErrorMessage() local
275 OSS << ": " << ErrCodeMsg; in getErrorMessage()
276 return OSS.str(); in getErrorMessage()
|
| /external/llvm/lib/Support/ |
| D | LockFileManager.cpp | 216 raw_string_ostream OSS(S); in LockFileManager() local
217 OSS << LockFileName.str() << " to " << UniqueLockFileName.str(); in LockFileManager()
218 setError(EC, OSS.str()); in LockFileManager()
261 raw_string_ostream OSS(Str); in getErrorMessage() local
263 OSS << ": " << Error->message(); in getErrorMessage()
264 OSS.flush(); in getErrorMessage()
|
| /external/python/cpython2/Doc/library/ |
| D | ossaudiodev.rst | 2 :mod:`ossaudiodev` --- Access to OSS-compatible audio devices
7 :synopsis: Access to OSS-compatible audio devices.
12 This module allows you to access the OSS (Open Sound System) audio interface.
13 OSS is available for a wide range of open-source and commercial Unices, and is
18 use ALSA, you'll have to make sure its OSS compatibility layer
25 > Likewise, googling shows OpenBSD also uses OSS/Free -- the commercial
26 > OSS installation manual tells you to remove references to OSS/Free from the
32 > * This is an OSS (Linux) audio emulator.
48 the official documentation for the OSS C API
50 The module defines a large number of constants supplied by the OSS device
[all …]
|
| /external/python/cpython3/Doc/library/ |
| D | ossaudiodev.rst | 1 :mod:`ossaudiodev` --- Access to OSS-compatible audio devices
6 :synopsis: Access to OSS-compatible audio devices.
10 This module allows you to access the OSS (Open Sound System) audio interface.
11 OSS is available for a wide range of open-source and commercial Unices, and is
16 use ALSA, you'll have to make sure its OSS compatibility layer
23 > Likewise, googling shows OpenBSD also uses OSS/Free -- the commercial
24 > OSS installation manual tells you to remove references to OSS/Free from the
30 > * This is an OSS (Linux) audio emulator.
50 the official documentation for the OSS C API
52 The module defines a large number of constants supplied by the OSS device
[all …]
|
| /external/oss-fuzz/docs/advanced-topics/ |
| D | ideal_integration.md | 9 # Ideal integration with OSS-Fuzz
12 OSS projects have different build and test systems. We can't expect them all to
13 implement and maintain fuzz targets or integrate them with OSS-Fuzz in the same
69 Many different build systems exist in the open-source world. The less OSS-Fuzz
72 An ideal build integration for OSS-Fuzz looks like this:
77 …env var [provided]({{ site.baseurl }}/getting-started/new-project-guide/) by OSS-Fuzz environment).
87 This minimizes OSS-Fuzz-specific configuration, making your fuzzing more robust.
101 For better OSS-Fuzz integration, the seed corpus should be available in
162 In such cases, we can host the fuzz targets, dictionaries, etc. in OSS-Fuzz's
170 bugs found by OSS-Fuzz.
|
| /external/tensorflow/tensorflow/compiler/xla/ |
| D | xla.bzl | 4 # Note: we don't currently define a proto library target for Python in OSS.
9 # Note: we don't currently define any special targets for Python GRPC in OSS.
|
| /external/tensorflow/tensorflow/lite/micro/examples/image_recognition_experimental/ |
| D | BUILD | 20 "no_oss", # TODO(b/174680668): Exclude from OSS.
28 "no_oss", # TODO(b/174680668): Exclude from OSS.
|
| /external/oss-fuzz/docs/reference/ |
| D | useful_links.md | 26 * 2016-12-01 - Announcing OSS-Fuzz: Continuous fuzzing for open source software
30 * 2017-05-08 - OSS-Fuzz: Five months later, and rewarding projects
34 * 2018-11-06 - A New Chapter for OSS-Fuzz
|
| D | glossary.md | 20 ## OSS-Fuzz specific terms
24 A scalable fuzzing infrastructure that is used for OSS-Fuzz backend.
35 in OSS-Fuzz a fuzz target can be used to
55 A project is an open source software project that is integrated with OSS-Fuzz.
|
| /external/tensorflow/tensorflow/security/fuzzing/ |
| D | BUILD | 153 tags = ["notap"], # Run in OSS only.
159 tags = ["notap"], # Run in OSS only.
166 tags = ["notap"], # Run in OSS only.
|
| /external/llvm-project/llvm/test/CodeGen/X86/ |
| D | pr46004.ll | 5 ; OSS Fuzz: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22357
23 ; OSS Fuzz: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22723
|
| /external/tpm2-tss/doc/ |
| D | fuzzing.md | 64 ## OSS Fuzz
66 OSS fuzz integration can be found under the
68 project in OSS Fuzz.
|