Trezor firmware

This is a routine developer tooling change that improves how code-coverage reports are generated for the Trezor firmware. It makes coverage measurements more accurate by using the same preprocessed source files that are actually compiled into test builds, and avoids redundant rebuilds in CI. There is no user-facing change and no security relevance.

This commit simply updates a Python testing tool called 'coverage' from version 5.5 to 7.13.5. The coverage tool is only used during software testing to measure which parts of the code were executed by tests. It is not part of the actual Trezor device firmware or wallet software that users interact with. There is no indication this update fixes or introduces any security issue.

This is a harmless build-system cleanup. It teaches the firmware build scripts to remove haptic (vibration) and RGB LED code from devices that do not have those hardware features, and it sorts the list of feature flags alphabetically for easier reading. There is no security bug being fixed here.

This commit is a code refactor in Trezor's Rust THP (Trezor Host Protocol) library. It moves responsibility for assigning channel IDs from the internal library mux to the application using the library. The change also removes the requirement that credential stores/cloners implement the Clone trait, and adds a helper allocator for consecutive channel IDs. There is no direct evidence in the commit or supplied references that this fixes an active security vulnerability; it appears to be an architectural cleanup that may make misuse harder but also places more correctness burden on the application.

This commit is a straightforward code cleanup in the Trezor firmware's Rust implementation of the Trezor Host Protocol (THP). It replaces repeated uses of a generic type `Channel<Host, B>` or `Channel<Device, B>` with shorter type aliases `Channel<B>` inside the host and device channel modules. No behavior of the code changes, and there are no security implications.

This commit adds a new 'reset' method to two internal Rust channel objects in the Trezor firmware's THP (Trezor Host Protocol) code. The method simply restores the channel to its freshly-created state, discarding any pending messages or connection bookkeeping. There is no indication in the commit that this fixes a security bug; it reads as a routine code cleanup or preparation for future use.

This commit is a code cleanup in Trezor's secure transport layer. It centralizes how error messages are sent and removes an outdated workaround where the device had to manually craft an error packet. The change also makes decryption failures on the device side send a proper error response instead of silently closing the channel. There is no indication this fixes an active security vulnerability; it appears to be a refactoring and robustness improvement.

This commit refactors how a Trezor hardware wallet's Rust-based secure channel code remembers whether a pairing handshake succeeded. It moves the pairing-state information from a temporary handshake object into the long-lived channel object, adds a check that the handshake is fully done before completing, and exposes the remote device's public key and pairing state to the rest of the application. The changes look like a defensive cleanup rather than an active vulnerability fix, but they close a small window where pairing state could be lost or queried incorrectly.

This commit refactors the internal state tracking of the Trezor hardware wallet's THP (Trezor Host Protocol) Rust code so the channel can count how many times it has retransmitted a message. It also exposes that retry count to callers and adds a helper function for calculating how long to wait before retrying. The change is defensive: it makes the protocol more observable and easier to limit in the future, but it does not by itself fix a known exploitable bug.

This commit only changes how numbers appear in log messages for the Trezor hardware protocol (THP) Rust code. It switches decimal formatting (e.g., '123') to hexadecimal formatting (e.g., '0x7b') for control bytes, channel IDs, and error codes. There are no functional code changes, no security fixes, and no behavior changes.

This commit only fixes typos and duplicated words in code comments. No actual program code was changed, so it cannot affect device behavior or introduce security issues.

This commit simply adds a new firmware version number (2.11.1) to a release metadata file. It is a routine administrative update with no code changes and no security relevance visible in the diff.

This commit simply adds a new digital signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. There is no code change, no bug fix, and no visible security issue. It appears to be routine release housekeeping: signing the translation data for firmware version 2.11.1.0.

This commit only updates a timestamp and a matching version number used for Ethereum network definition files. There are no code logic changes, no bug fixes, and no security-related modifications visible in the diff.

This commit replaces a binary file called secmon.bin for the T3W1 hardware model. The file is a compiled security monitor firmware image, but the actual code changes inside it are not visible in the commit. There is no description of any security fix or vulnerability, so we cannot determine from this commit alone whether it addresses a security issue.

This commit is purely a documentation change: it assembles the release notes for Trezor firmware version 2.11.1 by moving text fragments from temporary changelog files into the final Markdown changelogs. No source code, cryptographic logic, or device behavior is modified, so it cannot introduce or fix a security vulnerability on its own.

This commit moves an Ethereum feature called "stablecoin yielding" from debug-only mode into production. It adds user-interface flows for certain ERC-4626 vault interactions, such as depositing USDC into a yield-bearing vault. The change itself is a feature promotion, not a fix for a known security flaw. There is no evidence in the commit that it addresses an active vulnerability or that it introduces one.

This commit expands Trezor's Ethereum 'clear signing' support to include ERC-4626 vault withdraw and redeem transactions, not just deposits. For transactions where the receiver or owner differs from the signer on an unknown vault, the device now falls back to blind signing instead of refusing outright. For known Trezor-listed vaults, mismatches still trigger a hard error. The change is a feature addition with intentional security trade-offs rather than a clear-cut vulnerability patch.

This commit only changes user-facing text strings and their translation metadata for Ethereum vault (ERC-4626) screens. It adds labels like 'Redeem', 'Claim to', 'Withdraw amount', and removes unused strings like 'Your address'. There is no code logic change, no security fix, and no vulnerability introduced.

This commit updates a bundled third-party library called libtropic from version 3.1.0 to version 3.2.1 inside the Trezor firmware repository. The actual code changes are not visible because only a submodule pointer was changed (one line modified in the vendor/libtropic path). There is no information in the commit itself saying this fixes a security problem, and no independent references were provided. On its own, this looks like a routine maintenance update.

This is a small internal code cleanup in the Trezor firmware's user interface code. It renames a variable and ensures a temporary layout object is properly cleaned up after use. There is no indication this fixes a security vulnerability or introduces one.

This is a tiny code cleanup that wraps a UI menu layout call in a Python `with` statement so the object is automatically cleaned up after use. The commit message suggests it may help prevent an out-of-memory (OOM) crash during automated tests, but it does not describe a security vulnerability and no exploit path is visible.

This commit is a small code cleanup in the Trezor hardware wallet's user-interface code. It changes how on-screen payment-request confirmation dialogs are created and destroyed, wrapping them in a 'with' block so they are cleaned up promptly. The developer notes this may be related to an out-of-memory (OOM) issue seen in automated tests, but the commit does not claim to fix a security vulnerability and no independent security references are provided.

This commit is a straightforward internal refactoring that adds a new Rust logging bridge. It does not change any security-critical behavior: logging is already disabled in release builds, and the new code is only compiled into debug builds. There is no indication this fixes or introduces a security vulnerability.

This commit fixes a logging bug in Trezor firmware's debug console output. Previously, the code used a width specifier to print a log source name, which could read past the end of a string that isn't null-terminated. The fix switches to a precision specifier that respects the known length. This is a defensive correctness fix in debug-only logging code; there is no direct evidence it is exploitable as a security vulnerability.