| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
* libssh: Build new fuzzers in .c files
* libssh: Change c++ -> c in metadata too
|
|
|
|
|
|
|
| |
(#6303)
Do this based mostly on instrumented_libraries and more tests.
Related: #6180
|
|
|
|
|
|
|
| |
These projects were tested and it was found that their use
of MSAN does not work on Ubuntu 20.04. Therefore their use of
MSAN is being disabled.
Related: #6180
|
| |
|
| |
|
|
|
|
|
| |
* Use LABEL in place of MAINTAINER
* Remove LABEL maintainer from Dockerfiles
|
|
|
|
|
|
|
|
|
| |
* libssh: Enable support for none ciphers to unbreak build
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22074
* Add a new include for libssh_version.h
https://gitlab.com/libssh/libssh-mirror/-/merge_requests/116
|
|
|
|
|
| |
Do it in separate work directory and prepare for corpus inclusion
Signed-off-by: Jakub Jelen <jjelen@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [presubmit] Enforce language attribute in projectt.yaml to be always set.
* Update documentation, better presubmit check, new project template.
* add docstring to templates.py
* Add example values in the project.yaml template and remove python value for now
* Add "project: c++" to 256 projects
* format
* Add labels and selective_unpack sections to the presubmit check
* fix incorrect auto_ccs format in three projects
* fix nss emails after rebase
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* [libssh] Enable msan
Signed-off-by: Andreas Schneider <asn@cryptomilk.org>
* [libssh] Add Jakub Jelen to the project
Signed-off-by: Andreas Schneider <asn@cryptomilk.org>
|
|
|
|
|
|
| |
* [libssh] Clone the repository with depth=1
* [libssh] Add a client fuzzer
|
|
|
| |
Migrate from -lFuzzingEngine to $LIB_FUZZING_ENGINE where possible and not causing breakage
|
|
|
| |
Fix #1161
|
| |
|
|
|
| |
Fixes #1161
|
| |
|
|
|
|
|
|
| |
The fuzzer has been integrated into the source code. It is also compiled
there linking against libFuzzer.a from the clang project. However it
seems that oss-fuzz uses its own library so we still need to create the
executable on our own here and can't let cmake do it.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/
I ran into this because I was getting errors locally, like:
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/d/dpkg/libdpkg-perl_1.18.4ubuntu1.1_all.deb 404 Not Found [IP: 91.189.88.149 80]
It turns out you get these if you don't update, and the official best practices are to `run apt-get update && apt-get install`. In fact, running _any_ apt-get install command without the apt-get update && before it can result in unfortunate caching artifacts -- see "cache busting". (P.S. thanks to Peng on Freenode for helping me, I'm bad at Ubuntu.)
So:
sed -re \
's/RUN apt-get ((-y )?(install|build-dep))/RUN apt-get update \&\& apt-get \1/' -i \
projects/**/Dockerfile
I also manually fixed the cases that already ran apt-get update in their Dockerfile:
dlplibs/Dockerfile
grpc/Dockerfile
libreoffice/Dockerfile
|
| |
|
|
|
|
| |
Should hopefully fix https://github.com/google/oss-fuzz/pull/418#issuecomment-295277016
|
| |
|
| |
|
|
|