X-Git-Url: https://git.gag.com/?p=debian%2Fgzip;a=blobdiff_plain;f=NEWS;h=72b41099737e6789511da63052a28807c7568953;hp=ce0daaddfe43730d81b2bc2d9d0a8080ff9f5789;hb=659cae49714b93487242525dfa0e5737463d78d8;hpb=20fcfc81ece044b8b0a6768ec6cf47be4e22a2e6 diff --git a/NEWS b/NEWS index ce0daad..72b4109 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,59 @@ GNU gzip NEWS -*- outline -*- +* Noteworthy changes in release 1.10 (2018-12-29) [stable] + +** Changes in behavior + + Compressed gzip output no longer contains the current time as a + timestamp when the input is not a regular file. Instead, the output + contains a null (zero) timestamp. This makes gzip's behavior more + reproducible when used as part of a pipeline. (As a reminder, even + regular files will use null timestamps after the year 2106, due to a + limitation in the gzip format.) + +** Bug fixes + + A use of uninitialized memory on some malformed inputs has been fixed. + [bug present since the beginning] + + A few theoretical race conditions in signal handers have been fixed. + These bugs most likely do not happen on practical platforms. + [bugs present since the beginning] + + +* Noteworthy changes in release 1.9 (2018-01-07) [stable] + +** Bug fixes + + gzip -d -S SUFFIX file.SUFFIX would fail for any upper-case byte in SUFFIX. + E.g., before, this command would fail: + $ :|gzip > kT && gzip -d -S T kT + gzip: kT: unknown suffix -- ignored + [bug present since the beginning] + + When decompressing data in 'pack' format, gzip no longer mishandles + leading zeros in the end-of-block code. [bug introduced in gzip-1.6] + + When converting from system-dependent time_t format to the 32-bit + unsigned MTIME format used in gzip files, if a timestamp does not + fit gzip now substitutes zero instead of the timestamp's low-order + 32 bits, as per Internet RFC 1952. When converting from MTIME to + time_t format, if a timestamp does not fit gzip now warns and + substitutes the nearest in-range value instead of crashing or + silently substituting an implementation-defined value (typically, + the timestamp's low-order bits). This affects timestamps before + 1970 and after 2106, and timestamps after 2038 on platforms with + 32-bit signed time_t. [bug present since the beginning] + + Commands implemented via shell scripts are now more consistent about + failure status. For example, 'gunzip --help >/dev/full' now + consistently exits with status 1 (error), instead of with status 2 + (warning) on some platforms. [bug present since the beginning] + + Support for VMS and Amiga has been removed. It was not working anyway, + and it reportedly caused file name glitches on MS-Windowsish platforms. + + * Noteworthy changes in release 1.8 (2016-04-26) [stable] ** Bug fixes @@ -108,7 +162,7 @@ GNU gzip NEWS -*- outline -*- 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 + For more details, see https://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 @@ -208,10 +262,10 @@ Major changes in Gzip 1.3.7 (2006-12-06) Major changes in Gzip 1.3.6 (2006-11-20) -* Fix some race conditions in setting file time stamps, permissions, and owner. +* Fix some race conditions in setting file timestamps, permissions, and owner. * Fix some race conditions in signal handling. * When gzip exits due to a signal, it exits with the signal's status, not 1. -* gzip now restores file time stamps to the resolution supported by the +* gzip now restores file timestamps to the resolution supported by the time-setting primitives of the operating system, typically 1 microsecond. Formerly it restored them only to the nearest second. * gzip -r no longer attempts to reset the last-access times of directories @@ -344,7 +398,7 @@ Major changes from 1.0.7 to 1.1. * Added comparison of zip and gzip in the readme file. * Added small sample programs (ztouch, sub, add) * Use less memory when compiled with -DSMALL_MEM (for MSDOS). -* Remove the "off by more than one minute" time stamp kludge +* Remove the "off by more than one minute" timestamp kludge Major changes from 1.0.6 to 1.0.7. * Allow zmore to read from standard input (like more). @@ -423,7 +477,7 @@ Major changes from 1.0.1 to 1.0.2 on such systems. * Added gzexe to compress rarely used executables. * Reduce memory usage (required for MSDOS and useful on all systems). -* Preserve time stamp in znew -P (pipe option) if touch -r works. +* Preserve timestamp in znew -P (pipe option) if touch -r works. Major changes from 1.0 to 1.0.1 @@ -464,7 +518,7 @@ Major changes from 0.7 to 0.8: Major changes from 0.6 to 0.7: * Use "make check" instead of "make test". -* Keep time stamp and pass options to gzip in znew. +* Keep timestamp and pass options to gzip in znew. * Do not create .z.z files with gzip -r. * Allow again gunzip .zip files (was working in 0.5) * Allow again compilation with TurboC 2.0 (was working in 0.4) @@ -484,7 +538,7 @@ Major changes form 0.5 to 0.6: ======================================================================== -Copyright (C) 1999, 2001-2002, 2006-2007, 2009-2016 Free Software Foundation, +Copyright (C) 1999, 2001-2002, 2006-2007, 2009-2018 Free Software Foundation, Inc. Copyright (C) 1992, 1993 Jean-loup Gailly