suffix and pushing them to gcr.io/oss-fuzz-base.
This is useful for testing changes to images.
I used it to test changes I made for #6180.
This does not support msan as that image is being removed.
Also lint.
- Minor clarification about this using OSS-Fuzz's build chain. Be
consistent about calling this part OSS-Fuzz (rather than
ClusterFuzzLite), since that's what the image name says.
- Add project.yaml documentation.
- Refer to OSS-Fuzz's guide for efficient fuzzing.
Related: #6196
Removes unnecessary stuff in base-builder image to create a base-builder-new, and then adds a base-builder-swift on top of this that swift projects can use (without JVM/Go/etc fuzzing).
Recently the IF-MIB implementation on the Net-SNMP master branch became
dependent on libnl-route-3. An unfortunate side effect is that this broke
the build of the fuzz tests. Add the pkg-config package such that the
configure script can detect libnl-route-3 and reenable MIB-II and IF-MIB.
* Add Exiv2.
* Remove sanitizer flags so that OSS-Fuzz can insert its own.
* Using the fuzzer to create the seed corpus doesn't work with AFL.
* Only use libFuzzer
* Don't add files over 20KB to the corpus.
* Use ${LIB_FUZZING_ENGINE} when building the fuzz target.
The current way adds a lot of ordering assumptions, and doesn't fit too
well with parallel batch fuzzing either. Add a "upload-build" boolean action
input that can be added to "build_fuzzers" to upload latest builds
instead.
Builds are now uploaded by commit hash, rather than a fixed "latest" name.
ClusterFuzzLite's download_latest_build will check the last 3 commits and download the
first available build by git hash.
* Update fuzzers to new Atheris version
* Pin new atheris version
* Change = to ==
* Change path where Atheris fuzzers ld_preload from
* Update hypothesis fuzzer to work with new atheris
* Set version to 2.0.1
* Switch to Atheris 2.0.4
* Correct spelling of pygments_fuzzer decorator
* instrument yaml_reader
* Change to latest Atheris
* Set atheris version to 2.0.6
* nginx: request access
I would like to submit fuzzers to nginx and in this context having the coverage information from clusterfuzz would be great.
* nginx: add main_repo field
* initial attempt at fuzzing boost json with oss-fuzz
* use the boost super project master branch
* add mp11 to the list of checked out submodules
* remove leftover copy paste code
* use the boost json develop branch
* add vinnie
* add dmitry
This project is an implementation of Sparse Merkle tree, which will be
used by Celestia, Cosmos SDK, ... and maybe other blockchain ecosystem.
We want to make sure the code is fuzzed to catch highly impacted bug as
soon as possible.
See:
- https://github.com/celestiaorg
- https://docs.cosmos.network/v0.42/
* H3: Update for functions returning error codes
* Read H3 index directly from uint8_t data, not string
* remove new_str
* Fix pointer/int type confusion
* Revert h3NeighborRotations change that is not in master yet
* Fix h3NeighborRotations (again)
* wasmtime: provide OCaml packages for build
In order to build the WebAssembly spec interpreter, these packages are needed.
* wasmtime: remove ocamlbuild as a dependency
The oss-fuzz-base image is using Ubuntu 16.04.7 and the `ocaml-nox` package at this version contains `ocamlbuild`.
* tpm2-tss: update version of tpm simulator
Getting tpm simulator is failing occasionally [1].
Updating simulator version to the lastet might help it.
[1] https://oss-fuzz-build-logs.storage.googleapis.com/log-66fdad5b-1f63-4bc2-8a0e-876201912036.txt
Signed-off-by: Tadeusz Struk <tstruk@gmail.com>
* tpm2-tss: update outdated contact list
Signed-off-by: Tadeusz Struk <tstruk@gmail.com>
* tpm2-tss: add main_repo section
Signed-off-by: Tadeusz Struk <tstruk@gmail.com>
jonathanmetzman