Trezor firmware

This is a visual-only bug fix for the Trezor hardware wallet's Delizia user interface. When a warning screen is marked as dangerous, the title text was supposed to appear red, but it was only showing a danger icon. The fix adds the missing red title styling. There is no change to transaction logic, cryptography, or security checks.

This commit changes a Trezor firmware UI function so that a previously ignored 'external menu' flag is now actually used. When the flag is set, the confirmation screen uses an externally supplied menu instead of the built-in one. The change is small and appears to be a feature enablement rather than a fix for an active security bug, but it touches user-confirmation flow code where mistakes could affect what options a user sees.

This commit is a routine UI feature addition for the upcoming Trezor Safe 7 (Eckhart layout). It lets the device show a simplified external menu during certain confirmation screens, and currently rejects combinations that aren't yet supported. There is no indication of a security bug or fix.

This commit adds a new optional 'chunkify' setting to Tron transaction signing on Trezor hardware wallets. When enabled, addresses are shown on the device screen in small groups of characters (chunks of 4) instead of one long string, making them easier for users to read and verify. The change also makes chunking disabled by default for Tron sign-transaction screens, whereas some Tron screens previously always chunked addresses. There is no direct security vulnerability in the diff, but any change to how addresses are displayed can subtly affect how well users detect address-rewriting attacks.

This commit only adds a new test data file containing example inputs and expected outputs for Ethereum's EIP-7702 authorization signing feature. It does not change any production firmware code, so it cannot introduce a security vulnerability or fix one. The test vectors are public, use a well-known test mnemonic, and are explicitly marked as not requiring a changelog.

This commit is a straightforward internal code cleanup in the Ethereum transaction signing flow. It turns a callback-creating helper function into a class and moves where that object is created. There is no change to user-visible behavior, security checks, or cryptographic handling.

This commit only adds new automated tests for the Trezor hardware wallet's Ethereum transaction signing. It checks that the device correctly rejects malformed transaction data sent during signing. There are no changes to the actual firmware code that users run, so this commit does not fix or introduce a security issue by itself.

This is a small code cleanup in Trezor's Ethereum transaction signing. When an Ethereum transaction has no extra data (calldata), the device no longer runs a now-unnecessary progress-indicator step. This only changes the user-interface flow for no-data transactions; it does not change what is signed or how the signature is computed. The large diff is mostly updated test screenshot fingerprints (hashes) reflecting the changed on-screen sequence.

This commit is a code cleanup in the Ethereum transaction signing module. It replaces a manual byte-copying loop with a simpler buffer extension approach and removes duplicate code that wrote the RLP header and hashed the data in two different places. There is no indication of a security bug being fixed.

This commit refactors how a Trezor hardware wallet asks for pieces of an Ethereum transaction's data from the host computer. It renames an internal helper and, importantly, adds a size check so the host cannot return a chunk larger than the device requested. That oversized-chunk condition could previously lead to memory corruption or unexpected behavior during transaction signing.

This is a minor code cleanup in the Ethereum transaction signing module. It moves an import statement so that a helper class (`HashWriter`) is only imported during type-checking, not at runtime. There is no functional change, no bug fix, and no security relevance.

This commit only adds and updates user-facing text strings (labels, warnings, and confirmation messages) for a new Ethereum feature called EIP-7702. It does not change any code that handles private keys, signing logic, transaction parsing, or security checks. There is no direct security issue visible in this change.

This is a purely cosmetic code-style commit. It runs the project's Rust formatter across hundreds of files, changing only how import statements are grouped and how long comments are wrapped. No program logic, security behavior, or functionality was altered.

This commit simply moves a helper function called compact_size from one internal file to another and updates the import statements in files that use it. There is no change to what the function does, no bug fix, and no security impact.

This commit changes a Trezor firmware function so that, outside of a special factory testing mode (PRODTEST), it refuses to write an MCU attestation certificate. Previously the function accepted and stored such a certificate. The change prevents firmware from installing or overwriting this certificate, likely to reduce attack surface, but the commit message gives no details about any specific security issue.

This commit updates Trezor's internal test-only files that simulate a TROPIC01 secure chip. It replaces old self-signed test certificates with a new four-level test certificate chain and embeds keys directly into config files instead of referencing separate PEM files. The change is labeled as a testing chore, touches only test/development artifacts, and does not alter production firmware code. The most notable security-relevant detail is that a hardcoded X25519 private key is included in test data, but it is explicitly a test key already present in the public source tree and used only for the emulator/unix test build.

This commit changes how Trezor hardware wallet firmware handles a special factory-testing mode called 'prodtest'. In prodtest builds, it now uses an empty placeholder certificate for MCU (microcontroller) attestation instead of a real device certificate. This appears to be a development/testing convenience change rather than a fix for a live security vulnerability, because prodtest is not the normal user-facing firmware. However, it touches attestation code, which is security-sensitive, and the commit message gives no security context.

This commit is a simple code cleanup: it moves a small block of code that builds an authentication challenge message into its own reusable function. There is no change to behavior, no bug fix, and no security-related change.

This commit adds a new automated test that checks whether the serial numbers embedded in three different security certificates inside a Trezor device all match. It does not change any production firmware code, fix a bug, or alter device behavior. It only adds a test and a corresponding test fixture entry.

This commit only adds '.PHONY' declarations to many Makefiles. These declarations tell the build system that certain target names are not real files, preventing build mistakes if a file with the same name happens to exist. There is no change to the actual firmware, cryptography, or any code that runs on the device.

This commit changes a factory-production testing tool (prodtest) so that the commands for writing and reading the device's MCU attestation certificate also work in the software emulator, instead of returning 'not implemented'. In the emulator, the written certificate is only stored in memory and disappears after reboot. The change removes compile-time guards that previously disabled these commands for emulator builds. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a feature-enablement change for testing/development workflows.