Trezor firmware

This commit is a simple revert of a previous test-only change. It modifies one Python test file to go back to an older way of looking up translated strings during automated device tests. There is no change to the actual Trezor firmware code that runs on the hardware, so this cannot affect real users or device security.

This commit only updates a test file so that automated tests can correctly look up translated button labels for different device screen layouts. It does not change the actual Trezor firmware or any user-facing behavior, and it is not a security fix.

This commit only changes a test file. It adds a helper function to scroll through multi-page on-screen messages during automated PIN and wipe-code setup tests. There is no change to the actual Trezor firmware or wallet behavior, so it does not create or fix a security vulnerability in the product users rely on.

This commit only shortens and updates translated user-interface text in Spanish, French, and Portuguese translation files, plus refreshes the translation signature metadata. There are no code, logic, cryptographic, or security changes.

This commit simply removes a handful of unused translation text strings from non-English language files. There is no code change, no security fix, and no user-facing behavior change. It is a routine cleanup.

This is a tiny change to a single test file. It makes a test more tolerant of how spaces appear in on-screen text by ignoring spaces when comparing expected and actual text. There is no change to the actual Trezor firmware or wallet behavior, and no security issue is present.

This commit only updates the expected visual test snapshots (called 'fixtures') used by Trezor's automated UI testing suite. It does not change any firmware, application, or cryptographic code. The hash values in the fixtures file changed because the on-screen text, layout, or rendering was updated in a previous code change, and now the test expectations are being refreshed to match. There is no direct security relevance in this commit itself.

This commit only changes a test file. It updates helper functions in the language-related device tests to use a new shared translation lookup helper instead of reading language JSON files directly. There is no change to the actual Trezor firmware, wallet application, or any code that runs on the device. It is purely a test-code cleanup and does not affect user security.

This commit is a routine update of user-facing text translations for the Trezor firmware. It changes wording in multiple languages, adds new translation keys for upcoming features (such as Bluetooth and new device screens), and replaces a non-breaking space with a regular space in a few English strings. There is no code logic change and no security-relevant behavior is altered.

This commit tightens the rules for a Trezor message type called TextDetailsMemo, which is part of the SLIP-24 payment-request memo format. Previously the title and text fields were optional and defaulted to empty strings; now both are required. The change is defensive: it prevents a device from accepting a payment-request memo that omits the title or body text. Without this, a malicious or buggy host could send a payment request with an empty/incomplete memo and still have it treated as a valid TextDetailsMemo, potentially misleading the user about what they are approving.

This commit simply adds a new hardware model code (T3W1) to the list of default models in a build helper script. It changes two lines: the help text and the default model array. There is no security-relevant change visible in the diff.

This commit simply updates the version (revision) of an embedded bootloader component called MCUboot used in Trezor's Nordic-based products. The change is a one-line pointer update in a project manifest file, moving from one tagged internal revision to another. There is no description of a security problem, no patch to Trezor's own code, and no supplied references indicating this is a security fix.

This commit updates a small Python helper script used to display a fingerprint (a kind of checksum) for Trezor firmware files. It adds support for a newer bootloader image format (BootloaderV2) so the tool can handle both old and new formats. There is no direct evidence this change fixes a security vulnerability; it appears to be a feature/robustness improvement for a developer tool.

This is a small build-tool change that makes a helper script print the correct cryptographic fingerprint for a special 'prodtest' firmware image. It does not change any code that runs on the Trezor device itself, does not introduce any security vulnerability, and is not described by the vendor as a security fix.

This commit removes automatic Debug printing support from several Rust data structures in the Trezor firmware's production builds, keeping it only for unit tests. It is a code hygiene or size-reduction change with no visible security relevance.

This commit removes an unused import (`use std::vec::Vec;`) from a Rust test module in the Trezor firmware codebase. It is a routine code cleanup with no functional or security effect.

This commit is a code cleanup in Trezor's internal production-test tooling. It moves an existing factory-session startup routine into its own reusable function and exposes it through a new header file. No new behavior is added, no new keys are introduced, and no user-facing or wallet security feature is changed. The production factory pairing key remains compiled into the prodtest binary, which is unchanged from before this commit.

This commit changes how secret keys are generated during Trezor device production testing. Previously, randomness came from the device's own RNG and (on some models) an Infineon OPTIGA chip. The patch adds support for also mixing in randomness from a new 'Tropic' secure chip, and ensures a factory secure session with Tropic is started before secrets are generated. This is a feature addition, not a vulnerability fix. It improves entropy quality but introduces a new hardware dependency and a TODO-removal that should be reviewed for correctness.

This commit increases the memory reserved for the production-test firmware's call stack from 24 KB to 128 KB and moves it from MAIN_RAM to AUX1_RAM. The stated reason is to support ML-DSA (a post-quantum digital-signature algorithm) operations that need more stack space. A stack that is too small can trigger a UsageFault crash; the change prevents such crashes during production testing. There is no direct evidence in the commit that this fixes an exploitable security vulnerability, but running with an undersized stack can in some cases lead to memory corruption or unstable behavior.

This commit swaps the cryptographic algorithm used for one of the Trezor hardware wallet's internal device-attestation keys from Ed25519 to ML-DSA-44, a post-quantum NIST-standardized signature scheme. It also enlarges the certificate storage area and doubles the production-test command-line input buffer. There is no direct evidence in the commit of a security vulnerability being fixed; it reads as a planned cryptographic modernization change.

This commit updates Trezor's production-test firmware to accept multiple trusted public keys from secure hardware modules (HSMs) instead of just one. It also adds a helper function in the Noise crypto library that tries each trusted key in turn during a secure handshake. The change itself is a feature addition, not an obvious bug fix. However, the helper function restores a sensitive temporary key from a backup on every retry, which is good practice, and it wipes the backup when done. There is no direct evidence in the commit that this fixes a security vulnerability; it looks like operational hardening for factory testing.

This commit is a build-script change that adds an optional way to compile firmware for a new Trezor Bluetooth chip (nRF) inside the existing Docker build tool. It does not change any wallet code, cryptography, or device behavior. There is no security issue visible in the diff.

This commit updates the project's build dependency files (poetry.lock, pyproject.toml, shell.nix) to add tools needed for nRF microcontroller work. It is a routine build-environment change, not a fix for a security vulnerability. The only security-relevant note is that it pins several new Python packages, which is good practice, and it removes one unused tool (nrf-command-line-tools) from the development shell.

This commit changes a build script for Trezor's Nordic (nRF) hardware so it can automatically detect whether it is running inside a Docker/Nix build environment or a local developer's machine, and then run the build command the appropriate way. It is a build-system convenience change with no visible security relevance.

This is a minor code cleanup that changes how a helper function's input type is described. It makes no functional change to what the code does and does not affect security.