Trezor firmware

This change is a compatibility fix for the Trezor emulator's display on Linux. It makes the emulator try the older X11 graphics protocol if the newer Wayland protocol fails to create a display window. There is no security issue here; it simply improves reliability when running the emulator on certain Linux distributions.

This commit only refreshes a lock file to reflect a version number bump (trezor 0.20.1 → 0.20.2) that was already done in a separate commit. There are no code changes, no dependency updates, and no security-related content in the diff or message.

This commit removes the special on-screen 'clear signing' definitions for LiFi swap transactions on Trezor hardware wallets. From now on, LiFi transactions will be shown as generic contract interactions rather than nicely labeled swaps. There is no indication this fixes a security vulnerability; it appears to be a product decision to stop supporting LiFi's specific transaction formatting.

This commit simply increases the version number of the Trezor Python library from 0.20.1 to 0.20.2 after a release. It changes one line in a project metadata file and contains no functional or security-related code changes.

This commit is a routine documentation update that generates the changelog for the Python trezorlib package version 0.20.1. It only deletes small changelog fragment files and inserts their text into the main CHANGELOG.md. No program code was changed, so it cannot introduce or fix a security vulnerability by itself.

This commit changes the Python packaging tool used to build the trezorlib package from Hatch to Flit. It only touches the project's build configuration file (pyproject.toml) and adjusts which files are included or excluded when the package is published. There is no change to the actual Trezor firmware, device code, or any security-sensitive logic.

This commit adds backward-compatibility shims so that older code referencing certain moved Python modules still works, but now shows a deprecation warning. There is no security issue here; it is a routine code-maintenance change.

This is a routine code reorganization in the Python trezorlib library. It moves two helper classes into a new module and moves a user-interface file into the command-line interface package. No security-sensitive behavior is changed, no bugs are fixed, and no vulnerabilities are introduced.

This commit removes a feature that would have sent a 'MCU attestation'—a cryptographic proof signed by the device's microcontroller—during device authentication. The change itself is a simple deletion of the attestation code and its changelog entry. There is no direct evidence in the commit of a security vulnerability; it appears to be a product decision to stop sending this proof, possibly because the feature was not ready or was being reconsidered. It reduces the amount of identity information the device exposes during authentication.

This commit adds a missing initialization call for the hardware security feature called TrustZone in the Trezor device's kernel. TrustZone helps separate sensitive code (like cryptographic secrets) from less trusted code. Without this initialization, the security boundary may not be set up correctly when the device boots in secure mode, potentially leaving the device in a less protected state. The fix is small but important: it ensures the security boundary is properly established before other system services start.

This is a routine automated dependency update by Dependabot, bumping the Python Mako templating library from version 1.3.11 to 1.3.12. The change only updates version numbers and package hashes in the project's dependency files. There is no indication in the commit itself that this fixes a security issue, and no security advisory or incident details were provided.

This commit fixes a bug in the Rust Trezor client library used to talk to Trezor hardware wallets. When signing a large Ethereum transaction, the device may ask the user to confirm by sending a 'button request' in the middle of streaming the transaction data. Previously, the client did not handle that mid-stream request, so the signing process could hang or fail. The fix wraps each streamed chunk's response with the existing interaction handler so button requests are processed correctly. A new example and a regression test for a 10 KB transaction are added.

This commit changes how the Trezor firmware exposes its internal Git commit hash (the 'revision ID'). Previously the full hash was directly readable by software. Now only a shortened version is stored plainly, while the full hash is lightly scrambled (XORed) and only returned through a function that requires a specific key byte. The goal is to make it harder for a malicious fake Trezor to copy the revision ID from an official firmware update and pretend it is running that official firmware. It is a defensive hardening change, not a fix for an active bug or vulnerability in the traditional sense.

This commit is a straightforward code reorganization: it moves the emulator's profile-handling code from one directory to another and updates the build files and include paths accordingly. There is no change to what the code does, no bug fix, and no security-related change.

This commit is a cleanup of how the word 'const' is used in the Trezor firmware's ed25519 cryptographic code. Previously, the code defined a custom 'CONST' macro that meant 'const' on newer compilers and nothing on older GCC versions. The commit removes that macro and uses plain 'const' everywhere. It also adjusts a Rust build script comment and compiler flag. There is no indication in the commit that this fixes a security vulnerability or changes runtime behavior.

This commit is a straightforward internal code refactor. It renames a build feature flag from 'applet' to 'applets' and replaces the KERNEL preprocessor guard with a new USE_APPLETS guard in the relevant source files. There is no change to actual security logic, no bug fix, and no indication of a vulnerability being addressed.

This commit changes a build configuration for Trezor's Unix emulator so that MicroPython uses the standard C setjmp/longjmp mechanism for non-local returns instead of a custom x86_64 assembly implementation. There is no direct security fix here; it is a portability/refactoring change. It does not affect the actual Trezor hardware firmware.

This commit fixes how the Trezor firmware build generates a Rust binding for an internal identifier type called Qstr. Previously, the build always assumed the underlying C enum was a 32-bit integer, but the firmware actually compiles with smaller 16-bit enums. The mismatch could cause the generated Rust code to use the wrong size, leading to memory corruption or crashes when Rust and C exchange Qstr values. The patch makes the build choose the correct enum size for firmware versus host builds.

This commit updates the Trezor firmware build environment to include prebuilt Rust standard library support for a newer ARM processor target (thumbv8m, used in the T3 device model). It is a build tooling change with no visible security relevance.

This commit is a code cleanup in Trezor's Ethereum transaction handling. It replaces a hand-rolled method of reading Ethereum vault transaction data with a shared, more structured parsing system called DisplayFormat. There is no indication this fixes a security bug; it appears to be a refactoring change with no functional security relevance stated by the vendor.

This commit updates the Trezor firmware build system and emulator code to use SDL3 instead of the older SDL2 library. It is a routine dependency migration affecting only emulator builds (software simulations of the hardware wallet), not the real device firmware. The changes rename functions and constants to match SDL3's API, adjust build scripts, and add a couple of small safety checks. There is no indication this fixes a known security vulnerability.

This commit only updates expected test result hashes (called 'fixtures') in a single test data file. The firmware code itself is not changed, and there is no indication of a security fix or vulnerability. It appears to be routine maintenance after switching the UI test framework to SDL3, which likely changed how screen snapshots are rendered and therefore changed their hashes.

This commit removes a single deprecated configuration option, CONFIG_NFCT_PINS_AS_GPIOS, from the Nordic Bluetooth Low Energy firmware build file. The change is a routine cleanup with no visible security relevance. It does not alter runtime behavior in a way that introduces or fixes a vulnerability based on the information provided.

This is a minor internal cleanup in the Nordic (nRF52) Bluetooth Low Energy firmware for a Trezor hardware wallet. It replaces a hard-coded reference to 'spi0' with a device-tree alias called 'spi-master' so the same code can more easily be reused across different board revisions. There is no security-relevant change visible in the diff.

This commit tidies up build configuration files for Trezor's Nordic Bluetooth/radio test firmware. It removes some redundant or outdated settings, adds a couple of clarifying options, and disables over-the-air firmware update slots for test builds. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a routine cleanup of build settings.