Trezor firmware

This commit adds a cycle limit to the RGB LED animation effects on Trezor hardware wallets. Previously, LED effects like the charging or bootloader breathing animation would run indefinitely until explicitly stopped. Now, callers can request a specific number of cycles, and the effect will automatically stop after that many cycles. The change also slightly adjusts the blue LED color definition. There is no direct security vulnerability visible in the diff; it appears to be a feature or hardening improvement for LED behavior.

This commit adds two new factory-testing commands for controlling the RGB LED on Trezor devices during production testing. It is a feature addition to the prodtest (manufacturing diagnostic) firmware, not a fix for a security issue. There is no indication it addresses a vulnerability or was disclosed as security-relevant.

This commit adds new LED lighting effects (a slow blue 'breathing' light for the bootloader and a yellow pulsing light for charging) to the RGB LED driver used in some Trezor hardware wallets. It is a feature addition, not a security fix or vulnerability patch. There is no indication it addresses any security issue.

This commit removes an accidental duplicate of a harmless LED color-setting function in the Unix (simulator/emulator) build of the Trezor firmware. It is a routine cleanup with no security relevance.

This is a routine code cleanup in the RGB LED lighting driver for a Trezor hardware wallet. It renames variables and functions to be clearer (for example, 'bootloader_breathe' becomes 'pairing'), shortens a constant name, and adds clamping so color values stay within valid bounds. There is no security-relevant change and no indication this fixes a vulnerability.

This commit adds a new function that lets the firmware ask whether an RGB LED lighting effect is currently running. It also renames some internal constants and removes unnecessary 'return' statements. There is no security-relevant change here; it is a routine feature addition to the LED driver.

This commit is a routine feature improvement for the RGB LED on Trezor hardware wallets. It increases the smoothness of LED color transitions (for example the breathing blue bootloader light and the yellow charging light) by switching from 8-bit integer color values to higher-resolution timer values and adding gamma correction. There is no indication this change fixes or introduces a security vulnerability.

This commit adds empty placeholder functions for RGB LED effects in the Unix (simulator/emulator) build of the Trezor firmware. The functions do nothing and simply return. There is no security-relevant change.

This commit updates the Trezor firmware's RGB LED system-call interface. It adds two new kernel calls (effect_start and effect_stop), exposes them to Rust code, and removes a redundant negative-value check in the effect lookup. The change is a feature update with a minor hardening cleanup; there is no direct evidence it fixes an exploitable security bug.

This commit only tidies up comments and documentation for the RGB LED driver in Trezor hardware firmware. It also makes two tiny, safe-looking code-order tweaks: moving a timer unset call earlier and reordering flag/timer operations when stopping an LED effect. There is no security-relevant change and no bug fix.

This commit simply adds a new approved digital signature for translation files used in Trezor firmware version 2.9.1. It is a routine maintenance task with no visible security-relevant code change.

This change adjusts how a Trezor hardware wallet hands off from its main app to its bootloader during a firmware upgrade. Previously, the device would wait until the host computer acknowledged the 'I am rebooting' message before rebooting. Now it waits at most 500 milliseconds and reboots anyway if the acknowledgment doesn't arrive in time. The goal is to avoid getting stuck if that final acknowledgment packet is lost in transit, similar to how a phone call can hang waiting for a goodbye that never comes. The patch is a partial fix for a reliability issue in the device-host communication protocol.

This commit only adds a plain-language comment (docstring) explaining what the ThpContext class does. No code behavior was changed, so it cannot introduce or fix a security issue on its own.

This commit is a simple rename of a Bluetooth interface class from 'BleInterface' to 'BLEIF' to match the naming style of 'USBIF'. It only changes names in code comments, type stubs, and internal identifiers. No behavior changes, no security fixes, and no security risks are present.

This commit fixes a hard-coded Bluetooth Low Energy (BLE) interface identifier in the Trezor hardware wallet firmware. The old code used a fixed number (8) with a comment saying it should be replaced by the proper system handle. The fix now uses the correct generated constant. Using the wrong identifier could cause the BLE communication interface to be misidentified, which might lead to communication errors or, in a worst-case security scenario, allow an attacker to confuse the device about which channel data is arriving on. The change is small and defensive, but the commit message gives no details about any actual security issue.

This commit only adds new automated tests for the Trezor hardware wallet's THP (Trezor Host Protocol) transport layer. It checks that the device correctly rejects old protocol v1 packets and unallocated channel messages. No production firmware code is changed, so this commit does not introduce or fix a security vulnerability by itself.

This commit rewrites how the Trezor firmware handles the new Trezor Host Protocol (THP) across USB and Bluetooth. Instead of running one independent session handler for each interface, it merges them into a single task that can switch attention between interfaces. The main goal is to let the device abandon ('preempt') a stuck or unresponsive THP channel so that another interface can still make progress. The change is described as a feature/refactor, not as a security fix, and one THP test file is removed to be rewritten later.

This commit adds a verification step in the Trezor hardware wallet's factory production-test tool before writing a device certificate to secure storage. It now checks that the supplied certificate chain is cryptographically valid and matches the device's own MCU authentication key, preventing a malformed or mismatched certificate from being permanently written during manufacturing.

This commit adds a production-line safety check in Trezor's internal 'prodtest' firmware. Before writing a device-unique X.509 certificate to the device, the firmware now verifies that the certificate's subject serial number matches the device's own serial number stored in OTP. It also centralizes serial-number reading into a helper function. This is a hardening/validation improvement rather than a fix for an active user-facing vulnerability.

This commit removes extra Bluetooth address-type information from two Python-facing functions in the Trezor firmware. Previously, these functions returned both a 6-byte Bluetooth address and an integer indicating whether the address was public or random. Now they return only the 6-byte address. The change is described as a routine cleanup ('chore') with no changelog entry. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be an API simplification.

This commit updates the Bluetooth device menu on Trezor hardware wallets to display real paired-device MAC addresses instead of a hardcoded placeholder name ('Trezor Suite'). It is a UI feature change with no apparent security relevance.

This commit changes how the Trezor hardware wallet displays a long device name in its settings menu. Previously, if the device name was too long to fit on screen, the firmware would trigger a fatal error in debug builds. The fix allows the name to overflow visually instead of crashing. There is no indication this is a security vulnerability; it is a UI robustness fix.

This commit is a UI layout fix for the Trezor hardware wallet's 'Eckhart' design. It renames and restructures how menu buttons handle long text labels so that certain items (like the device name) can overflow onto a single scrolling line instead of being forced into two lines. There is no indication this change fixes a security vulnerability; it appears to be a visual/UX improvement.

This commit fixes a data structure bug in the production-test emulator for Trezor hardware wallets. The code previously stored a list of pointers to command definitions, but used the wrong size when growing the list and then dereferenced it incorrectly. The fix stores the command definitions directly in the list and uses the correct size. This is a straightforward bug fix in an internal testing tool; there is no direct evidence it is an exploitable security vulnerability.

This commit fixes a bug in the Unix emulator for Trezor's USB virtual serial port (VCP). Previously, after reading part of a message, the emulator would erase the entire buffer and reset the length to zero, even if unread data remained. Now, for VCP interfaces, it correctly keeps the unread portion of the message for the next read. This is a correctness fix in emulator code, not the real device firmware, and there is no direct evidence it is security-relevant or exploitable.