From 12b39aab6092348d0883cf482839110dd1c0f40b Mon Sep 17 00:00:00 2001 From: Frank Denis Date: Mon, 29 Dec 2025 23:09:17 +0100 Subject: [PATCH] Sync ChangeLog --- ChangeLog | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index a3368d7a..7dd7d58c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -7,15 +7,29 @@ with some compilers - Windows ARM binaries have been added to the NuGet package - The Android build script has been improved. The base SDK is now 27c, and the default platform is 21 - - The library can now be compiled with Zig 0.14+ + - The library can now be compiled with Zig 0.15 and Zig 0.16 + - Zig builds now generate position-independent static libraries by +default on targets that support PIC - arm64e builds have been added to the XCFramework packages - XCFramework packages are now full builds instead of minimal builds - MSVC builds have been enabled for ARM64 + - iOS 32-bit (armv7/armv7s) support has been removed from the +XCFramework build script + - Security: optblockers have been introduced in critical code paths +to prevent compilers from introducing unwanted side channels via +conditional jumps. This was observed on RISC-V targets with specific +compilers and options. + - Security: `crypto_core_ed25519_is_valid_point()` now properly +rejects small-order points that are not in the main subgroup + - `((nonnull))` attributes have been relaxed on some `crypto_stream*` +functions to allow NULL output buffers when the output length is zero - A cross-compilation issue with old clang versions has been fixed - 16K page sizes are now supported on Android - JavaScript: support for Cloudflare Workers has been added + - JavaScript: WASM_BIGINT is forcibly disabled to retain +compatibility with older runtimes - A compilation issue with old toolchains on Solaris has been fixed - `crypto_aead_aes256gcm_is_available` is exported to JavaScript