| commit | 69400fb24bf11cc5c4479962a3e12103e880a848 | [log] [tgz] |
|---|---|---|
| author | Oliver Chang <oliverchang@users.noreply.github.com> | Tue Jul 27 10:46:20 2021 +1000 |
| committer | GitHub <noreply@github.com> | Tue Jul 27 10:46:20 2021 +1000 |
| tree | ad7f617ba1b72b2de950024212ec42a6fb79ba8c | |
| parent | 7c3f3ddc2b8c5a31fe4d3e4f8254a6b398660955 [diff] |
Add a Git backed filestore. (#6088) - Add storage-repo, storage-repo-branch, and storage-repo-branch-coverage fields to the actions, to indicate that the Git filestore should be used. - The CI provided filestore is still used for crashes and builds. - Replace generic Filestore.upload_directory with typed upload methods which matches the download methods. - Rename upload_latest_build to upload_build to make it more generic. - Make artifact name prefixes an implementation detail of the store. For #6052.
Fuzz testing is a well-known technique for uncovering programming errors in software. Many of these detectable errors, like buffer overflow, can have serious security implications. Google has found thousands of security vulnerabilities and stability bugs by deploying guided in-process fuzzing of Chrome components, and we now want to share that service with the open source community.
In cooperation with the Core Infrastructure Initiative and the OpenSSF, OSS-Fuzz aims to make common open source software more secure and stable by combining modern fuzzing techniques with scalable, distributed execution.
We support the libFuzzer, AFL++, and Honggfuzz fuzzing engines in combination with Sanitizers, as well as ClusterFuzz, a distributed fuzzer execution environment and reporting tool.
Currently, OSS-Fuzz supports C/C++, Rust, Go, Python and Java/JVM code. Other languages supported by LLVM may work too. OSS-Fuzz supports fuzzing x86_64 and i386 builds.
Read our detailed documentation to learn how to use OSS-Fuzz.
As of June 2021, OSS-Fuzz has found over 30,000 bugs in 500 open source projects.