Trezor firmware

This commit is a routine feature addition to an internal production-test tool used during hardware manufacturing. It expands a stress test for the Tropic secure chip to also exercise chip initialization and random-number generation, and it cleans up how the emulator build chooses a network port for the simulated Tropic chip. There is no indication this fixes a security vulnerability or introduces a security-relevant weakness.

This commit removes a small piece of Python code in Trezor's host-side library that automatically bundled low-level transport acknowledgements with every device call. The change is labelled as a routine cleanup ('chore') and explicitly says it has no changelog entry. There is nothing in the diff or commit message that indicates a security fix, vulnerability, or behavior change visible to users.

This commit refactors how the Trezor Python client handles low-level 'ACK' messages during encrypted THP communication. It replaces a single-workflow marker with a stack of nested contexts so multiple sessions can share a channel without sending duplicate acknowledgements. The change is a feature/cleanup, not a security fix, and does not appear to introduce a vulnerability. It mainly touches test helpers and the THP transport layer.

This is a small internal cleanup in Trezor's Python library. It moves the 'refresh device info' and 'invalidate client' steps into a shared decorator so they happen after a workflow finishes, rather than inside each individual function. The stated reason is to avoid unnecessary re-transmissions in the new THP (Trezor Host Protocol) when an ACK is piggybacked. There is no direct security bug being fixed; it is a reliability/refactoring change.

This commit re-enables a feature called 'THP ACK piggybacking' in Trezor firmware. It is a feature change, not a security patch. The commit message and diff do not describe any security vulnerability or fix. The change was previously disabled due to an unrelated issue (#6506) that is now apparently resolved. Without additional references, there is no direct evidence this commit fixes a security problem.

This commit adds a new 'BackupMethod' setting to Trezor's device communication protocol. It lets the wallet software tell the device how to handle backup or recovery of the secret recovery words. The change only defines the new enum and wires it into three messages (ResetDevice, BackupDevice, RecoveryDevice); it does not add any actual backup/recovery behavior. There is no security fix or vulnerability visible in this patch.

This commit is a documentation-only update to the production-test changelog. It records that an optional amplitude argument was added to a haptic (vibration) test command for two Trezor device models. There is no code change, no security fix, and no security-relevant behavior change.

This commit updates a factory-testing command used only in Trezor's internal production-test firmware. It adds an optional amplitude parameter (0-100) to the haptic-test command so testers can vary vibration strength. There is no user-facing change, no normal wallet firmware impact, and no security relevance visible in the commit.

This commit adds support for native Solana (SOL) payment requests using the SLIP-24 standard on Trezor hardware wallets. It extends existing token payment-request logic to also cover plain SOL transfers, and updates tests and UI fixtures accordingly. There is no direct evidence in the commit of a security vulnerability, but any change to payment verification and confirmation flows carries a low level of implementation risk.

This commit adds a smoother, momentum-based scrolling effect to long menus on the Trezor T3W1 hardware wallet. It is a user-experience improvement, not a security fix. There is no indication it addresses a vulnerability or that an attacker could exploit it.

This commit changes how a Trezor hardware wallet decides whether its USB connection is truly active, especially for battery-powered models. Previously, the code assumed the device was USB-powered and treated a suspended USB state as still 'configured' and ready. The patch makes that behavior depend on actual power-manager data and a remembered 'was configured' flag, so the device no longer falsely reports itself as ready when it may not be. This is a hardening/robustness improvement rather than a clear-cut fix for an exploitable vulnerability.

This commit adds pagination support for listing WebAuthn (FIDO2) resident credentials stored on a Trezor device. Previously, the device returned all credentials in one message, which could hit size limits. Now the host can request credentials in smaller batches. There is no obvious security bug in the change; it is a feature addition with a small, well-scoped protocol change.

This commit only changes the protocol definitions (the message formats) used for listing WebAuthn resident credentials. It adds an optional batch size, a flag indicating whether more credentials are available, and a new acknowledgment message so the host can request the next batch. There is no actual implementation of the pagination logic in the firmware or host code in this commit, and nothing in the commit suggests a security vulnerability. It appears to be a normal feature addition to support paginated credential listing.

This commit simply changes the default hardware model name used when building the Trezor firmware from 'T2T1' (Model T) to 'T3W1' (a newer model). It is a one-line build configuration change with no security relevance.

This commit only adds new unit tests for the Trezor Host Protocol (THP) channel code. It does not change any production firmware logic, so it cannot introduce a security vulnerability by itself. The tests verify that the channel correctly rejects or handles oversized messages.

This commit hardens how the Trezor firmware handles oversized messages in its low-level communication layer. Previously, asking for a buffer larger than the fixed 8 KB limit would trigger an internal assertion failure (a hard crash). Now the code returns a failure indicator and, in the sending path, raises a controlled FirmwareError instead. This is a defensive improvement that prevents a class of potential denial-of-service or crash conditions when very large messages are received or sent, but it does not by itself fix a known exploitable vulnerability.

This commit is a minor test-code cleanup. It removes a hard-coded Eckhart-specific JPEG homescreen path from a Trezor hardware wallet test suite and instead reuses a helper function that picks the correct image based on the device's screen layout type. There is no change to firmware behavior, no security fix, and no vulnerability.

This commit adds a new factory/production tool command that permanently exits 'manufacturing mode' by writing and locking a special one-time-programmable memory block. It also reorganizes how each Trezor model defines its OTP memory layout and unit properties. The change is a feature addition for the production-test firmware, not a fix for a known exploitable bug in user-facing firmware. It does not appear to introduce an obvious vulnerability, but it changes security-relevant manufacturing state logic.

This is a routine automated dependency update by Dependabot that bumps the Python library pyasn1 from version 0.6.2 to 0.6.3 in the project's lock file. The commit itself only changes package metadata (download URLs and cryptographic hashes) and contains no code changes, bug fixes, or security claims. There is no evidence in the commit or supplied references that this update addresses a security issue.

This commit removes a single unused dependency (fonttools) from a requirements file for an internal battery-testing tool. There is no indication of a security vulnerability or functional change to the Trezor firmware or wallet software.

This commit only changes test tooling. It extends a script that downloads Trezor firmware emulators for testing so it can also fetch a new 'tropic-enabled' variant for supported hardware models, and it fixes a shell quoting issue in a Nix helper command. There is no change to the actual device firmware, wallet logic, cryptography, or anything end users rely on for security.

This commit fixes two internal tooling issues in Trezor's firmware test pipeline: it makes the test framework correctly find a new 'Tropic' emulator variant, and it sanitizes the Amazon S3 upload path so a leading or missing trailing slash does not accidentally change where emulator files are stored. There is no direct evidence this is a security vulnerability in the hardware wallet itself, but the S3 path normalization is a hardening measure that could prevent accidental mis-uploads in CI.

This commit is a routine cleanup of the project's automated build scripts. It extracts repeated emulator build steps into reusable GitHub Actions components without changing what gets built, how it gets uploaded, or who can access it. There is no indication this affects the security of Trezor devices or their firmware.

This commit only updates the version number shown at the top of six changelog files from 2.10.1 to 2.11.0. No code, no bug fixes, and no security changes are present.

This commit simply adds two new firmware version numbers to a release tracking file. It does not change any code, fix any bug, or alter device behavior. There is no security relevance visible in the change itself.