aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* Migrate projects using -lFuzzingEngine to $LIB_FUZZING_ENGINE (#2325)Gravatar jonathanmetzman2019-05-01
| | | Migrate from -lFuzzingEngine to $LIB_FUZZING_ENGINE where possible and not causing breakage
* [cras] Modify accounts to auto-cc (#2360)Gravatar CY Chiang2019-05-01
| | | Modify accounts for CRAS team member changes.
* Migrate projects with trouble with exceptions to $LIB_FUZZING_ENGINE (#2359)Gravatar jonathanmetzman2019-04-30
| | | | Migrate projects that broke libFuzzer with exceptions to $LIB_FUZZING_ENGINE. Replace uses of -lFuzzingEngine with `$LIB_FUZZING_ENGINE`
* Roll clang to r359254 (#2358)Gravatar jonathanmetzman2019-04-30
| | | Roll clang to r359254 to uptake fixes for exception handling and MSAN.
* Revert "[infra] Revert the recent clang roll to fix some builds (#2315) ↵Gravatar jonathanmetzman2019-04-29
| | | | | | | | (#2316) (#2356) * Revert "[infra] Revert the recent clang roll to fix some builds (#2315). (#2316)" This reverts commit 8b34fd89d24551a2268099a6213a6152922cb601.
* Disable unrar project due to file creation spam (#2355)Gravatar Abhishek Arya2019-04-29
|
* [llvm] Switch to LIB_FUZZING_ENGINE. (#2352)Gravatar Matt Morehouse2019-04-29
|
* [bignum-fuzzer] Fix OpenSSL build (#2354)Gravatar Guido Vranken2019-04-28
| | | Temporary workaround for OpenSSL's build system problems.
* envoy: remove UBSAN blacklist. (#2351)Gravatar htuch2019-04-26
| | | | | | | This is no longer needed as we handle this Envoy-side. This should fix the build that has been broken since https://github.com/envoyproxy/envoy/pull/6610. Signed-off-by: Harvey Tuch <htuch@google.com>
* Custom patch for libpcap to avoid infinite loop (#2344)Gravatar Catena cyber2019-04-24
|
* [libtorrent] update libtorrent project to just pull the main repository and ↵Gravatar Arvid Norberg2019-04-22
| | | | build fuzzers from there (as they recently landed in the release branch) (#2339)
* use immutable default arguments (#2341)Gravatar jonathanmetzman2019-04-22
|
* Prevent misuse of check_build (#2340)Gravatar jonathanmetzman2019-04-22
| | | Don't allow using check_build with builds it doesn't actually support.
* Fix build - option got renamed to --without-libxml (#2338)Gravatar Stanislav Malyshev2019-04-20
|
* Cryptofuzz fixes (#2337)Gravatar Guido Vranken2019-04-18
| | | | | | | | | | | | | | | * [cryptofuzz] Use latest OpenSSL version This is a workaround for an issue OpenSSL's build system is currently having. I've appended || true to the build command so failure is not signaled to the Docker process running the build script, and the build is not aborted. Multithreaded compiling has been removed temporarily to avoid a race condition that causes the make procedure to abort before libcrypto.a has been compiled. * [cryptofuzz] Build against LIB_FUZZING_ENGINE_DEPRECATED to prevent crashes
* Fixes capstone build (#2335)Gravatar Catena cyber2019-04-18
| | | Uses a newly compiled file for next branch only
* [zstd] Move downloading seed corpora to build.sh (#2331)Gravatar Nick Terrell2019-04-17
| | | | | | I just added a new fuzzer, `zstd_frame_info`, and want to be able to add new fuzzers without submitting a pull request to oss-fuzz. This change uses zstd's Makefile to download the corpora. Now I can add a new fuzzer to zstd and it will automatically get built and download the seed corpus in oss-fuzz.
* Cryptofuzz (differential crypto fuzzing) (#2273)Gravatar Guido Vranken2019-04-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add cryptofuzz * [cryptofuzz] Specify sanitizers * [cryptofuzz] Actually disable assembly in second OpenSSL build * [cryptofuzz] Add BoringSSL * [cryptofuzz] Enable MemorySanitizer builds * [cryptofuzz] Fix OpenSSL build * [cryptofuzz] Add LibreSSL target * [cryptofuzz] Don't build LibreSSL if MemorySanitizer is enabled * [cryptofuzz] Adapt build script to latest cryptofuzz code * [cryptofuzz] Force rebuild of OpenSSL * [cryptofuzz] Comment and move to Dockerfile OpenSSL's commit lock * [cryptofuzz] BoringSSL, LibreSSL: only build libcrypto.a for faster builds * [cryptofuzz] Replace -lFuzzingEngine -> $LIB_FUZZING_ENGINE for compatibility with OSS-Fuzz' new build setup * [cryptofuzz] Add README.md
* [graphicsmagick] Added --time flag to clone (#2333)Gravatar Alex Gaynor2019-04-17
| | | This will give us more information if the clone fails (which it does sometimes, probably due to sourceforge infra issues)
* [lwan] Use HTTP dictionary to speed up fuzzing (#2329)Gravatar Leandro A. F. Pereira2019-04-17
|
* [kimageformats] Split fuzzer into 9 fuzzers (#2327)Gravatar tsdgeos2019-04-16
| | | oss-fuzz devels say this is optimal
* Update patch to fix build and migrate to -fsanitize=fuzzer (#2324)Gravatar jonathanmetzman2019-04-16
| | | | Update skia.diff to fix build breakage. Also, use $LIB_FUZZING_ENGINE instead of -lFuzzingEngine to start using -fsanitize=fuzzer
* [karchive] New project: karchive (#2318)Gravatar tsdgeos2019-04-15
|
* [libxslt] Update project.yaml: replace Chromium owner in auto_cc.Gravatar Max Moroz2019-04-15
|
* [libxslt] Start with integration (#2320)Gravatar Nick Wellnhofer2019-04-15
| | | Integrate the first fuzz targets from libxslt.
* [libical] Make sure to do an apt update before apt install (#2319)Gravatar Alex Gaynor2019-04-15
|
* Change LIB_FUZZING_ENGINE to -fsanitize=fuzzer in libFuzzer builds (#2312)Gravatar jonathanmetzman2019-04-15
|
* [infra] Revert the recent clang roll to fix some builds (#2315). (#2316)Gravatar Max Moroz2019-04-12
|
* Build clang so that it can compile targets with `-fsanitize=fuzzer` (#2311)Gravatar jonathanmetzman2019-04-11
| | | | Build clang so that it can compile targets with -fsanitize=fuzzer without adding any runtime dependencies.
* [zstd] Add fuzzers and cc emails (#2309)Gravatar Nick Terrell2019-04-10
| | | | | | | | * [zstd] Add seed corpora for two new fuzzers * [zstd] Add two more emails to cc list It is helpful to add in the corporate email so we don't miss bugs.
* libical: Fix undefined sanitizer not building (#2308)Gravatar tsdgeos2019-04-10
| | | | The cmake option for disabling shared libs was not the correct one and the compilation was getting confused
* Updates for OpenSSH fuzzing (#2306)Gravatar Damien Miller2019-04-10
| | | | | | * Enable experimental XMSS keys for fuzzing * Enable auth options fuzzer
* [lwan] Add fuzzing targets for Lwan (#2302)Gravatar Leandro A. F. Pereira2019-04-09
|
* Disable UBSan for libical (#2298)Gravatar Abhishek Arya2019-04-09
|
* Add libical (#2298)Gravatar tsdgeos2019-04-09
|
* Libtorrent take2 (#2299)Gravatar Paul Dreik2019-04-09
| | | | | | | | | | | | | | | | | | | | | * switch to another fuzzer repo aimed to be merged upstream * update email addresses checked with arvid, he approved adding his address * [libtorrent] improve building - use ninja - don't build tests - respect CXXFLAGS when building boost - less verbose output when downloading * create initial corpus zip files from git this makes it much easier to add and remove both fuzzers and corpus upstream and make sure they work well.
* [libpng-proto] remove stale commentGravatar Kostya Serebryany2019-04-09
|
* [libpng-proto] add asan backGravatar Kostya Serebryany2019-04-09
|
* Revert "Remove mbed TLS fuzzer (#2278)" (#2304)Gravatar Abhishek Arya2019-04-09
| | | This reverts commit cce2ed4d23eb65251c0cd6b44cc666d91c883803.
* [infra] Enabling DataFlow build configuration (#1632). (#2292)Gravatar Max Moroz2019-04-09
| | | | | | * [infra] Enabling DataFlow build configuration (#1632). * Copy all data flow scripts from the libFuzzer repo.
* Update project.yamlGravatar Oliver Chang2019-04-09
|
* [llvm] Remove proto fuzzers. (#2301)Gravatar Matt Morehouse2019-04-08
| | | | | Proto fuzzers are slow and haven't found bugs in a long time. Their builds are also hard to maintain since they build in a different configuration than any of the LLVM build bots.
* [bignum-fuzzer] Fix OpenSSL build (#2296)Gravatar Guido Vranken2019-04-06
|
* [mupdf] Update to latest version of API provided by MuPDF. (#2294)Gravatar Sebastian Rasmussen2019-04-05
|
* [TensorFlow] Ensure we're always using a valid Bazel (#2293)Gravatar Mihai Maruseac2019-04-04
| | | | | | | | | | | | * Determine Bazel version from configure.py script * Install Bazel at the version from configure.py * Don't downgrade Bazel on Dockerfile * Make sure we were able to install proper Bazel * Comment update
* [zlib] Fix build.sh to overwrite seed corpus symlinks.Gravatar Max Moroz2019-04-04
|
* Fix build breakage caused by unnecessary AFL testing (#2291)Gravatar jonathanmetzman2019-04-04
| | | | Don't test compilation with afl-clang and afl-fuzz
* [tensorflow] Update Bazel version and check that it is compatible (#2288)Gravatar Mihai Maruseac2019-04-03
| | | | | | * Update Bazel to 0.24.0 * Always run ./configure
* Address comments from https://github.com/google/oss-fuzz/pull/2285. (#2287)Gravatar Oliver Chang2019-04-03
|
* [libtorrent] add address for google account (#2286)Gravatar Paul Dreik2019-04-02
| | | see https://github.com/google/oss-fuzz/issues/2261#issuecomment-479085906
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-06 01:04:22 +0000