Trezor firmware

This commit updates the project's build dependency files (poetry.lock, pyproject.toml, shell.nix) to add tools needed for nRF microcontroller work. It is a routine build-environment change, not a fix for a security vulnerability. The only security-relevant note is that it pins several new Python packages, which is good practice, and it removes one unused tool (nrf-command-line-tools) from the development shell.

This is a minor code cleanup that changes how a helper function's input type is described. It makes no functional change to what the code does and does not affect security.

This commit is a purely cosmetic code cleanup: it adds missing spaces before arrow symbols in two lines of Rust source code. There is no functional change, no bug fix, and no security relevance.

This is a small internal code cleanup in Trezor firmware. It removes an unnecessary conversion of a byte slice into a mutable bytearray before storing it in a channel cache. The change is described by the developer as a memory-allocation optimization and is not presented as a security fix.

This commit swaps in two new pre-built binary files for the T3W1 hardware model (a QA bootloader and a Bluetooth development firmware blob) and updates the matching SHA-256 hashes in a header file. The actual code inside the binaries is not shown in the diff, and the commit message gives no reason for the update. There is nothing here that directly demonstrates a security bug or fix.

This commit removes an unfinished 'Connect' button from the Bluetooth device menu on Trezor's upcoming Eckhart hardware model. The feature was only a placeholder (its handler contained a TODO comment and did nothing), so deleting it does not fix any active security bug. It is a routine cleanup change with no security relevance.

This commit removes a confirmation prompt that asked the user before disconnecting a Bluetooth device, and instead immediately disconnects if a device is connected. It is a minor user-experience/behavior change on a new hardware model (Eckhart). There is no direct evidence in the commit that this fixes a security vulnerability.

This commit adds the ability for a Trezor hardware wallet to forget (unpair) a specific Bluetooth device by its MAC address, instead of only being able to unpair the currently connected device or all devices. It is a feature-completion change for the new Eckhart model's Bluetooth settings menu. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine user-facing feature implementation.

This commit is a routine user-interface tweak for an upcoming Trezor hardware wallet model (codename Eckhart). It changes the Bluetooth pairing limit from 4 to 8 devices, disconnects any active Bluetooth connection before starting pairing, and updates the on-screen warning text and button label shown when the device limit is reached. There is no security-relevant change visible in the code.

This commit removes a Bluetooth on/off button from the Trezor device's settings menu. The button was only a placeholder: it showed a confirmation dialog but did not actually change Bluetooth state. The change is described as a temporary UI cleanup because the underlying Bluetooth control API is not yet available. There is no security fix here.

This commit adds a new 'Power' menu to the Trezor Safe 7 (Eckhart) device interface, letting the user turn the device off, reboot it, or reboot into bootloader mode. It also adds a low-level 'hibernate' function to the power-management module. The changes are user-facing feature additions and do not appear to fix or introduce a security vulnerability on their own.

This commit makes a small change to the firmware update process for the nRF wireless chip inside some Trezor hardware wallets. It adds a one-second delay after writing the new firmware image, presumably to give the flash memory time to finish saving before rebooting the chip. The change is described as improving reliability, not fixing a security vulnerability. There is no direct evidence in the commit that this is exploitable or that it was caused by a security flaw.

This commit is a simple code cleanup: it moves the definitions of which physical pins control the RGB LED from a shared driver file into the board-specific header files for two Trezor T3W1 hardware revisions. The same pin numbers and ports are used, and no behavior changes. There is no security issue here.

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 fixes a build configuration problem in the RGB LED code for Trezor hardware wallets. It moves some shared color definitions outside a KERNEL_MODE guard and wraps an effects source file in the same guard, plus adds a missing dependency. There is no direct evidence this is a security vulnerability; it appears to be a build/dependency fix.

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 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 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 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 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 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 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 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 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 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.