aboutsummaryrefslogtreecommitdiffhomepage
path: root/projects/libjpeg-turbo
Commit message (Collapse)AuthorAge
* [libjpeg-turbo] Fuzz multiple code branches (#7528)Gravatar DRC2022-04-08
| | | | | | | | | | | | | | | | | | | | | | libjpeg-turbo uses a stable mainline branch model, so the main branch is always stable and feeds into the current release series. The next-gen evolving release series is developed in the dev branch, and bug fixes are cherry-picked into stable branches for past release series. It is desirable to fuzz the dev branch to ensure that bugs are caught before the evolving code is merged down into main (which generally occurs in conjunction with a beta release) and also to allow for the fuzzers themselves to evolve along with the libjpeg-turbo feature set. It is also desirable to fuzz the stable branch from the most recent release series (2.0.x at the moment) to ensure that the same quality is maintained from when that code occupied the main branch. Note that both the Dockerfile and multi-branch build script included in this commit accommodate the fact that the dev branch may not exist. The dev branch will not exist between the time that the current release series enters beta and the first feature for the next-gen release series is developed. Closes #7479
* [libjpeg-turbo] Remove unneeded pkg in Dockerfile (#5574)Gravatar DRC2021-04-02
| | | | Installing the i386 libstdc++ SDK was part of a failed effort to fix the i386 fuzz targets. They have been fixed in a different way.
* [libjpeg-turbo] Use new fuzzers in project repo (#5537)Gravatar DRC2021-04-02
| | | | | | | | | | | | | | | | | | | | | | - Eliminate unnecessary packages from Docker image (Autotools has not been required since libjpeg-turbo 1.5.x.) - Obtain seed corpora from a new Git repository maintained by The libjpeg-turbo Project. (This new repo contains the old corpora from https://lcamtuf.coredump.cx, with duplicates removed, and some new corpora curated from historical libjpeg-turbo bug reports.) - Remove build.sh. (The libjpeg-turbo Project is now maintaining its own build script in order to facilitate the future creation of new fuzz targets.) - Remove fuzz target source code. (The libjpeg-turbo Project is now maintaining its own fuzz targets with better code coverage.) - Update the project home page in project.yaml. - Change the project language to C in project.yaml. (The new fuzz targets are written in pure C rather than C++, since libjpeg-turbo is a C-only project.)
* [libjpeg-turbo] Fix build with libjpeg-turbo 2.1.x (#5519)Gravatar DRC2021-03-26
| | | | | | | libjpeg-turbo 2.1 now requires NASM 2.13 or later or YASM 1.2.0 or later. Since the Docker image is based on Ubuntu 16.04, NASM 2.13 isn't available, so the easiest workaround is to use YASM instead. Fixes #4931
* Populate a bunch of main_repo values. (#4815)Gravatar Oliver Chang2020-12-10
| | | | Also enforce this for future integrations.
* Update project.yamlGravatar Oliver Chang2020-11-26
|
* [libjpeg-turbo] DRC’s Google acct—>primary_contact (#4721)Gravatar DRC2020-11-25
| | | This will enable the libjpeg-turbo maintainer to see oss-fuzz bug reports.
* [libjpeg-turbo] Update project contacts (#4436)Gravatar DavidKorczynski2020-09-10
| | | I spoke to the maintainers of libjperg turbo and they would like to have this email added to the CC list of bug reports.
* Update Dockerfiles (#4070)Gravatar devtty1er2020-07-06
| | | | | * Use LABEL in place of MAINTAINER * Remove LABEL maintainer from Dockerfiles
* Upgrade lcamtuf.coredump.cx to HTTPS, as it has been (#3527)Gravatar Lovell Fuller2020-03-20
| | | | | | accepting only HTTPS connections since approx 14th March. This allows the builds for guetzli, libjpeg-turbo, libtiff and libvips to succeed again.
* [presubmit] Enforce language attribute in project.yaml to be always set. (#3477)Gravatar Max Moroz2020-03-10
| | | | | | | | | | | | | | | | | | | * [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
* [libjpeg-turbo] Update CC list (#3087)Gravatar Tyson Smith2019-12-04
|
* Add Mozilla fuzzing team to auto_cc of their used 3rd party libraries (#2703)Gravatar Christoph Diehl2019-08-28
| | | | | | | | | | * Add Mozilla fuzzing team to auto_cc of their used 3rd party libraries * Use new vendor_ccs field in projects.yml (#2703) * Remove not yet approved projects * Remove not yet approved projects
* libjpeg-turbo: enable i386 architecture and improve fuzzer regarding msan ↵Gravatar Even Rouault2019-08-12
| | | | | | (#2680)
* 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
* fix libjpeg-turbo build (#1269)Gravatar Paul Kehrer2018-03-25
|
* Use apt-get update && apt-get install, per best practices: (#561)Gravatar Devin Jeanpierre2017-05-01
| | | | | | | | | | | | | | | | | | | 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
* Remove experimental flag from already tested projects with msan(#473) (#513)Gravatar Abhishek Arya2017-04-04
|
* oss-fuzz/BASE_IMAGE -> oss-fuzz-base/BASE_IMAGEGravatar Oliver Chang2017-03-22
|
* Enable Msan experimentally for some projects (#473).Gravatar Oliver Chang2017-03-21
|
* [infra] ossfuzz/IMAGE -> gcr.io/oss-fuzz/IMAGEGravatar Oliver Chang2017-03-15
|
* Update project.yamlGravatar Abhishek Arya2017-02-02
|
* [infra] updating usages of base-libfuzzer (#142)Gravatar Mike Aizatsky2017-01-03
|
* [libjpeg-turbo] small simplification to dockerfile (#226)Gravatar Alex Gaynor2016-12-28
|
* [libjpeg-turbo] enabling ubsanGravatar Mike Aizatsky2016-12-27
|
* Don't overflow on multiplication in the libjpeg_turbo fuzzer (#218)Gravatar Alex Gaynor2016-12-27
|
* Update DockerfileGravatar Abhishek Arya2016-12-24
|
* Add test corpus from libjpeg-turbo repoGravatar Abhishek Arya2016-12-24
|
* [infra] using -lFuzzingEngine instead of -lfuzzerGravatar Mike Aizatsky2016-12-07
|
* Expand the corpus used by the libjpeg-turbo fuzzer (#104)Gravatar Alex Gaynor2016-11-29
|
* [infra] making shallow git clones. fixes #42Gravatar Mike Aizatsky2016-11-29
|
* [infra] target.yaml -> project.yamlGravatar Mike Aizatsky2016-11-29
|
* [infra] renaming targets/ to projects/Gravatar Mike Aizatsky2016-11-29
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-06 01:04:38 +0000