libwally-core

This commit only changes the project's continuous integration (CI) configuration. It re-enables a set of tests called 'clear tests' that were previously disabled in automated build pipelines, and adds a compiler warning suppression for an amalgamation compile test. There is no change to the actual library code that users run, so this commit does not introduce or fix a security vulnerability in the software itself.

This commit fixes a potential information leak in a cryptocurrency wallet library. When the library is built as a shared library on x86/x86_64 systems, optimized memory-copy functions can leave secret data (private keys, seed phrases, chain codes) inside special CPU registers (SSE/AVX). If the program then makes a call through the dynamic linker before those registers are reused, the CPU spills the register contents onto the stack, where they may remain uncleared. The patch replaces many ordinary memory copies with a simple, unoptimized byte-by-byte copy function for sensitive data, preventing the data from being left in those registers. The commit message explicitly calls this an 'info leak' and thanks an external contributor for finding the cause and suggesting the fix.

This commit only adds new test cases to an existing test file. It does not change any production code, fix a bug, or alter behavior. The tests check whether sensitive secret bytes are cleared from the call stack after using certain cryptographic functions, which is a defensive security practice, but the commit itself is purely a testing improvement.

This change is a hardening patch for a cryptocurrency wallet library. It tells the compiler to keep certain internal helper functions private to the library, so calls to them stay inside the library instead of going through an external lookup table (the PLT). The commit message says the old route could cause CPU register values containing secret key material to be temporarily saved to the stack, where they might be more easily exposed in a crash dump or memory leak. The patch reduces that risk but does not by itself fix a specific, independently reported vulnerability.

This is a small code cleanup in how a Bitcoin descriptor function counts child nodes. It removes a redundant loop and counts children while already checking them. There is no visible security bug being fixed—just an efficiency and clarity improvement.

This commit is a routine version bump from 1.5.3 to 1.5.4 across build files, documentation, and package metadata. It changes only version strings and constants; no code logic is modified. There is no security-relevant content in the diff.

This commit is a routine build-system version bump. It changes one number in a Makefile from 0 to 1 so the shared library reports version 1.5.4 instead of 1.5.3. There is no code change, no bug fix, and no security relevance visible in the diff.

This commit only updates the project's changelog file (CHANGES.md) to document what is included in the upcoming 1.5.4 release. No actual source code, build scripts, or configuration files were changed. It is a documentation-only release-notes update.

This commit simply swaps the Docker image used by the project's automated CI (continuous integration) pipeline to a newer version. There is no change to the actual library code, no user-facing behavior change, and no security-relevant signal visible in the diff.

This commit simply updates the pinned SHA256 digest of the Debian 'trixie' base Docker image used for building and testing. It is a routine dependency refresh with no code changes and no security-relevant content described by the project.

This commit tightens the unblinding process for confidential asset transactions in the Elements/Liquid sidechain. Previously, the code blindly trusted the decrypted message and did not verify that the extracted asset ID and blinding factor actually match the original cryptographic commitments. The patch adds verification steps: after decryption it re-derives the asset generator and value commitment and compares them to the inputs. If they do not match, it clears the sensitive outputs and returns an error. This prevents a class of attacks where a malicious or malformed blinded output could make the wallet accept an incorrect asset ID or amount.

This commit changes the Java build configuration so that it falls back to Java 8 source compatibility when the compiler does not support Java 17, instead of unconditionally requiring Java 17. It is a build-system compatibility fix, not a security patch.

This commit simply updates the GitHub Actions workflow that builds the JavaScript/WebAssembly package. It changes the build runner from Ubuntu 22.04 to Ubuntu 24.04 and switches the dependency installation script from one named for Debian 'bullseye' to one named for 'trixie'. There is no code change affecting users, no security fix, and no vulnerability introduced.

This commit swaps one way of setting up Microsoft's C++ compiler on Windows in the project's automated wheel-building workflow. It replaces a third-party GitHub Action (msvc-dev-cmd) with a direct call to a Microsoft-provided batch file on the runner. There is no code change that affects the library's behavior, its cryptography, or how it handles user input.

This commit is a routine build configuration update. It changes one line in the project's wheel-building workflow so that Python 3.14 wheels are now built and Python 3.15 wheels are skipped while Python 3.15 is still in beta. There is no security relevance in the change itself.

This commit changes how two fixed lookup tables are written in the source code for the base64 encoding/decoding module. The old form used long string literals made of many hex escape characters; the new form lists individual characters/bytes inside braces. The commit message says the purpose is to silence a compiler warning about unterminated string initialization. The data values in the tables are identical before and after, so this is a code-style/maintenance change, not a security fix.

This is a small build/test configuration change for Java tests. It adds a Java command-line option that suppresses a warning when native (non-Java) libraries are loaded during testing. The change only affects how tests are run and requires Java 20 or newer. There is no indication it fixes or introduces a security vulnerability.

This commit simply changes the Java compiler target version from 1.8 to 17 in the build configuration. It is a routine build hygiene change to silence an obsolete-version warning and does not alter any program logic, cryptographic code, or security behavior.

This commit changes the project's automated build script so that Python wheel and source distribution packages are built in two separate steps instead of one combined step. The commit message says this is a workaround because something in the secp256k1 auxiliary macros breaks when both are built together. The wheel is only used for a quick smoke test; the final artifact they keep is the source distribution. There is no indication this is a security fix.

This commit only reorganizes the project's GitLab CI configuration file. It creates a shared template for test jobs and updates the Docker image used for testing to a newer version. There are no changes to the actual library code, cryptographic logic, or any files that end users install.

This is a tiny CI (continuous integration) maintenance change. It removes a redundant pip install command for a code-coverage tool called gcovr, because that tool is now pre-installed in the test environment. There is no change to the actual library code, cryptography, or anything users interact with.

This commit fixes the CMake build system so it correctly detects several platform features and headers that the library's C code relies on. Before this fix, the CMake build could silently produce a misconfigured library that uses less secure fallback code paths (for example, missing secure memory-zeroing functions or unaligned-access handling). The commit does not change the core cryptographic code itself; it only changes how the build system discovers what the current platform supports.

This commit is a routine update to the project's automated testing configuration for newer Debian 'trixie' tooling versions. It changes CI paths from older GCC 10/Clang 11 tool versions to newer GCC 14/Clang 19 versions, and adjusts the Valgrind test step to run directly on compiled test binaries instead of libtool wrapper scripts. There is no change to the actual library source code, no bug fix, and no security patch.

This commit changes the build configuration so that when building Python packages for 'manylinux' (a standard for portable Linux Python wheels), a failed link check against libpython is ignored. This is a build-system workaround, not a code change, and it does not alter cryptographic behavior, memory handling, or runtime security.

This commit is a build-system fix that changes the order in which automated tests run during 'make check'. It moves the Python wheel-building tests to run last, because building the Python wheel while other tests are running in parallel was causing test failures. There is no security-relevant code change here.