960cc7d793
[librawspeed] LIB_FUZZING_ENGINE fixes ( #2317 ) ( #2377 )
...
* [librawspeed] LIB_FUZZING_ENGINE fixes
Depends on 8906ca4a40https://github.com/google/oss-fuzz/issues/2317
* [librawspeed] Drop dead CMake WITH_PTHREADS param
It is gone from RawSpeed's CMake, there is no longer any direct
dependecy on PThreads.
2019-05-03 11:28:58 -07:00
ab3cede757
Update project.yaml
2019-05-03 07:18:39 -07:00
dde14d4709
update libtorrent build script to only build and expose large fuzz targets ( #2376 )
2019-05-03 07:09:54 -07:00
7d2884aaea
[unrar] Re-enable fuzzing by creating/clearing a temporary directory ( #2368 )
2019-05-02 11:32:32 -07:00
a9c4e0fa07
[s2opc] Address review comments ( #2348 ).
2019-05-02 11:24:41 -07:00
18b9c57f4e
[s2opc] Add build scripts ( #2348 )
2019-05-02 10:54:18 -07:00
acb1bae5b4
[unicorn][libpcap] Try using -lFuzzingEngine to fix MSAN issue ( #2370 )
2019-05-01 21:09:40 -04:00
bbd509dca4
Speculative fix for yajl migration: Reorder arguments ( #2366 )
...
Use $LIB_FUZZING_ENGINE before -x c which causes all subsequent files to be treated as C source,
including libFuzzingEngine.a during AFL builds.
2019-05-01 16:58:41 -04:00
f6be0078df
Try to migrate yajl-ruby and libxslt to LIB_FUZZING_ENGINE ( #2365 )
2019-05-01 16:11:29 -04:00
27240f86f5
[mupdf] Update to latest version of API provided by MuPDF. ( #2362 )
...
This reverts commit 7fa021dfbe
2019-05-01 15:47:53 -04:00
60a23d3841
[gfwx] Add gfwx fuzzers ( #2346 )
...
* [gfwx] Add gfwx fuzzers
* [gfwx] Update maintainer fields to GFWX maintainer address
2019-05-01 10:42:18 -07:00
5217d8efb4
[qpid-proton] Undo change to comment during migration ( #2361 )
2019-05-01 12:14:33 -04:00
3049c50d48
Migrate projects using -lFuzzingEngine to $LIB_FUZZING_ENGINE ( #2325 )
...
Migrate from -lFuzzingEngine to $LIB_FUZZING_ENGINE where possible and not causing breakage
2019-05-01 11:09:55 -04:00
22f5e3e0b8
[cras] Modify accounts to auto-cc ( #2360 )
...
Modify accounts for CRAS team member changes.
2019-05-01 07:31:13 -07:00
7553ee876d
Migrate projects with trouble with exceptions to $LIB_FUZZING_ENGINE ( #2359 )
...
Migrate projects that broke libFuzzer with exceptions to $LIB_FUZZING_ENGINE.
Replace uses of -lFuzzingEngine with `$LIB_FUZZING_ENGINE`
2019-04-30 16:48:34 -04:00
c1c6ea69a0
Disable unrar project due to file creation spam ( #2355 )
2019-04-29 09:18:52 -07:00
e7b479a8cc
[llvm] Switch to LIB_FUZZING_ENGINE. ( #2352 )
2019-04-29 10:35:29 -04:00
4caafd5aa1
[bignum-fuzzer] Fix OpenSSL build ( #2354 )
...
Temporary workaround for OpenSSL's build system problems.
2019-04-28 17:19:25 -07:00
bf05a80651
envoy: remove UBSAN blacklist. ( #2351 )
...
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>
2019-04-26 09:58:44 -07:00
1e88b4f948
Custom patch for libpcap to avoid infinite loop ( #2344 )
2019-04-24 09:16:10 -07:00
50d08b7d7c
[libtorrent] update libtorrent project to just pull the main repository and build fuzzers from there (as they recently landed in the release branch) ( #2339 )
2019-04-22 15:53:44 -07:00
30190987f4
Fix build - option got renamed to --without-libxml ( #2338 )
2019-04-20 22:26:16 -07:00
1ea634a278
Cryptofuzz fixes ( #2337 )
...
* [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
2019-04-18 13:07:09 -07:00
028c9c486a
Fixes capstone build ( #2335 )
...
Uses a newly compiled file for next branch only
2019-04-18 08:16:58 -07:00
fb7075b1ed
[zstd] Move downloading seed corpora to build.sh ( #2331 )
...
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.
2019-04-17 21:42:41 -07:00
7bdfb2b7d8
Cryptofuzz (differential crypto fuzzing) ( #2273 )
...
* 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
2019-04-17 20:33:50 -07:00
7b8971290d
[graphicsmagick] Added --time flag to clone ( #2333 )
...
This will give us more information if the clone fails (which it does sometimes, probably due to sourceforge infra issues)
2019-04-17 14:21:54 -07:00
c416a8007b
[lwan] Use HTTP dictionary to speed up fuzzing ( #2329 )
2019-04-17 08:28:57 -07:00
0221e8b030
[kimageformats] Split fuzzer into 9 fuzzers ( #2327 )
...
oss-fuzz devels say this is optimal
2019-04-16 15:40:48 -07:00
53c09d30f6
Update patch to fix build and migrate to -fsanitize=fuzzer ( #2324 )
...
Update skia.diff to fix build breakage.
Also, use $LIB_FUZZING_ENGINE instead of -lFuzzingEngine to start using -fsanitize=fuzzer
2019-04-16 11:52:23 -07:00
d2f7690886
[karchive] New project: karchive ( #2318 )
2019-04-15 14:20:24 -07:00
4fba752cc3
[libxslt] Update project.yaml: replace Chromium owner in auto_cc.
2019-04-15 11:08:34 -07:00
8af165e494
[libxslt] Start with integration ( #2320 )
...
Integrate the first fuzz targets from libxslt.
2019-04-15 10:27:43 -07:00
7c05d15480
[libical] Make sure to do an apt update before apt install ( #2319 )
2019-04-15 10:11:25 -07:00
ae9398deef
Change LIB_FUZZING_ENGINE to -fsanitize=fuzzer in libFuzzer builds ( #2312 )
2019-04-15 10:05:02 -07:00
3eaad4f3e2
[zstd] Add fuzzers and cc emails ( #2309 )
...
* [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.
2019-04-10 13:35:20 -07:00
36005daba0
libical: Fix undefined sanitizer not building ( #2308 )
...
The cmake option for disabling shared libs was not the correct one
and the compilation was getting confused
2019-04-10 11:23:34 -07:00
2b49be2eaa
Updates for OpenSSH fuzzing ( #2306 )
...
* Enable experimental XMSS keys for fuzzing
* Enable auth options fuzzer
2019-04-10 13:31:45 +10:00
935e25b1ff
[lwan] Add fuzzing targets for Lwan ( #2302 )
2019-04-09 13:54:01 -07:00
c4fe1fef9e
Disable UBSan for libical ( #2298 )
2019-04-09 11:46:33 -07:00
e445a90d94
Add libical ( #2298 )
2019-04-09 11:23:05 -07:00
676071636c
Libtorrent take2 ( #2299 )
...
* 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.
2019-04-09 11:22:07 -07:00
08af8b64ad
[libpng-proto] remove stale comment
2019-04-09 11:01:58 -07:00
663d09feb2
[libpng-proto] add asan back
2019-04-09 10:57:09 -07:00
2e3212d8f0
Revert "Remove mbed TLS fuzzer ( #2278 )" ( #2304 )
...
This reverts commit cce2ed4d23
2019-04-09 09:07:55 -07:00
5c5a10a16d
Update project.yaml
2019-04-09 10:47:13 +10:00
6c3880cfd5
[llvm] Remove proto fuzzers. ( #2301 )
...
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.
2019-04-08 12:30:36 -07:00
eb2795c830
[bignum-fuzzer] Fix OpenSSL build ( #2296 )
2019-04-06 07:28:40 -07:00
7fa021dfbe
[mupdf] Update to latest version of API provided by MuPDF. ( #2294 )
2019-04-05 12:16:43 -07:00
922ea7c8fe
[TensorFlow] Ensure we're always using a valid Bazel ( #2293 )
...
* 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
2019-04-04 23:35:11 -07:00
Roman Lebedev