Trezor firmware

This commit hardens how a Trezor hardware wallet checks the authentication tag when decrypting data protected by the ChaCha20-Poly1305 cipher. Previously, the Python caller compared the expected tag with the computed tag using a helper called utils.consteq. Now the comparison is done inside the low-level C module using a constant-time equality function, and decryption callers must pass the expected tag directly to finish(). This reduces the risk of a developer forgetting to verify the tag or using a non-constant-time comparison, which could let an attacker tamper with encrypted secrets.

This commit is a routine code cleanup that splits one combined AES-GCM encryption/decryption class into two separate classes: one for encryption and one for decryption. It does not fix a security bug or introduce a new vulnerability. The change makes the API clearer and prevents accidental misuse, such as trying to decrypt with an encryption-only object.

This commit is a code cleanup, not a security fix. It creates a new, more specific error type called AuthenticationError and changes AES-GCM and ChaCha20-Poly1305 decryption to throw that error instead of a generic RuntimeError when authentication fails. It also updates the Python code that catches those errors to catch the new type. The cryptographic behavior itself is unchanged.

This commit is a routine code cleanup (chore) that splits one combined ChaCha20-Poly1305 encryption/decryption class into two separate classes: one for encryption and one for decryption. It does not fix a security bug, add a new feature, or change cryptographic behavior. All existing callers are updated to use the appropriate new class. The change is purely structural and makes the API clearer.

This commit only changes Python unit tests for the AES-GCM cryptography code in the Trezor firmware. It updates existing tests to pass an expected authentication tag to the finish() method and adds new tests that check the code correctly rejects missing, wrong-length, or invalid tags. There is no change to the actual cryptographic implementation or firmware behavior, so this commit does not introduce or fix a live security vulnerability by itself.

This commit only changes Python unit tests for the ChaCha20-Poly1305 encryption code in the Trezor firmware test suite. It does not modify the actual cryptographic implementation, device firmware, or any production code. The changes add test cases to verify that decryption correctly requires and validates the authentication tag (MAC). There is no security vulnerability in this commit itself.

This commit updates the Monero ChaCha20-Poly1305 decryption helper in Trezor firmware to use the cryptographic library's built-in tag verification instead of a custom comparison. The old code computed the authentication tag and compared it to the expected tag using a helper called monero.ct_equals. The new code passes the expected tag directly into cipher.finish(), letting the library verify it. This is a defensive hardening change that reduces the risk of subtle timing or comparison bugs in authentication-tag checking, which could theoretically allow forged or tampered data to be accepted.

This is a tiny user-interface bug fix. It moves a translation lookup so that the 'Enter PIN' message is shown in the correct language on the boot screen instead of always appearing in English. There is no security vulnerability here.

This is a minor user-interface cleanup for the Trezor hardware wallet's Eckhart layout. It changes one default button label parameter from a hardcoded translated string to the system's default confirmation verb, and updates the corresponding screen-shot test hashes. There is no security-relevant change visible in the code.

This commit is a simple revert that brings back previously removed display definitions for the LiFi decentralized exchange aggregator on Trezor hardware wallets. It restores human-readable transaction labels (such as 'Amount to Send' and 'Recipient') when users sign LiFi swap transactions. There is no indication of a security bug, vulnerability, or malicious change in the code itself.

This commit simply removes two unused Ethereum address and chain-list constants from a Python file. There is no functional code change, no bug fix, and no security relevance.

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