Ledger Bitcoin app

This commit only changes a CI/testing Docker image used for Ledger's automated test environment. It adds common development tools (build-essential, curl, git) and slightly reorganizes apt commands. There is no indication this affects the actual Bitcoin app that runs on Ledger devices or end-user security.

This commit only updates automated test scripts to use a different Bitcoin Core RPC command for checking wallet balances. It does not change the Ledger app code that users interact with, and it has no security relevance.

This commit simply swaps the name of a test container used in automated CI testing. It changes one line in a GitHub Actions workflow file, switching from a custom 'speculos-bitcoin-musig2' container to a standard 'speculos-bitcoin' container because Bitcoin Core now supports MuSig2 natively. There is no change to the actual app code, no user-facing behavior change, and no security-relevant content.

This commit changes a CI Dockerfile used to build Bitcoin Core for testing. It adds a build flag that disables Bitcoin Core's optional multiprocessing (IPC) feature because the build environment lacks the required dependencies. This is a build-configuration convenience change, not a security fix for the Ledger app itself.

This commit only changes automated test code for the Bitcoin app's message-signing feature. It adds a new test for messages containing a line feed (LF) character and updates an existing test to use a carriage return (CR) instead of a line feed. There is no change to the actual app code that runs on the Ledger device, so this commit does not introduce or fix a security vulnerability by itself.

This commit changes how the Ledger Bitcoin app decides whether a message being signed is 'printable' on the device screen. It now allows the Line Feed (newline) character to pass through, because the newer NBGL screen library can display multi-line text. Previously, any character outside the normal visible ASCII range would make the message be shown as a hex dump instead of readable text. The change is a small UI/UX improvement for message signing and does not appear to alter the actual cryptographic signature.

This commit only updates test screenshot snapshots (expected device screen images used in automated testing). It does not change any application code, firmware logic, or user-facing behavior. The title refers to a prior change that removed warnings for unusual Bitcoin key derivation paths; this commit merely refreshes the test images to match that earlier change.

This commit only changes test helper code, not the actual Ledger Bitcoin app that users run. It removes a special test-only shortcut for handling 'suspicious derivation path' warnings and replaces it with more explicit test button presses. There is no direct evidence in the commit that a real security vulnerability was fixed.

This commit removes a warning screen that previously appeared when a Bitcoin public key was requested for an unusual or non-standard derivation path. Without the warning, users may be less likely to notice if malicious software asks their Ledger device to reveal keys for a suspicious path. The change itself is a deliberate feature removal, not a hidden bug, but it weakens a user-facing safety check.

This commit only updates test screenshot images (snapshots) for the Ledger Bitcoin app's message-signing user-interface tests. It does not change any application source code, cryptographic logic, or device behavior. The snapshots reflect a switch to the 'classical NBGL API' for message signing, but this is a test-asset update, not a security-relevant code change.

This commit only updates automated test scripts for Ledger's Bitcoin app. It changes how on-screen button presses are simulated during message-signing tests on newer touch-screen devices, switching from one generic test helper to more specific tap coordinates. There is no change to the actual wallet application code that users run, so this cannot directly affect user funds or security.

This commit refactors how the Ledger Bitcoin app displays messages before signing. It replaces a streaming, paginated message-review flow with a single-page review using the standard NBGL API. The change increases the maximum message that can be shown from about 128 bytes to roughly 640 bytes, and removes the intermediate 'loading' start page. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a user-interface simplification. However, any change to the confirmation screen logic can affect whether users correctly see what they are signing, so it warrants careful review.

This commit only updates test screenshot snapshots (PNG images) for the Ledger Bitcoin app. It does not change any application source code, so it cannot directly affect the security of the app or user funds. The images are used by automated tests to verify that the device's on-screen prompts look as expected when signing transactions.

This commit only updates the automated test framework for the Ledger Bitcoin app. It changes how tests simulate button presses on the device screen, renames some test helper functions, and adds new test cases for transactions with many outputs and for navigating back and forth during signing. There is no change to the actual app code that runs on the Ledger device, so this commit does not introduce or fix a security vulnerability in the product itself.

This commit is a minor user-interface wording change. It replaces the generic spinner text 'Signing' with the more descriptive phrase 'Signing transaction' shown while the device is computing a Bitcoin transaction signature. There is no change to cryptographic logic, transaction validation, or security behavior.

This commit refactors how the Ledger Bitcoin app displays transaction details on newer devices (Stax/Flex/Apex). It replaces a streaming, one-output-at-a-time review flow with a non-streaming 'simplified' flow for transactions with up to 16 external outputs, unifies warning messages, and moves warning screens to appear before the main transaction review. The changes are primarily a user-interface restructuring rather than a clear security fix, but they do widen the simplified-review path from 0/1 external outputs to up to 16 and change the order/timing of user warnings.

This commit changes how a cryptocurrency amount is formatted on screen during a swap operation. Previously the coin ticker (like 'BTC') appeared before the amount; now it appears after. The change also replaces hard-coded number 8 with a named constant and uses a safer array initialization. There is no direct evidence this fixes a security vulnerability.

This commit only changes the version of a testing container used in the project's automated CI workflow. It freezes the Speculos emulator image from 'latest' to a specific older version (0.25.5) because the test suite still uses an old Nano S Bitcoin binary that newer Speculos versions no longer support. There is no change to the actual Bitcoin app code, no user-facing change, and no security fix or vulnerability introduced.

This commit only changes a GitHub Actions CI workflow file. It adds a manual option for developers to automatically update test snapshot images when running tests, rather than failing the build. There is no change to the actual Bitcoin app code, no user-facing behavior change, and no security relevance.

This commit only updates test screenshot images (called 'Ragger snapshots') for the Ledger Bitcoin app. No actual application code, transaction logic, or security behavior was changed. It is a routine test-maintenance update and does not affect users' funds or security.

This commit only removes an old developer comment (a 'TODO' note) about a possible future feature. No actual code behavior changes, so it has no security effect on its own.

This commit fixes a defensive coding issue in the Ledger Bitcoin app. A function that derives a secret key from a text label could overflow an internal 32-byte buffer if given a label longer than 32 bytes. In practice, the app only ever passed one fixed short label, so the overflow was not reachable from normal use. The patch now rejects oversized labels and also handles the rare failure case when generating a wallet security code (HMAC).

This commit only updates three test snapshot images for Ledger device screens. These are reference pictures used in automated testing to check that the app's user interface displays correctly. No application code, firmware logic, or security-sensitive files were changed.

This commit only adds 390 PNG image files used for automated testing of the Ledger Bitcoin app on a new device variant called 'apex_p'. These are screenshot snapshots that the test suite compares against expected device screens. No application code, no firmware logic, and no user-facing behavior were changed. There is no security risk visible in this commit.

This commit only bumps the app's version number from 2.4.1 to 2.4.2 and updates the changelog to note 'Apex P porting'. There are no code changes, no security fixes, and no functional modifications visible in the diff.