extract.c: control characters are invalid in filenames on Windows

[wimlib] / NEWS

diff --git a/NEWS b/NEWS
index 55235ead2f5ba9096c4d0ae64c7ac452a72a5f24..61de93bc45a1dbb919cdde2aaa899d76eff0bf06 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,19 @@
-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.
+
+       Reduced the stack space used by directory tree scans.
+
+       Windows symbolic links and junctions in mounted WIM images are now
+       automatically rewritten to be valid in the mounted location.
+
+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 +26,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.