From: Matthias Klose <doko@ubuntu.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: gdb-patches@sourceware.org, binutils <binutils@sourceware.org>
Subject: [patch] update zlib to the 1.2.10 release.
Date: Thu, 05 Jan 2017 14:45:00 -0000 [thread overview]
Message-ID: <ec939349-8200-2cd3-c7c8-cc2abe70d722@ubuntu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2288 bytes --]
These are the changes updating zlib from 1.2.8 to 1.2.10. It is only used when
building without a system zlib. The new release includes fixes for security
issues CVE-2016-9840, CVE-2016-9841, CVE-2016-9842, CVE-2016-9843.
Checked with a build with disabled system-zlib. Ok for the trunk?
Matthias
Changes in 1.2.10 (2 Jan 2017)
- Avoid warnings on snprintf() return value
- Fix bug in deflate_stored() for zero-length input
- Fix bug in gzwrite.c that produced corrupt gzip files
- Remove files to be installed before copying them in Makefile.in
- Add warnings when compiling with assembler code
Changes in 1.2.9 (31 Dec 2016)
- Fix contrib/minizip to permit unzipping with desktop API [Zouzou]
- Improve contrib/blast to return unused bytes
- Assure that gzoffset() is correct when appending
- Improve compress() and uncompress() to support large lengths
- Fix bug in test/example.c where error code not saved
- Remedy Coverity warning [Randers-Pehrson]
- Improve speed of gzprintf() in transparent mode
- Fix inflateInit2() bug when windowBits is 16 or 32
- Change DEBUG macro to ZLIB_DEBUG
- Avoid uninitialized access by gzclose_w()
- Allow building zlib outside of the source directory
- Fix bug that accepted invalid zlib header when windowBits is zero
- Fix gzseek() problem on MinGW due to buggy _lseeki64 there
- Loop on write() calls in gzwrite.c in case of non-blocking I/O
- Add --warn (-w) option to ./configure for more compiler warnings
- Reject a window size of 256 bytes if not using the zlib wrapper
- Fix bug when level 0 used with Z_HUFFMAN or Z_RLE
- Add --debug (-d) option to ./configure to define ZLIB_DEBUG
- Fix bugs in creating a very large gzip header
- Add uncompress2() function, which returns the input size used
- Assure that deflateParams() will not switch functions mid-block
- Dramatically speed up deflation for level 0 (storing)
- Add gzfread(), duplicating the interface of fread()
- Add gzfwrite(), duplicating the interface of fwrite()
- Add deflateGetDictionary() function
- Use snprintf() for later versions of Microsoft C
- Fix *Init macros to use z_ prefix when requested
- Replace as400 with os400 for OS/400 support [Monnerat]
- Add crc32_z() and adler32_z() functions with size_t lengths
- Update Visual Studio project files [AraHaan]
[-- Attachment #2: zlib-1.2.10.diff.gz --]
[-- Type: application/gzip, Size: 94895 bytes --]
next reply other threads:[~2017-01-05 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 14:45 Matthias Klose [this message]
2017-01-12 21:17 ` Jeff Law
2017-01-12 21:27 ` Matthias Klose
2017-01-12 21:38 ` Jeff Law
2017-01-12 21:39 ` Jeff Law
2017-01-13 12:14 ` Matthias Klose
2017-01-22 18:01 ` Matthias Klose
2017-01-22 18:12 ` NightStrike
2017-01-22 18:42 ` Matthias Klose
2017-01-23 22:57 ` Iain Buclaw
2017-01-23 4:09 ` Joel Brobecker
2017-01-23 9:10 ` Matthias Klose
2017-01-23 16:01 ` Nick Clifton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ec939349-8200-2cd3-c7c8-cc2abe70d722@ubuntu.com \
--to=doko@ubuntu.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox