Trezor firmware

This commit changes the Trezor command-line tool so that when a user restores a wallet with fewer than 24 words on older (legacy) Trezor devices, it automatically uses the 'advanced/matrix' recovery method instead of the default 'scrambled words' method. The scrambled method is disabled for shorter mnemonics on legacy firmware, so without this change the recovery command could fail or behave unexpectedly. It is a usability/compatibility fix rather than a fix for a vulnerability that lets an attacker steal funds.

This commit only changes a CI test timeout setting in a GitHub Actions workflow. It increases how long automated tests for one Trezor device model (T3W1) are allowed to run before being cancelled. There is no change to firmware code, cryptography, user-facing behavior, or anything an attacker could exploit.

This is a minor GitHub Actions CI workflow tweak. It adds an extra condition so a job that posts UI comparison comments only runs in the official Trezor firmware repository, preventing harmless failures when the workflow runs in forks or other repositories. There is no product security issue.

This commit only adjusts a hardware test script so it waits longer for the device to respond and checks the correct error code. It does not change the actual Trezor firmware or fix any security bug in the product.

This commit removes an old, duplicated screen called flow_confirm_output and makes the confirm_output function always use the newer confirm_value-based flow. There is no security bug being fixed here; it is a cleanup that unifies how transaction recipient and amount confirmations are shown on newer Trezor device layouts.

This commit fixes a bug in the Trezor hardware wallet's Rust-based THP (Trezor Host Protocol) code where a received message could claim a payload shorter than the checksum length. Before the fix, this caused an integer underflow when calculating how many bytes to feed into the checksum, which could crash or confuse the device. The patch adds an explicit length check and uses a safer subtraction method.

This commit only changes a test file for the Tron cryptocurrency signing feature. It adds 'yield' statements to the test's simulated button-pressing sequence so the test properly waits between simulated user actions. There is no change to the actual Trezor firmware code that users run, and no security fix or vulnerability is present in the diff.

This commit is a routine version bump from 2.10.2 to 2.11.0 for the Trezor firmware. It only changes version numbers in a header file and translation metadata, plus updates the signed translation package fingerprint. There are no code behavior changes, bug fixes, or security patches in this diff itself.

This commit reorganizes how Trezor firmware handles secret keys and the 'secret' subsystem. It splits key-handling code into a new optional component (secret_keys), adds compile-time flags (USE_SECRET and USE_SECRET_KEYS) so different device models can include or exclude these features, and updates the build configuration for every supported model. The change is a structural refactor, not a direct security fix, but it touches sensitive code paths that protect device secrets and storage encryption.

This commit adds a new factory-testing command called secrets-reset that erases the device's secret storage area. It is only compiled into non-production (debug/test) builds, so it cannot be used on normal consumer Trezor devices. The change exposes an internal erase function so the test tool can call it.

This is a routine build-system cleanup for the Trezor hardware wallet firmware. It makes sure that certain device-specific source files (for example, code that talks to a security chip called Optiga, or code that adjusts screen backlight) are only included in firmware builds for devices that actually have those hardware features. There is no indication this fixes a security vulnerability or changes runtime behavior on supported devices.

This commit only updates a test data file (tests/ui_tests/fixtures.json) containing expected hash values for automated UI tests. It does not change any actual firmware, application, or security code. There is no indication this is a security fix or that it affects any user-facing behavior.

This commit is a routine synchronization of translated user-interface text strings for the Trezor hardware wallet firmware. It updates Czech, German, Spanish, French, and Portuguese translation files, plus their signature file, with wording changes, additions, and removals. There is no code logic change, no security fix, and no indication of a vulnerability.

This commit adds a test-only debug feature that lets automated tests restart the Trezor device's main software loop. It is not a normal user feature and only works through the special DebugLink interface used during testing. The change is explicitly for improving backup-failure tests and is marked with '[no changelog]', meaning it is not intended for end users.

This update changes how the Trezor hardware wallet handles unexpected messages while creating a seed backup. Previously, stray or hostile messages (such as a 'Cancel' command) could interrupt the backup process and leave the wallet in an unclear or partially-backed-up state. The fix wraps the backup flow in a new 'continue on errors' mode that ignores unexpected traffic and tells the host the device is busy, so the backup runs to completion. The change is defensive and improves reliability, but it also means a user can no longer cancel a backup from the host side once it has started.

This commit updates Trezor's GitHub CI automation so that branches whose names start with 'secfix/' are treated the same as release branches. It also tightens a couple of upload jobs so they only run in the official repository, and changes one commit-message check to run on any push. The change itself is about build/release plumbing, not a fix for a security bug in the firmware.

This commit only changes the on-screen label shown to Trezor users when confirming TRON transactions. The text 'Maximum Fees' is replaced with 'Fee limit' to match TRON-specific terminology. No transaction logic, fee calculation, or security behavior is changed.

This commit simply turns on Tron (TRX) support in Trezor firmware for all users. It moves Tron code from debug-only builds into normal production builds, updates support lists, and refreshes test snapshots. There is no bug fix or security patch here—just a feature release.

This commit simply renames internal labels used for Tron transaction confirmation screens across different Trezor device layouts. The old names like 'confirm_tron_send' are replaced with newer names like 'tron/send'. There is no visible security change—just keeping naming conventions consistent.

This commit only updates expected visual test snapshots (hashes) for pairing-code entry screens in the Trezor firmware test suite. No actual product code was changed, so it cannot introduce or fix a security vulnerability on its own.

This commit temporarily disables a performance feature called 'THP ACK piggybacking' in Trezor firmware to reduce the chance of triggering an unrelated bug referenced as issue #6506. It is described as a workaround, not a complete fix. The underlying bug can still occur, but only if a network acknowledgment is delayed by more than 200 milliseconds. The change lowers the protocol version minor number from 1 to 0 and stops the device from enabling ACK piggybacking during the handshake. There is no direct evidence in the commit that this is a security vulnerability, and no changelog entry is added.

This commit only changes an automated test for the Trezor hardware wallet. It simplifies how the test puts the device into a 'backup failed' state by starting from a pre-configured test fixture instead of manually running and cancelling a backup. No actual wallet firmware code or user-facing behavior is changed.

This is a minor cleanup change in the Python Trezor library. It removes an internal, underscore-prefixed flag called `_skip_init_device` that was not being used anywhere. The function now always refreshes device features after loading a device. There is no security issue here.

This commit adds a new test-only debug option called `unfinished_backup` to the Trezor hardware wallet's device-loading tools. It lets developers set an internal storage flag that marks a backup as incomplete. The change only affects debug/test code paths and does not alter normal user-facing wallet behavior. There is no indication in the commit that this fixes or introduces a security vulnerability.

This commit changes how Trezor handles Tron cryptocurrency smart-contract payments. Previously, the device used a programming assertion to assume that certain address-padding bytes were zero. Now it checks those bytes at runtime and rejects the transaction if the padding is wrong. The change likely prevents a malformed Tron token-transfer request from being misinterpreted or from causing the device to behave unexpectedly. It is a defensive hardening fix rather than a clear-cut remote exploit patch.