Ledger Bitcoin app

This commit only adds new automated unit tests for Merkle-tree helper functions in the Ledger Bitcoin app. It does not change any production firmware code, so it cannot by itself introduce a security vulnerability or fix one. The tests exercise functions that verify Merkle proofs, retrieve leaf data, and stream key-value map entries.

This commit only adds a new testing feature to the unit-test mock dispatcher. It lets test authors simulate a malicious client that tampers with protocol responses. It does not change the actual Ledger Bitcoin app code, does not introduce a real vulnerability, and is not a security fix. It is purely test infrastructure.

This commit only adds new unit tests that simulate a malicious or buggy companion app sending bad data to the Ledger device. It does not change the actual security code being tested. The tests check that the device-side functions correctly reject corrupted Merkle proofs, wrong leaf indices, bad preimage lengths, and interrupted communications. Because no production code is modified, the commit itself does not introduce or fix a vulnerability; it improves test coverage for existing defensive behavior.

This commit is a small cleanup following a code review. It updates comments, adds safety checks to a test-only mock function, increases a test mock queue size, and adds a missing standard header include. None of the changes affect the real device firmware's security behavior.

This commit only adds new unit tests to the Ledger Bitcoin app. It does not change any production code, so it cannot introduce a security vulnerability or fix one directly. The tests exercise edge cases and adversarial inputs for functions that handle Merkle-tree preimages and BIP32 derivation extraction, which helps confirm existing defensive checks reject malformed data.

This commit only adds new automated unit tests for two existing functions in Ledger's Bitcoin app. It does not change the actual app code that runs on devices, so it cannot introduce a security vulnerability or fix one by itself. The tests check that the functions correctly fetch and decode data from tamper-evident Merkle trees and reject malformed or corrupted inputs.

This commit is a routine cleanup of the project's unit-test code. It removes duplicate mock implementations of a small helper function called `pic()` from 14 test files and places a single shared version in a mock header. The change only affects test code, not the actual Ledger Bitcoin app that runs on devices. The commit message says the cleanup was done to fix confusing code-coverage measurements. There is no indication this fixes a security vulnerability or changes how the app behaves.

This commit is a pure refactoring of the project's unit tests. It replaces manually initialized static mock dispatcher objects with heap-allocated ones managed by cmocka test fixtures, and moves hash-pool reset into the common setup function. There is no change to the actual Ledger Bitcoin app firmware or its security-critical code, so this commit does not introduce or fix any user-facing security vulnerability.

This commit removes a single line from a GitHub Actions CI workflow file. The removed line disabled a JFrog deployment option for a Python package publishing job. It is a routine build/pipeline configuration fix with no apparent security relevance.

This commit removes a PyPI (Python package publishing) API token from a public GitHub Actions workflow file. The change itself is a cleanup step, likely after the token was exposed or no longer needed. It does not show whether the token was ever valid, leaked, or misused, but removing exposed credentials is a standard security hygiene measure.

This commit is a straightforward code cleanup: it extracts a repeated block of code into a shared helper function. Two existing functions that previously each had their own nearly identical loop now call the helper instead. There is no change to what the code does, only to how it is organized.

This commit is a performance optimization for the Ledger Bitcoin app. It reorders nested loops in two signing-related functions so that the app reads each transaction input's data once and then processes all relevant internal keys, rather than re-reading the input data once per key. The commit message and diff show no functional change—only a reduction in redundant work.

This commit is a small performance refactor inside the Ledger Bitcoin app. It moves the calculation of a Taproot tree hash (used for advanced multi-signature scripts) so it only runs when actually needed, rather than once per input unconditionally. There is no direct evidence this fixes a security bug; it appears to be an optimization, though it slightly reduces the chance of unnecessary computation or state errors.

This commit removes unused network port mappings from GitHub Actions CI configuration files. It is a routine infrastructure cleanup to reduce random test failures when CI containers start up. It does not change any application code, cryptographic logic, or user-facing behavior, and it does not fix a security vulnerability.

This commit only changes a version number in a packaging file from 0.6.1 to 0.6.2. The stated reason is to re-run the publishing process so the package page on crates.io includes the README file. No program code was modified, and there is no security relevance.

This commit only adds a GitHub CODEOWNERS file that assigns the embedded-apps-bitcoin team as the default reviewer for all changes. It does not modify any application code, build scripts, or security-sensitive configuration.

This commit removes an old, unused code path that handled device communication when a newer 'revamped' input/output system was not enabled. The change only deletes code that was already guarded by a compile-time flag and no longer used, with no functional change to the active system.

This commit only changes automated test files. It forces the test transactions to use Bitcoin transaction version 2 so that a test helper called combinepsbt works correctly. There is no change to the actual Ledger app code that users run, and no security fix or vulnerability is present in the diff.

This commit swaps the library's standard variable-length integer type for a custom one in Ledger's Bitcoin app client code. The change is needed because a newer version of the rust-bitcoin library started rejecting large varints that the Ledger protocol legitimately uses for non-Bitcoin data. The patch itself is a compatibility fix, not an obvious vulnerability, but it removes a safety boundary and any bugs in the new custom encoder/decoder could affect how the client talks to Ledger devices.

This commit only changes a version number in a package configuration file from 0.6.0 to 0.6.1. There is no code change, no bug fix, and no security-related content visible in the diff.

This commit only changes GitHub CI workflow settings. It turns on two build-reporting features: comparing compiled outputs across builds and reporting how much stack memory the app uses during tests. There is no change to the actual Bitcoin app code, no bug fix, and no security patch.

This commit removes two lines from a GitHub Actions CI workflow file. It disables a JFrog deployment step and stops passing a Cargo crate publishing token to that workflow job. There is no change to the actual Bitcoin app code, cryptography, or anything users install on their Ledger devices. It is purely an internal adjustment to how a Rust client library crate is published.

This commit fixes a missing safety check in Ledger's Bitcoin app when handling newer 'V2 wallet policies.' The app was told in advance how long the wallet policy data should be, but it never verified that the actual data matched that length. The fix adds a simple comparison: if the lengths don't match, the app now rejects the request. The commit credits Rob Hamilton for reporting the bug, but no public security advisory or CVE is included in the materials.

This commit adds a new GitHub Actions workflow file that automatically creates a GitHub release whenever a version tag like '1.2.3' is pushed. It calls a reusable release workflow maintained by Ledger. There is no change to the Bitcoin app code, device firmware, or any user-facing security behavior. It is purely a CI/CD automation addition.

This is a tiny consistency fix in the JavaScript client for the Ledger Bitcoin app. It changes one number in a command that resumes interrupted operations so it matches the Python and Rust clients. The app already ignores this version number for this specific command, so the change is unlikely to have any security effect on its own. It mainly removes an unexplained difference between client implementations.