X-Git-Url: https://wimlib.net/git/?p=wimlib;a=blobdiff_plain;f=NEWS;h=644d10f120bbef6b559822d6e2700be58ba9f499;hp=7d7ab340615e7efdb25cbce3bd83b34ca5795e1c;hb=e5a57ce54a643464c54d74b89a594f9e42fe3097;hpb=73004fcaa39fdc5e8b55b9e2835c862e0c104874

diff --git a/NEWS b/NEWS
index 7d7ab340..644d10f1 100644
--- a/NEWS
+++ b/NEWS
@@ -1,4 +1,86 @@
-Version 1.7.3-BETA:
+Version 1.8.1-BETA:
+	Fixed a bug in the LZX decompressor: malicious input data could cause
+	out of bounds writes to memory (since wimlib v1.2.2).
+
+	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".
+	wimlib will now store and restore both streams on Windows as well as in
+	NTFS-3g mode.  Microsoft's WIMGAPI also has this behavior.
+
+	On Windows, named data streams of encrypted files are no longer stored
+	twice in WIM archives.
+
+	On Windows, named data streams are now correctly extracted to existing
+	"readonly" directories.  Before, an error would be reported.
+
+	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.
+
+	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.
+
+Version 1.8.0:
+	Improved the LZX compressor.  It is now 15-20% faster than before and
+	provides a slightly better compression ratio.
+
+	Improved the LZMS compressor.  It now provides a compression ratio
+	slightly better than WIMGAPI while still being faster and using slightly
+	less memory.
+
+	The compression chunk size in solid resources, e.g. when capturing or
+	exporting a WIM file using the '--solid' option, now defaults to 64 MiB
+	(67108864 bytes) instead of 32 MiB (33554432 bytes).  This provides a
+	better compression ratio and is the same value that WIMGAPI uses.  The
+	memory usage is less than 50% higher than wimlib v1.7.4 and is slightly
+	lower than WIMGAPI's memory usage, but if it is too much, it is still
+	possible to choose a lower value, e.g. with the '--solid-chunk-size'
+	option to wimlib-imagex.
+
+	The '--chunk-size' and '--solid-chunk-size' options to wimlib-imagex now
+	accept the 'K', 'M', and 'G' suffixes.
+
+	Files are now sorted by name extension when creating a solid WIM file.
+
+	Fixed various issues related to capture/apply of EFS-encrypted files on
+	Windows.
+
+	The file list printed by 'wimdir' is now sorted by the platform-specific
+	case sensitivity setting, rather than always case sensitively.  This
+	also affects the library function wimlib_iterate_dir_tree().
+
+	On Windows, some error and warning messages have been improved.
+
+Version 1.7.4:
+	The Windows binary distribution no longer contains third party DLLs.
+	These dependencies are instead compiled directly into the libwim DLL.
+
+	Added more fixes for wimlib on non-x86 architectures such as ARM.
+
+	Extracting files to a Windows PE in-memory filesystem no longer fails if
+	the target files do not yet exist.
+
+	Improved the performance of XPRESS compression and LZMS decompression.
+
+	Enabled SSSE3 accelerated SHA-1 computation in x86_64 Windows builds.
+	It will automatically be faster on newer Intel and AMD processors.
+
+	Removed the --with-imagex-progname and --enable-more-assertions
+	configure options.
+
+Version 1.7.3:
+	Fix for very slow export from solid WIM / ESD files.
+
+	Fix for LZX and LZMS algorithms on non-x86 architectures, such as ARM.
+
+	New progress message: WIMLIB_PROGRESS_MSG_HANDLE_ERROR.  Applications
+	may use this to treat some types of errors as non-fatal.
+
 	The library now permits making in-memory changes to a WIMStruct backed
 	by a read-only WIM file.
 
@@ -16,13 +98,6 @@ Version 1.7.3-BETA:
 		Added a hack to try to work around an intermittent bug in
 		Microsoft's WOF (Windows Overlay Filesystem) driver.
 
-	Added a workaround that tries to prevent short filename conflicts.  It
-	can have an effect primarily on versions of Windows that do not support
-	removing short names from files (earlier than Windows 7).
-
-	New progress message: WIMLIB_PROGRESS_MSG_HANDLE_ERROR.  Applications
-	may use this to treat some types of errors as non-fatal.
-
 Version 1.7.2:
 	Made more improvements to the XPRESS, LZX, and LZMS compressors.