Ledger Bitcoin app

This commit is a routine maintenance change to the project's unit tests. It updates the test build system to use shared utility code from the Ledger SDK instead of local copies, deletes tests for functions that now live in the SDK, and adds a couple of new test cases for wallet policy parsing. There is no change to the actual Bitcoin app code that runs on the device, and nothing in the commit suggests a security fix or vulnerability.

This commit is a large refactoring that replaces many locally-implemented utility files (for parsing APDUs, buffers, base58, BIP32, varints, read/write helpers, etc.) with equivalent files from Ledger's official SDK library (lib_standard_app). It also renames some local files (e.g., io.c -> io_ext.c, buffer.c -> buffer_ext.c) to hold only app-specific extensions. The change itself is not a security patch; it is a code-maintenance / deduplication move. However, any large-scale dependency switch can introduce subtle behavioral differences or regressions, so it warrants careful review rather than alarm.

This commit only changes the project's GitHub Actions workflow file. It replaces an inline CodeQL security-scanning job with a call to a shared, reusable workflow maintained by Ledger. No application source code, cryptographic logic, or user-facing behavior is modified. There is no direct security vulnerability in this change.

This commit only reorganizes how automated unit tests are run in the project's GitHub CI pipeline. It removes the inline unit-test job from one workflow file and replaces it with a call to a shared Ledger reusable workflow. No application code, cryptographic logic, or user-facing behavior was changed. There is no security-relevant change visible in the diff.

This commit only edits the changelog text: it updates a release date and capitalizes some bullet points. No code was changed, so it cannot by itself introduce, fix, or exploit a security issue. The changelog does mention that version 2.4.5 fixes a signing bug and changes a derivation flag, but those actual code changes are not present in this diff.

This commit fixes two bugs in the Ledger Bitcoin app's data-receiving code when large messages are split into multiple chunks. One bug caused the app to hash and copy from the wrong memory location after the first chunk, potentially corrupting a cryptographic proof. The other bug could read corrupted data or behave incorrectly if an empty chunk arrived, or if a taproot PSBT field started with a very large variable-length integer. These are memory/data-integrity issues in security-critical signing code, but the commit does not state they are exploitable for theft.

This commit adds an automated GitHub Actions job to publish the Rust Bitcoin client library to a package registry (including JFrog) when a version tag is pushed. It also changes the package author metadata from an individual contributor to 'Ledger' and adds a README acknowledgement for that contributor. There are no code changes to the library itself and no apparent security implications.

This commit fixes two spelling mistakes: one in the changelog ('jome' to 'home') and one in a code comment ('In te case' to 'In the case'). No program logic, security behavior, or functionality was changed.

This commit changes a single setting in the project's automated CI workflow. It stops GitHub from automatically creating a new GitHub Release every time a new Python package is published to PyPI. This is a workflow/process change, not a code change affecting the app, wallet, or any security-sensitive functionality.

This commit only adds documentation to the README explaining how maintainers should create release tags to trigger automatic publishing of the Python, JavaScript, and Rust client packages. No code, configuration, or security behavior was changed.

This commit adds a new automated GitHub Actions job that builds and publishes a Python package to PyPI whenever a Git tag starting with 'pyclient' is pushed. It is a routine CI/CD configuration change with no apparent security relevance.

This commit is a routine packaging and publishing cleanup for the JavaScript client. It renames the npm package from 'ledger-bitcoin' to '@ledgerhq/ledger-bitcoin', updates the README and package-lock.json accordingly, and moves the JS client deployment from a separate workflow triggered on pushes to the 'develop' branch into the main CI workflow triggered only by tags starting with 'jsclient-'. There is no change to the Bitcoin app firmware, cryptographic code, or any user-facing security behavior.

This commit simply changes a GitHub Actions workflow to point at the correct, stable version of a reusable deployment workflow. It is a normal repository hygiene fix with no security relevance visible in the diff.

This commit is a packaging and publishing workflow change for Ledger's Bitcoin JavaScript client. It adds a GitHub Actions workflow to publish the package to JFrog and npm, renames the package from 'ledger-bitcoin' to '@ledgerhq/ledger-bitcoin', removes ESLint tooling, and adjusts published files. There is no direct evidence of a security vulnerability in the code changes, but the workflow pins to a non-default branch of a reusable workflow ('mbr/reusable-workflow-jfrog-npm') and removes linting tools, which slightly weakens supply-chain assurance.

This commit only updates three test snapshot images used by an automated testing tool called Ragger. These snapshots are expected outputs of UI screens during automated tests. There are no code changes, no application logic changes, and no security-relevant modifications.

This commit is a routine version bump from 2.4.4 to 2.4.5. It only updates the version number in the Makefile and adds a changelog entry describing unrelated feature and bug-fix changes. There is no code change in this commit itself, and nothing in the diff indicates a security vulnerability or security fix.

This commit only adds a new automated test case to the project's test suite. It checks that the Ledger Bitcoin app can display and return an extended public key (xpub) for a specific non-standard key path when the user approves on the device screen. There is no change to the actual app code, no security fix, and no vulnerability being introduced.

This commit only updates test snapshot images used by an automated testing framework called Ragger. These are reference screenshots of Ledger device screens during tests. No application code, firmware, or user-facing behavior was changed, so this has no security relevance on its own.

This small code change fixes how the Bitcoin app builds extended public keys (xpubs) for the very first account level (called 'L1', meaning a BIP32 path with just one number, like m/44'). Before, the code always tried to look up a parent public key one level above the requested path. For a single-level path, there is no usable parent above it except the master key, so that lookup could fail or behave incorrectly. The patch adds a special case: when the path has exactly one element, it uses the master key's fingerprint as the parent fingerprint instead of trying to derive a non-existent parent. This is a correctness/reliability fix rather than an obvious security vulnerability, but a broken xpub could mislead wallet software about which key hierarchy it is dealing with.

This commit fixes the on-screen name shown for a special 'Bitcoin Recovery' version of the Ledger Bitcoin app and removes some old, duplicated menu code. It is a user-interface cleanup, not a fix for a vulnerability that could steal funds or keys.

This commit re-enables a build flag for a special 'bitcoin_recovery' app variant that lets it derive any key path, including non-hardened ones. The change is intentional and limited to a recovery/debug variant, not the main Bitcoin app. It is not a vulnerability by itself, but it removes a restriction on a variant that already had broad permissions, so it slightly increases the risk surface if that variant is misused or compromised.

This commit only updates three test snapshot images used by the Ragger testing framework. These are reference screenshots for automated UI tests on Ledger hardware device simulators. No application code, firmware logic, or security-sensitive files were changed.

This commit is a routine version bump from 2.4.3 to 2.4.4. It only updates the version number in the Makefile and adds a changelog entry describing two newly allowed Bitcoin derivation paths. There are no code changes in the diff, so it does not introduce, fix, or alter any security-relevant behavior on its own.

This commit only updates test screenshot images used by an automated testing tool called Ragger. No application code, firmware, or user-facing behavior was changed. It has no security relevance on its own.

This commit only adds and updates automated tests for the Ledger Bitcoin app's extended public key feature. It does not change any application code, cryptographic logic, or security behavior. The tests verify that certain Bitcoin derivation paths (including Electrum and BIP-45 style paths) are accepted or rejected as expected. There is no indication of a security fix or vulnerability being patched.