* [infra] Fix reproduce command invoking run_fuzzer for a single testcase (#4338).
* review feedback
* do not introduce new variable, rely on SKIP_SEED_CORPUS only
* initial commit
* update build script, build failing
* add necessary environment variable definitions
* build working
* programmatically get system bits
* add md5 fuzzer
* fix style
* add fuzzers for two more hash functions
* testing dynamic includes
* build working
* clean up build script
* add aes fuzzer
* patch block_common to avoid build issues
* remove comments
* update patchfile location
* move patchfile again
* apply patch from subdirectory
* remove another comment
* change state type, use same data for encryption and decryption
* Build of nodejs has now been upstreamed and this commit simplifies the build for nodejs to the new updates.
* We only support libfuzzer for now.
* Simplified the build script.
Do this so that CIFuzz will work.
Co-authored-by: Zepeng Hu <zepenghu@google.com>
Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
* Get Sleuthkit building in the OSS-Fuzz builder.
* added fuzzers, included primary contact email, and updated build script
* included license headers
* fixed variable name typo in build script
* remove memory initialization in sleuthkit_mem_img.h
* style fixes, remove instances of goto
Co-authored-by: Ravi Jotwani <rjotwani@google.com>
Hopefully this should prevent OSS-Fuzz from reporting bugs that
have alread been fixed. Though I'm not sure how stable it's going to be
given that https://github.com/google/oss-fuzz/issues/4083 is still
open. Let's see.
* added draco integration files
* wrote build file and Dockerfile for Draco
* added more fuzzers, updated build script to generate corpus and options for each
* place yaml.dict in SRC first, rather than in OUT directly
* changed fuzzers from c++ to c, updated build script
* started using booleans instead of ints, updated naming conventions
* replaced all instances of with
* removed memsets, stopped using first two bytes of input, and removed file I/O
* fixed style, changed function return types to bool instead of int
* added libyaml_parser_fuzzer back, implemented string handling to not exceed buffer size in libyaml_emitter_fuzzer, and made style fixes
* changed boolean functions to return error, not success
* fixed inverted check
* changed variable names, fixed crash in libyaml_emitter_fuzzer
* fixed addition/subtraction style
* make a dynamically growing heap buffer
* place yaml_write_handler in distinct header file, style fixes
* fix style and memory safety issues in reformatter fuzzers, remove unused vars
* consistent assignment of done variables
* [CRAS] Fix build error and build new fuzzer
- Fix build error by installing 1.8.x gtest and using `make install` to
install gtest pc file for pkg-config
- Build and add new fuzzer `cras_hfp_slc`
BUG=oss-fuzz:24744
* fix the copyright
* fix the copyright
* Update Dockerfile
Co-authored-by: Max Moroz <mmoroz@chromium.org>
* Add bind9 as new proposed oss-fuzz target
* Add basic Dockerfile and build.sh
* Change the auto_cc addresses to @isc.org
* fix the copyright
* fix the copyright
Co-authored-by: Max Moroz <mmoroz@chromium.org>
* initial commit
* removed instances of cout in fuzzer, build failing
* Fix the Alembic build.
This commit gets Alembic building properly by linking it against
a locally compiled checkout of the most recent OpenEXR release.
* placed temp file in /tmp, modified build script
* added zlib1g-dev:i386 as a dependency in Dockerfile
* style fixes, removed msan
* combine dumpAttribute functions
* fix formatting
* update fuzzer_temp_file.h, style fixes for fuzzer
* populate target names
* disable ubsan for the time being
Co-authored-by: Michael Jezierny <mtjz@google.com>
jonathanmetzman