Trezor firmware

This commit adds a new error code called Failure_InProgress to the Trezor firmware's communication protocol. It does not change any security logic; it simply gives the device a standardized way to tell a connected computer that a non-interruptible task is currently running. The actual behavior of blocking or allowing interruptions is not part of this change.

This commit removes an unused error code named Failure_BufferError from the Trezor firmware's protocol definitions and generated code. It is a cleanup change with no security relevance: the code was not being used, and the protobuf field number is now marked as reserved to prevent future accidental reuse.

This commit is purely a build/code-generation formatting change. It splits a very long single-line string constant into many shorter lines using Rust's concat! macro, and reformats a long array of numbers into multiple lines. The goal is to reduce Git merge conflicts when multiple people update translation strings at the same time. No user-facing behavior, security logic, or functionality changes.

This commit is a routine localization (translation) update. It changes a few user-facing text strings—such as capitalization of 'Locktime' and wording of backup/recovery prompts—and regenerates the matching string tables and test fixtures. There is no code behavior change and no security relevance.

This commit only changes English text strings in a translation file. It fixes capitalization, adds missing translations for some product variants, and clarifies one recovery message. There is no code behavior change and no security impact.

This commit only updates expected test result fingerprints (hashes) in a single test data file. It does not change any firmware code, cryptographic logic, or user-facing behavior. There is no security issue in this change itself.

This commit refactors how the Trezor hardware wallet's backlight driver manages its internal DMA buffers. It replaces direct memory writes with helper functions that add bounds checks and a 'dirty' flag to track whether a buffer has been modified. The change improves code readability and defensive programming but does not appear to fix an actively exploitable security bug. It is labeled by the developer as a refactoring with no changelog entry.

This commit fixes a small logic bug in the Trezor hardware wallet's screen backlight driver for STM32U5 devices. The driver uses a two-element buffer (pwm_data[][0] and pwm_data[][1]) to send pulse values to a backlight power chip (TPS61062). The old code only checked whether the first element was 'empty' (set to UINT16_MAX) before deciding to clear the buffer, ignoring the second element. This meant the buffer could fail to be cleared when it should have been, potentially leaving stale pulse values and causing incorrect backlight behavior or visual glitches during brightness transitions.

This commit is a routine build-system update that swaps two source files in the list of files compiled for the Trezor T3W1 hardware model and its emulator. It removes references to files named lt_l1_port_wrap.c and lt_random.c and adds a new file named lt_port_wrap.c, so the project builds against version 3.1.0 of an external library called libtropic. There is no indication in the commit of any security bug, vulnerability fix, or behavior change beyond keeping the build compatible with the newer library version.

This commit updates a bundled third-party library called libtropic from one version to another (v3.1.0). The change is a single-line version bump in a vendor submodule. There is no code diff shown, no description of any bug or security fix, and no external security advisory provided. On its own, this looks like a routine dependency maintenance update.

This commit fixes a test helper so it properly closes the USB/transport connection when a background test task is killed. It only touches test code, not the firmware or production wallet code, so it has no direct security impact on real Trezor devices or users.

This is a small internal code cleanup in the Python Trezor library. It removes a helper method and moves the same error-code-to-exception logic directly into the ThpError class constructor. There is no user-visible behavior change and no security relevance.

This commit only updates expected test result fingerprints (hashes) in a JSON file used for automated UI testing. It does not change any firmware, application, or security code. There is no indication of a security fix or vulnerability.

This is a tiny test-only fix that stops the Python test helper from sending a special 'reseed' debug command to real Trezor hardware during automated tests. The reseed command is meant only for the software emulator used in testing. Sending it to a physical device had no production security effect, but it could cause hardware tests to behave unexpectedly or fail. It is not a vulnerability in the firmware that end users run.

This commit only adds four changelog text files describing unrelated past or upcoming changes to the Trezor Python library. No actual code was modified, so it cannot introduce, fix, or hide a security vulnerability on its own.

This commit simply changes a version number in a Python package configuration file from a development pre-release (0.20.0-dev0) to a stable release (0.20.0). It is a routine release housekeeping change with no security implications.

This is a small bug-fix in Trezor's Python library. Older Trezor firmware did not advertise which features it supports via a 'capabilities' field, so the library was incorrectly throwing errors when connecting to those older devices. The change makes the library skip capability checks when the field is missing, and it unifies the error handling. It does not appear to be a security fix.

This commit fixes a bug in Trezor's Python library for handling large USB-style messages (THP protocol). Previously, if a message payload was too large, the code could silently wrap around a 16-bit length field, producing an incorrect packet size. The patch now catches that overflow and raises a clear error instead. It also removes an unused constant that capped payload length at 60,000 bytes. The fix is defensive and improves error handling, but it is in the host-side Python library, not the device firmware itself.

This commit fixes a Python library helper so that checking whether a Trezor device is unlocked no longer crashes or misbehaves when the device is brand new and not yet set up. It adds a guard that returns early if the device is uninitialized, because an uninitialized device has no wallet and therefore cannot be 'locked' in the usual sense. The change is accompanied by a docstring clarifying that the lower-level session method only works on initialized devices with a passphrase.

This commit is a code cleanup that moves the screen-recording helper from a low-level debug library into the command-line tool. It does not change what the feature does; it only reorganizes where the code lives and makes the recording stop more reliably when an error occurs. There is no indication this fixes a security vulnerability.

This is a tiny one-line fix in the Python Trezor library that changes when a session ID counter wraps around. Previously, the counter reset before reaching 255, so session ID 255 could never be used. The fix allows 255 to be used as a valid session ID. This is a minor correctness/robustness improvement, not a clear security vulnerability.

This commit refactors how the trezorctl command-line tool saves and resumes sessions with Trezor hardware wallets. It changes the session identifier from a simple hex string to a base64-encoded JSON object that also includes the device path, and it adds support for resuming THP (Trezor Host Protocol) sessions. The changes are described by the vendor as a feature/refactor improvement, not as a security fix. There is no direct evidence in the commit of a vulnerability being patched, but the refactor touches session lifecycle code and could affect security-relevant behavior such as session isolation, passphrase handling, and device path matching.

This is a Python-only internal refactoring of how Trezor's test/debugging library keeps track of open connections. It replaces fragile manual open/close bookkeeping with a cleaner 'reopen' flag and context-manager handling. There is no direct evidence this fixes an exploitable security bug; it appears to be code-quality work to prevent connection-state mistakes during testing.

This commit fixes a crash bug in the Trezor command-line tool (trezorctl). It changes when the USB connection to the Trezor device is closed, moving cleanup from program shutdown to right after each command finishes. The old approach could trigger a segmentation fault (a hard crash) in the underlying USB library because two different cleanup routines interfered with each other at exit.

This commit simply removes three unused helper functions from the Python debug-link library. These functions were already non-functional on current Trezor devices and are not used by older devices anymore. There is no security issue here.