X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=NEWS;h=f9e48e87bf35b13715b9e914e4b7db454ab69725;hb=503506009abee645fc93e835367237aecb0c8564;hp=b809273a5efef6d6ab26cdca6bf092f811faaca7;hpb=800deb09b422a73c1212233a93839a223ff59678;p=debian%2Fgzip diff --git a/NEWS b/NEWS index b809273..f9e48e8 100644 --- a/NEWS +++ b/NEWS @@ -1,7 +1,80 @@ +GNU gzip NEWS -*- outline -*- + +* Noteworthy changes in release 1.5 (2012-06-17) [stable] + +** Bug fixes + + gzip -d now decodes and checks header CRC16 checksums as specified by + the FHCRC section of Internet RFC 1952. + + "gzip -d -S '' precious.gz" is now rejected immediately. Before, + that command would emulate "rm -i precious.gz", but with an easily- + misunderstood prompt. I.e., gzip would ask if it's ok to remove the + existing file, "precious.gz". If you made the mistake of saying "yes", + it would remove that input file before attempting to uncompress it. + + gzip -cdf now properly handles input consisting of gzip'd data followed + by uncompressed data. Before it would output raw compressed input, too. + For example, now "(printf x|gzip; echo y)|gzip -dcf" prints "xy\n", + while before it would print "xy\n". + + gzip -rf no longer compresses files more than once (e.g., replacing + FOO with FOO.gz.gz) on file systems such as ZFS where a readdir + loop that unlinks and creates files can revisit output files. + + +* Noteworthy changes in release 1.4 (2010-01-20) [stable] + +** Bug fixes + + gzip -d could segfault and/or clobber the stack, possibly leading to + arbitrary code execution. This affects x86_64 but not 32-bit systems. + This fixes CVE-2010-0001. + For more details, see http://bugzilla.redhat.com/554418 + + gzip -d would fail with a CRC error for some valid inputs. + So far, the only valid input known to exhibit this failure was + compressed "from FAT filesystem (MS-DOS, OS/2, NT)". In addition, + to trigger the failure, your memcpy implementation must copy in + the "reverse" order. + + +* Noteworthy changes in release 1.3.14 (2009-10-30) [beta] + +** Bug fixes + + gzip no longer fails when there is exactly one trailing NUL byte + gzip has always accepted trailing NUL bytes. Note the plural. + + zdiff would exit with status 2 (indicating an error) rather than 1 to + indicate differences when both inputs were compressed and different. + + zdiff would fail to print differences in two compressed inputs + + zgrep -f - didn't work + + +* Noteworthy changes in release 1.3.13 (2009-09-30) [stable] + +** 'gzip -f foo.gz' now creates a file foo.gz.gz instead of complaining. + +** Bug fixes + + gzip -d no longer fails with "-" as 2nd or subsequent argument + + gzip no longer ignores a close-induced write failure, e.g., on NFS + + gzip -d no longer segfaults on certain invalid inputs + + Major changes in Gzip 1.3.12 (2007-04-13) * znew now uses $TMPDIR (default /tmp) instead of always using /tmp. +* It is now documented that gzip ignores case when examining file name + extensions; for example, 'gzip test.Gz' (without -f) fails because + the file name ends in '.Gz'. + Major changes in Gzip 1.3.11 (2007-02-05) * As per the GNU coding standards, the behavior of gzip and its @@ -333,11 +406,12 @@ Major changes form 0.5 to 0.6: ======================================================================== -Copyright (C) 1999, 2001, 2002, 2006, 2007 Free Software Foundation, Inc. +Copyright (C) 1999, 2001-2002, 2006-2007, 2009-2012 Free Software Foundation, +Inc. Copyright (C) 1992, 1993 Jean-loup Gailly Permission is granted to copy, distribute and/or modify this document -under the terms of the GNU Free Documentation License, Version 1.2 or +under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the ``GNU Free