Fix tagged item parsing infinite loop when 32-bit and len=0xFFFFFFF8

[wimlib] / NEWS

diff --git a/NEWS b/NEWS
index 7b4a0e37ee11b7bf7e78f83197a998f4354e2c89..50c2131339657a7c0cf6e9666837b3f21227abf1 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,14 @@
-Version 1.8.1-BETA:
+Version 1.8.2-BETA:
+       Fixed a bug: on 32-bit systems, the library would enter an infinite loop
+       if WIM image metadata was malformed in a very specific way.
+
+Version 1.8.1:

        Fixed a bug in the LZX decompressor: malicious input data could cause
        out of bounds writes to memory (since wimlib v1.2.2).
 
        Fixed a bug in the LZX decompressor: malicious input data could cause
        out of bounds writes to memory (since wimlib v1.2.2).
 

+       The output of the 'wiminfo' command now consolidates various boolean
+       flags (such as "Relative path junction") into a single line.
+

        A file can now have both an unnamed data stream ("file contents") and a
        reparse point stream.  Such files can exist as a result of the use of
        certain Windows features, such as offline storage, including "OneDrive".
        A file can now have both an unnamed data stream ("file contents") and a
        reparse point stream.  Such files can exist as a result of the use of
        certain Windows features, such as offline storage, including "OneDrive".


@@ -14,6 +21,9 @@ Version 1.8.1-BETA:
        On Windows, named data streams are now correctly extracted to existing
        "readonly" directories.  Before, an error would be reported.
 
        On Windows, named data streams are now correctly extracted to existing
        "readonly" directories.  Before, an error would be reported.
 

+       On Windows, it is now possible to do a "WIMBoot mode" extraction with
+       non-standalone WIMs such as delta WIMs.
+

        On Windows, when doing an extraction in "WIMBoot mode", files larger
        than 4 gigabytes are now never extracted as externally backed.  This
        works around a bug in Microsoft's "WOF" driver.
        On Windows, when doing an extraction in "WIMBoot mode", files larger
        than 4 gigabytes are now never extracted as externally backed.  This
        works around a bug in Microsoft's "WOF" driver.


@@ -21,6 +31,19 @@ Version 1.8.1-BETA:
        The '--enable-verify-compression' configure option has been removed.  If
        you want to verify a WIM file, use the 'wimverify' program.
 
        The '--enable-verify-compression' configure option has been removed.  If
        you want to verify a WIM file, use the 'wimverify' program.
 

+       The way the "file count", "directory count", "total bytes", and "hard
+       link bytes" image statistics (stored in the WIM XML data) is calculated
+       has been slightly changed.
+
+       In mounted WIM images, the disk usage provided for each file (st_blocks)
+       is now the compressed size rather than the uncompressed size.
+
+       The performance of the NTFS-3g and Windows capture modes has been
+       slightly improved.
+
+       On UNIX-like systems, symbolic links whose targets contain the backslash
+       character are now handled correctly (losslessly).
+

 Version 1.8.0:
        Improved the LZX compressor.  It is now 15-20% faster than before and
        provides a slightly better compression ratio.
 Version 1.8.0:
        Improved the LZX compressor.  It is now 15-20% faster than before and
        provides a slightly better compression ratio.