aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2021-03-12spotify-json: initial integration. (#5014)DavidKorczynski
* spotify json: initial integration. * Updated the spotify-json library to reflect upstream fuzzer merge.
2021-03-12json5format initial integration (#5354)DavidKorczynski
* json5format initial integration * Updated the dockerfile for json5format.
2021-03-12[fastjson2] Initial integration of alibaba/fastjson (#5373)Fabian Meumertzheim
2021-03-12More generic target directory for rust coverage (#5366)Catena cyber
* More generic target directory for rust coverage * Rust coverage cargo does not change PATH
2021-03-12Update project.yaml (#5375)DavidKorczynski
2021-03-12[CIFuzz] Add functionality to save diskspace (#5342)jonathanmetzman
* [CIFuzz] Add functionality to save diskspace. Add a LOW_DISK_SPACE env/config var. When this is specified (always true for Github actions) run_fuzzers will delete base-builder and the project builder image before fuzzing. After it finishes fuzzing with a target, it will also delete the targets, its seed corpus and its corpus. Related: #4879
2021-03-12Modify deadline text to disclose immediately after fix is released. (#5323)Oliver Chang
2021-03-11[firefox/spidermonkey] Remove cargo wrapper in /usr/local/bin to fix builds ↵Christian Holler (:decoder)
(#5369)
2021-03-10[c-blosc2] Link shared libraries with lld for -fno-semantic-interposition ↵Nathan Moinvaziri
support. (#5360)
2021-03-10protobuf-c: fix coverage builds, use latest code (#5363)Ilya Lipnitskiy
* protobuf-c: fix coverage builds, ignore protobuf results No need to include Google Protobuf library coverage results, since we are testing protobuf-c. * protobuf-c: use pkg-config for dependency resolution * protobuf-c: use next branch to check latest code master is not the latest branch in the protobuf-c repo. Run fuzzer on the next branch, which is the development branch for the next release. * protobuf-c: add myself to CC list
2021-03-10[libavif] Fix corpus to have proper av1C property associations (#5364)Joe Drago
Related: https://github.com/AOMediaCodec/libavif/pull/537 Co-authored-by: Joe Drago <jdrago@netflix.com>
2021-03-10Update project.yaml (#5365)Tadeusz Struk
2021-03-10Improve Actions hygiene (#5361)Seth Vargo
👋 hello there! I'm a fellow Googler who works on projects that leverage GitHub Actions for CI/CD. Recently I noticed a large increase in our queue time, and I've tracked it down to the [limit of 180 concurrent jobs](https://docs.github.com/en/actions/reference/usage-limits-billing-and-administration) for an organization. To help be better citizens, I'm proposing changes across a few repositories that will reduce GitHub Actions hours and consumption. I hope these changes are reasonable and I'm happy to talk through them in more detail. - Only run GitHub Actions for pushes and PRs against the main branch of the repository. If your team uses a forking model, this change will not affect you. If your team pushes branches to the repository directly, this changes actions to only run against the primary branches or if you open a Pull Request against a primary branch. - For long-running jobs (especially tests), I added the "Cancel previous" workflow. This is very helpful to prevent a large queue backlog when you are doing rapid development and pushing multiple commits. Without this, GitHub Actions' default behavior is to run all actions on all commits. There are other changes you could make, depending on your project (but I'm not an expert): - If you have tests that should only run when a subset of code changes, consider gating your workflow to particular file paths. For example, we have some jobs that do Terraform linting, but [they only run when Terraform files are changed](https://github.com/google/exposure-notifications-verification-server/blob/c4f59fee71042cf668747e599e7c769fca736554/.github/workflows/terraform.yml#L3-L11). Hopefully these changes are not too controversial and also hopefully you can see how this would reduce actions consumption to be good citizens to fellow Googlers. If you have any questions, feel free to respond here or ping me on chat. Thank you!
2021-03-10Use more RUSTFLAGS for Suricata (#5352)Catena cyber
* Use more RUSTFLAGS for Suricata Taken from libra and cargo fuzz * rustflags only for asan
2021-03-10[json-sanitizer] Add severity markup (#5350)Fabian Meumertzheim
Annotates the findings of the various json-sanitizer fuzzers with severities as follows: * XSS: High * Comment injection: Medium * Invalid JSON: Low * Failure to be idempotent: Not a security issue * Undeclared exceptions: Not a security issue This commit takes advantage of the support for severity markers in stack traces introduced in https://github.com/google/clusterfuzz/pull/2270.
2021-03-10Don't rpath patch llvm-symbolizer. (#5357)Abhishek Arya
Should fix https://github.com/google/oss-fuzz/issues/5349
2021-03-10Fix unzip regression on base-runner. (#5356)Abhishek Arya
* Fix unzip regression on base-runner. * Dont rpath patch llvm-symbolizer. Should fix https://github.com/google/oss-fuzz/issues/5349 * Revert "Dont rpath patch llvm-symbolizer." This reverts commit fdd881dea252fa2da655eb8c88dd4057db6f0215.
2021-03-10Include Loki team for the notification email (#5359)Kaviraj
2021-03-10[vitess] Add maintainers (#5358)AdamKorcz
2021-03-09[base-builder] Remove unnecessary python files (58 MB) (#5348)jonathanmetzman
Related: #5170
2021-03-09[cairo] Add vendor_ccs (#5347)Tyson Smith
2021-03-09Rust coverage : source remap after changing dir (#5345)Catena cyber
2021-03-09Allow security team of Gitea to access the issues (#5338)Lunny Xiao
And once the security team members changed, we have to send new PR to change this.
2021-03-09[base-builder] Delete unneeded files from atheris install (#5344)jonathanmetzman
2021-03-09[infra] Remove minijail. (#5343)jonathanmetzman
We don't need minijail tooling anymore since we aren't using it on OSS-Fuzz.
2021-03-09[base-runner] Reduce size by ~200 MB by using apt better (#5339)jonathanmetzman
Don't install recommended packages if it means installing an entire gcc toolchain. We don't need it in the runner.
2021-03-09[CIFuzz][cifuzz-base] Slim down cifuzz-base (#5288)jonathanmetzman
Reduce cifuzz-base size from 846MB to 444MB. 1. Don't install parts of docker that aren't necessary. 2. Use .dockerignore properly.
2021-03-09libfido2: update dependencies (#5340)Ludvig Michaelsson
* libfido2: update libcbor to v0.8.0 * libfido2: add new zlib dependency
2021-03-09[gpac] initial integration (#5289)DavidKorczynski
2021-03-09[go-sftp] Add go-sftp project (#5324)Catena cyber
2021-03-09[ygot] Add ygot project (#5245)Catena cyber
2021-03-09Golang coverage ok with package in $SRC (#5325)Catena cyber
2021-03-09[rnp] Update build script to reflect library naming change. (#5327)Nickolay Olshevsky
2021-03-09fix afl++ asan options (#5336)van Hauser
2021-03-09[gitea] Use a special email address to manage security (#5334)Lunny Xiao
2021-03-09[clamav] Disable honggfuzz (#5322)Micah Snyder
The honggfuzz fuzz targets are failing the build checks for reasons unknown. Disabling for now because I don't know how to debug it.
2021-03-08Golang coverage with go 1.16 and modules (#5321)Catena cyber
* Fixes go coverage with modules * Golang coverage html report turning off modules Otherwise, we get the error working directory is not part of a module
2021-03-08libvips: ensure linker is aware of selinux/resolv deps (#5318)Lovell Fuller
2021-03-08[base-runner] Fix go issue and remove uneeded rust stuff. (#5319)jonathanmetzman
Go needs the toolchain for now, so add it back to base-runner. We don't actually need the rust toolchain so get rid of it (saving about 1GB).
2021-03-08Rust coverage report (for Suricata) (#4697)Catena cyber
* Rust coverage test * Workaround to get rust coverage for Suricata
2021-03-07[cryptofuzz] Fix build (#5310)Guido Vranken
* [cryptofuzz] Fix build * [cryptofuzz] Trigger CI
2021-03-07proj4/Dockerfile: install wget (#5313)Even Rouault
Builds are currently broken since running libtiff ./autogen.sh requires wget ``` autoconf echo ./autogen.sh: getting config.guess... ./autogen.sh: getting config.guess... wget -q --timeout=5 -O config/config.guess.tmp https://git.savannah.gnu.org/cgit/config.git/plain/config.guess ```
2021-03-07[wolfssl] Import Wycheproof test vectors into corpus (#5314)Guido Vranken
2021-03-07dropbear: move corpus out of the source checkout (#5315)Matt Johnston
This should fix cifuzz which replaces the checkout
2021-03-06dropbear: Use github so cifuzz might work (#5312)Matt Johnston
2021-03-06add asan poison check to afl++ cmplog (#5311)van Hauser
* output afl++ setup * update commit id * update afl++ commit id * asan + cmplog fix * update commit id * update and enhance afl++ * update afl++ commit id, better run asan options * fix linter * add debug_afl script * Update debug_afl * Update compile_afl * fix for karchive * put debug_afl in the docker container * asan poison fix Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
2021-03-05[freeimage] Use the SVN repo instead of the latest source archive. (#3414)Max Moroz
* [freeimage] Use the SVN repo instead of the latest source archive. Requested in https://github.com/google/oss-fuzz/pull/2606#issuecomment-588533038 * fix the path * fix path again * more fixes * should work now! * test locally
2021-03-05[clamav] Switch from autotools to cmake (#5302)Micah Snyder
For the CMake build, build all dependencies as static libraries first. To automate this, the Dockerfile uses the Mussels tool. The HAVE_MMAP variable is explicitly disabled so that malloc is used in place of mmap, which will yield better fuzzing results.
2021-03-05Fix TensorFlow coverage build. (#5309)Mihai Maruseac
It seems that due to some recent change in `BUILD` rules, `bazel` creates a copy of the code tree under `bazel-tensorflow/external/org_tensorflow` symlink. However, the tree contains a `bazel-tensorflow` symlink so we get to an infinite symlink expansion issue. This breaks coverage build. The fix is simple: before copying `bazel-tensorflow/external` to `${OUT}` in coverage builds, remove `org_tensorflow` symlink. This is not an issue for the coverage build since we copy the entire source tree to the coverage directory in a previous step.
2021-03-05[runc] Initial integration (#5287)AdamKorcz
* [teleport] Initial integration * Minor update to run tests again * Remove debugging things * Removed an unfinished file * Small nit * Added maintainers * Update Dockerfile * Update build.sh * Update project.yaml * Updated licenses Co-authored-by: jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-24 15:23:14 +0000