| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
Update Mosh’s build.sh to pass appropriate configure options when
coverage is requested, as well as to pass CXXFLAGS through to the
actual build. These fix ClusterFuzz code coverage reports.
Along the way, enable verbose build rules, since they’re useful for
debugging build failures.
|
| |
|
|
|
|
| |
Ref:
https://github.com/googleapis/google-auth-library-python/issues/1082#issuecomment-1188384851
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due to upstream changes, the Git fuzzers must now link against
common-main.o; however, this breaks the build in two ways:
1) Linking with common-main.o causes main() to have multiple
definitions, one in common-main.o and one from the fuzzing engine.
2) To avoid #1, the Git Makefile specifically excludes common-main.o
from the fuzzer build rule.
To work around these issues, we can override FUZZ_CXXFLAGS (add
"-Wl,--allow-multiple-definition" to fix #1) and LIB_FUZZING_ENGINE (add
"common-main.o" to fix #2).
Once we can get a Makefile fix into Git's upstream, we can remove the
override for LIB_FUZZING_ENGINE.
However, this change causes `check_build` to fail for honggfuzz, and we
have not yet been able to diagnose the reason. So for now, we also need
to limit our engines to afl and libfuzzer.
|
| |
|
|
|
|
| |
Create util fuzzer
Add project settings
|
| |
|
|
|
|
|
|
|
|
| |
* google-auth-library-python: initial integration
Initial integration of
https://github.com/googleapis/google-auth-library-python
* nit
|
|
|
|
|
|
|
| |
* python-cloud-core: initial integration
Initial integration of https://github.com/googleapis/python-cloud-core
* nit
|
|
|
|
| |
Initial integration of
https://github.com/googleapis/google-resumable-media-python
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* psycopg2: initial integration
build initial fuzzer
* Fix Dockerfile
Fix error handling
* Fix data length
Fix formatting
* Fix fuzzer
* Fix project contact
|
|
|
| |
Fixes: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46923
|
|
|
| |
Fixes: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=48948
|
|
|
|
|
|
| |
* ghostscript: add tiff fuzzer
Similar to all other devices with exception it writes to file instead of
/dev/null. This is needed because tiff writing requires seek abilities.
|
|
|
|
|
|
| |
This reverts commit 4a13e59f3a09cece14001ed747c08ef06a6fb126.
Thanks to the Google Patch Rewards Program for supporting my work on
libxml2 and libxslt!
|
| |
|
|
|
|
|
|
|
| |
Update project.yaml
Add new `auto_ccs`
Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
|
|
|
| |
Replaces #7954
|
|
|
| |
Signed-off-by: AdamKorcz <adam@adalogics.com>
|
|
|
|
| |
This is now the email address for my Google account; I changed it a
while ago.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [crossplane] Initial integration
Signed-off-by: AdamKorcz <adam@adalogics.com>
* Update Dockerfile
* Update build.sh
* Update fuzz.go
Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
|
|
|
| |
Work-around for recent libyal project updates
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* google-cloud-logger-python: initial integration
Create initial integration
Create fuzzers
* google-cloud-logger-python: fix folder name
- Remove "google" from folder name
|
|
|
|
|
|
|
| |
* g-apis-py-core: initial integration
Initial integration of https://github.com/googleapis/python-api-core
* expand fuzzer
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Google requires the primary_contact is not the alternate email on a google
account.
https://github.com/google/oss-fuzz/issues/7985
|
|
|
|
|
| |
Builds Werkzeug from latest, which is also needed for proper fuzzing.
Fixes: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=49025
|
|
|
| |
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=48949
|
|
|
|
|
|
|
| |
* ghostscript: add three new devices fuzzers
* nits
* simplify build
|
| |
|
| |
|
| |
|
|
|
| |
Signed-off-by: AdamKorcz <adam@adalogics.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* libwebsockets: Add fuzzer for lws-upng
* Add License
* Fix sanitzer config
* Fix fuzzing_engine config
* Update Dockerfile
* Update build.sh
Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
|
| |
|
|
|
| |
Add fuzzer_metadata
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* infra: have timeout per fuzz target for coverage
As is done for other languages
* ngolo-fuzzing: remove temporary workaround
now that https://github.com/golang/go/issues/53190 is closed
* ngolo-fuzzing: use built go toolchain in its directory
without copying it to /root/.go/
in order to get coverage for std lib in the end
* infra: ability to get coverage for additional golang package
And uses it with ngolo-fuzzing :
ngolo-fuzzing fuzz targets live in a different repository than
the code being fuzzed, and we we want to get the coverage, for
both the fuzz target and the package being fuzzed
* fixup bash unbound
* fixup ngolo-fuzzing only match at beginning for std package
* stricter check for every additional go package
|
|
|
|
|
|
|
|
|
| |
* Disable dataflow builds for projects that have enabled it.
Related: https://github.com/google/oss-fuzz/issues/7963
* fix openjpeg
* fix
|
|
|
|
| |
As suggested on https://github.com/warmcat/libwebsockets/issues/2687 I'd
like to add lws to oss-fuzz.
|
|
|
| |
To debug https://github.com/golang/go/issues/49075
|
|
|
| |
Fix typo in code
|
|
|
| |
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=48789
|
|
|
|
|
| |
* [wolfssl] Fix build
* [wolfssl] Fix build try 2
|