aboutsummaryrefslogtreecommitdiff
path: root/projects/libjpeg-turbo
AgeCommit message (Collapse)Author
2021-04-02[libjpeg-turbo] Remove unneeded pkg in Dockerfile (#5574)DRC
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.
2021-04-02[libjpeg-turbo] Use new fuzzers in project repo (#5537)DRC
- 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.)
2021-03-26[libjpeg-turbo] Fix build with libjpeg-turbo 2.1.x (#5519)DRC
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
2020-12-10Populate a bunch of main_repo values. (#4815)Oliver Chang
Also enforce this for future integrations.
2020-11-26Update project.yamlOliver Chang
2020-11-25[libjpeg-turbo] DRC’s Google acct—>primary_contact (#4721)DRC
This will enable the libjpeg-turbo maintainer to see oss-fuzz bug reports.
2020-09-10[libjpeg-turbo] Update project contacts (#4436)DavidKorczynski
I spoke to the maintainers of libjperg turbo and they would like to have this email added to the CC list of bug reports.
2020-07-06Update Dockerfiles (#4070)devtty1er
* Use LABEL in place of MAINTAINER * Remove LABEL maintainer from Dockerfiles
2020-03-20Upgrade lcamtuf.coredump.cx to HTTPS, as it has been (#3527)Lovell Fuller
accepting only HTTPS connections since approx 14th March. This allows the builds for guetzli, libjpeg-turbo, libtiff and libvips to succeed again.
2020-03-10[presubmit] Enforce language attribute in project.yaml to be always set. (#3477)Max Moroz
* [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
2019-12-04[libjpeg-turbo] Update CC list (#3087)Tyson Smith
2019-08-28Add Mozilla fuzzing team to auto_cc of their used 3rd party libraries (#2703)Christoph Diehl
* 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
2019-08-12libjpeg-turbo: enable i386 architecture and improve fuzzer regarding msan ↵Even Rouault
(#2680)
2019-05-01Migrate projects using -lFuzzingEngine to $LIB_FUZZING_ENGINE (#2325)jonathanmetzman
Migrate from -lFuzzingEngine to $LIB_FUZZING_ENGINE where possible and not causing breakage
2018-03-25fix libjpeg-turbo build (#1269)Paul Kehrer
2017-05-01Use apt-get update && apt-get install, per best practices: (#561)Devin Jeanpierre
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
2017-04-04Remove experimental flag from already tested projects with msan(#473) (#513)Abhishek Arya
2017-03-22oss-fuzz/BASE_IMAGE -> oss-fuzz-base/BASE_IMAGEOliver Chang
2017-03-21Enable Msan experimentally for some projects (#473).Oliver Chang
2017-03-15[infra] ossfuzz/IMAGE -> gcr.io/oss-fuzz/IMAGEOliver Chang
2017-02-02Update project.yamlAbhishek Arya
2017-01-03[infra] updating usages of base-libfuzzer (#142)Mike Aizatsky
2016-12-28[libjpeg-turbo] small simplification to dockerfile (#226)Alex Gaynor
2016-12-27[libjpeg-turbo] enabling ubsanMike Aizatsky
2016-12-27Don't overflow on multiplication in the libjpeg_turbo fuzzer (#218)Alex Gaynor
2016-12-24Update DockerfileAbhishek Arya
2016-12-24Add test corpus from libjpeg-turbo repoAbhishek Arya
2016-12-07[infra] using -lFuzzingEngine instead of -lfuzzerMike Aizatsky
2016-11-29Expand the corpus used by the libjpeg-turbo fuzzer (#104)Alex Gaynor
2016-11-29[infra] making shallow git clones. fixes #42Mike Aizatsky
2016-11-29[infra] target.yaml -> project.yamlMike Aizatsky
2016-11-29[infra] renaming targets/ to projects/Mike Aizatsky