Trezor firmware

This commit only updates translated text strings for the Trezor hardware wallet's user interface. It adds a new message about canceling the setup of a 'wipe code' (a feature that erases the device if a specific code is entered) and updates the digital signature that verifies the translation files. There is no code that handles secrets, cryptography, device communication, or security logic being changed.

This commit is a routine translation update for the Trezor hardware wallet firmware. It adds and updates translated text strings for a new device model called 'Eckhart' across several language files (Czech, German, Spanish, French, Italian, Portuguese). It also updates the digital signature that verifies the translation files and refreshes the expected visual test snapshots because the on-screen text has changed. There is no code that handles secrets, cryptography, or device security logic in this change.

This commit is a routine synchronization of translated user-interface text strings for the new 'Eckhart' Trezor device model. It adds and updates translations in Czech, German, Spanish, French, Italian, and Portuguese, plus updates translation signatures and UI test snapshot hashes. There are no code logic changes and no security relevance.

This commit is purely a code-style and formatting cleanup. It re-indents a large embedded image byte array, adds a missing import and two function calls related to screen dimming in the lock manager, and wraps a debug log line to fit style guidelines. There is no security-relevant change.

This commit only adds a new Python library called 'bleak' to the project's dependency list and lock file. Bleak is a popular, legitimate library used for Bluetooth Low Energy communication. There is no actual code change, no vulnerability fix, and no indication of malicious intent in the commit itself. It is a routine build/dependency update.

This commit replaces hard-coded English text in Trezor's on-screen pairing and connection prompts with proper translation keys. The visible messages stay the same in English, but the firmware can now display them in other languages. There is no security bug being fixed here; it is a routine internationalization cleanup.

This commit is a routine code cleanup that replaces older Python type-hint syntax (Union[...]) with the newer pipe syntax (|). It also updates one helper function to return None instead of the string 'dynamic' for consistency. There is no change to program logic, no security fix, and no vulnerability introduced.

This is a routine automated dependency update by Dependabot, bumping the Python image-processing library Pillow from version 11.2.1 to 11.3.0 inside an internal testing tool. The change is a single version number in a requirements file for the automatic battery tester, which is not part of the Trezor firmware that runs on devices or handles cryptocurrency secrets. There is no indication in the commit that this fixes a security issue, and no verified security references were supplied.

This commit is a routine build-system housekeeping change for the Trezor firmware repository. It replaces the Python Poetry package manager with the `uv` package manager across CI workflows, build scripts, and documentation. No device firmware code, cryptographic logic, or security-sensitive behavior is modified. The change is purely about how development dependencies are installed and invoked.

This commit is a routine update of user-facing text translations for the Trezor firmware. It changes wording in multiple languages, adds new translation keys for upcoming features (such as Bluetooth and new device screens), and replaces a non-breaking space with a regular space in a few English strings. There is no code logic change and no security-relevant behavior is altered.

This commit only shortens and updates translated user-interface text in Spanish, French, and Portuguese translation files, plus refreshes the translation signature metadata. There are no code, logic, cryptographic, or security changes.

This commit changes a build script for Trezor's Nordic (nRF) hardware so it can automatically detect whether it is running inside a Docker/Nix build environment or a local developer's machine, and then run the build command the appropriate way. It is a build-system convenience change with no visible security relevance.

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 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 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 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 numeric model identifier for a specific Trezor hardware board (the T3W1 revision A with Nordic nRF52832 chip) into the firmware signing process as a protected custom TLV field. It is a feature addition that embeds device-model metadata into signed firmware images. There is no indication in the commit that it fixes a security bug or introduces a vulnerability.

This commit adds four pre-signed binary files called 'vendor headers' for a new Trezor hardware model (T3W1). These files are part of the device's firmware build and boot trust chain, but the commit itself only adds already-signed binaries. There is no code change, no evidence of a vulnerability, and no indication these files are malicious or improperly signed.

This commit is a routine user-interface change for the Trezor hardware wallet. It adds a small connection-status icon and a new 'Disconnected' label to buttons that represent Bluetooth Low Energy (BLE) paired devices. There is no security-relevant behavior change in the code.

This commit is purely a documentation update: it compiles the changelog for Trezor firmware version 2.9.1 by deleting individual changelog fragments and adding the final release notes to several CHANGELOG files. No source code, firmware logic, or security behavior is changed.

This is a straightforward internal code cleanup in Trezor's Python library. It replaces two separate flags that tracked whether a device was paired with a single simpler flag, and adds extra debug logging. There is no indication this fixes or introduces a security vulnerability.

This commit changes a single test marker so that a Cardano message-signing test runs on Trezor Model T/Core devices instead of being skipped on the older T1B1 model. It is a test-suite maintenance change with no effect on the actual firmware code that users rely on.

This commit is a simple internal code cleanup in the Cardano app of Trezor firmware. It renames a function parameter from 'payload_first_chunk' to 'payload' and switches from keyword arguments to positional arguments in one call. There is no change to user-visible behavior, security logic, or data handling.

This commit rewrites how the Trezor device fetches the message payload during Cardano message signing. Instead of the host pushing fixed-size chunks to the device, the device now asks for a specific slice of data by sending a length and offset, and the host replies with exactly that slice. The change also removes the previous 1024-byte maximum payload size limit, so larger messages can now be signed. The code adds bounds checks on both sides, but because the device now requests the entire payload in one go, this could stress limited device RAM. There is no direct evidence in the commit that this fixes a reported security bug; it reads as a feature/refactoring change.