Trezor firmware

This commit is a small defensive cleanup in Trezor's user-interface code. It adds a runtime check that prevents two UI features—'info' and 'external_menu'—from being used at the same time, because that combination is not implemented. It also removes two places in Python code that accidentally passed both flags together. The change makes a previously silent debug-only assertion into an explicit error, which helps avoid unexpected UI behavior rather than fixing an active security vulnerability.

This commit is a test-only/internal UI change for the Trezor firmware. It adds a flag called has_flow_menu to a screen component and marks three screens in the confirm_output flow with that flag. The flag is only used to expose menu state to automated tests/debuglink, and does not change user-facing behavior or fix any security issue.

This commit adjusts linker scripts that control how the Trezor hardware wallet's bootloader and security monitor (secmon) binary images are laid out in flash memory. It reduces alignment padding from 512 bytes to 4 bytes and changes how unused space at the end of each image is filled with zeros. The change appears to be a correctness fix for image padding rather than a fix for an exploitable memory corruption bug, but the exact security implications are not stated by the vendor.

This commit changes how many wrong PIN attempts are allowed on Trezor hardware wallets that use a component called Tropic. Previously, devices using both Tropic and Optiga security chips were limited to 10 PIN attempts, while devices using only Tropic were allowed 16. The change makes all Tropic-based devices use 10 attempts, matching the stricter limit. This is a defensive consistency fix, not an active vulnerability patch, but it reduces the attack surface for PIN brute-force attempts on Tropic-only devices.

This commit is a code cleanup: it removes duplicate helper macros from several cryptography modules and replaces them with a single shared macro. There is no change to user-facing behavior, no bug fix, and no security patch. It is purely an internal refactoring to make the code easier to maintain.

This commit simply bumps the version of a Rust dependency called zeroize from 1.7.0 to 1.8.2. zeroize is a library used to securely erase sensitive data from memory. The change itself is a routine version update with no visible security fix or vulnerability being addressed in the commit. There is no indication this update fixes a known security problem in Trezor firmware.

This commit adds Rust wrappers around existing low-level cryptographic functions in the Trezor firmware so they can be used by a new feature called THP. It does not appear to fix a known bug or vulnerability. The changes are mostly a refactor: they expose AES-GCM, Curve25519, HMAC-SHA256, SHA-512, CRC32, and a random-byte helper to Rust code, and add unit tests. There is no direct evidence in the commit that this resolves a security issue, but any new crypto binding introduces a small chance of misuse or memory-safety mistakes.

This is a routine dependency update for the Rust build tool bindgen inside Trezor firmware. It bumps bindgen from version 0.62.0 to 0.72.1 and adjusts the code to match the newer API. The change removes a small workaround that forced a function signature to be read as non-const pointers, because the newer bindgen now generates the correct const pointers. There is no direct security fix here, but keeping build tools current reduces the chance of future bugs or build issues.

This is a one-line change adding a missing C standard header file (`stdbool.h`) to a cryptographic header. It enables the use of `bool`, `true`, and `false` types in the file. There is no functional code change, no bug fix, and no security-relevant behavior change visible in the diff.

This commit fixes a compiler-specific alignment definition for AES cryptographic data structures. Previously, the code only forced memory alignment when compiled with GCC on 64-bit x86, but not when compiled with Clang on the same architecture. The change makes Clang behave the same way as GCC, ensuring the AES context has the same memory layout regardless of which compiler is used. This is a hardening/fix for consistency in cryptographic code, but the commit message does not describe an active exploit or security vulnerability.

This commit removes the ability to download or install 'beta' firmware versions through the Trezor Python command-line tool. It is a feature cleanup, not a security fix. There is no indication it patches a vulnerability.

This commit is a small internal cleanup of how the Trezor firmware's kernel talks to applets (isolated mini-programs). It removes a direct pointer to the applet's header from the applet structure and instead reads that header from the start of the applet's code area when needed. The change is described as a refactor with no changelog. There is no direct evidence in the commit that this fixes a security vulnerability, but it does reduce the chance that a stale or manipulated header pointer could be used.

This commit marks several fixed data objects as read-only constants so the compiler can place them in flash memory (.rodata) instead of writable RAM. This is a hardening change: it prevents accidental or malicious code from modifying values like the device model name, USB product strings, firmware revision, and the base32 alphabet. There is no direct evidence in the commit that an actual exploit exists; it is a defensive memory-layout fix.

This commit is a code cleanup that moves coreapp-specific logic out of the generic applet code into a new dedicated coreapp module. It does not appear to fix or introduce a security vulnerability; it is a structural refactor to make the applet abstraction more generic and prepare for future extension applets.

This commit changes how the Trezor firmware's embedded Python interpreter handles short 'atomic' critical sections. Previously, these sections disabled interrupts using a privileged system call. Now they are replaced with no-ops (do nothing). The stated reason is to remove interrupt locking from unprivileged code. The change could affect timing, race conditions, or security properties that relied on interrupt masking for atomicity, but the diff alone does not show an exploitable bug or a disclosed vulnerability.

This commit adds a new 'thread-local storage' (TLS) memory section for Trezor's coreapp on newer hardware models. It changes how the device saves and restores small, per-task memory areas when switching between tasks. The change is a feature implementation, not a fix for a known security bug. There is no evidence in the commit or supplied references that this addresses an active vulnerability or was disclosed as security-relevant.

This commit adds support for retrieving Tron cryptocurrency addresses on Trezor hardware wallets. It is a feature addition that extends existing address-derivation infrastructure to a new blockchain. There is no indication in the commit that it fixes a security bug or introduces a vulnerability.

This commit updates the Tron coin support in Trezor firmware to use the newer 'session' API and changes the Tron message type numbers. It also removes unused Tron transaction-signing message definitions and limits Tron support to debug builds only. There is no direct evidence in the commit of a security vulnerability being fixed; it appears to be a maintenance and integration cleanup change.

This commit changes a function parameter declaration from an empty array syntax to a pointer syntax in the Noise protocol cryptography code. It is purely a coding-style/compiler-warning fix with no functional change to the program's behavior or security.

This commit only updates version numbers and translation metadata. It does not change any program logic, fix any bug, or alter any security behavior. There is nothing here that could directly affect security.

This commit adds new Trezor firmware features for an 'Evolu' / 'Suite Sync' service. It introduces a device-bound delegated identity key, a way to export that key after user confirmation, and ways to prove possession of that key to request a SLIP-21 node or to sign a registration request with the device's Optiga certificate. The change is framed by the vendor as spam protection / anti-abuse functionality, not as a security fix. The commit itself is a feature implementation, but it touches sensitive areas: key derivation from a new per-device master secret, secure-monitor/kernel syscalls for reading a private key, and user-consent flows for exporting a private key.

This commit is a visual/UI-only fix for the Trezor T3W1 hardware wallet. It changes the font used to display Stellar transaction amounts and Bitcoin lock times on the device screen. There is no change to security logic, cryptography, transaction validation, or how the device signs anything. The only code changes are selecting a different font style and updating the corresponding screen snapshot hashes used by automated tests.

This commit is a simple revert that puts two features—PaymentRequest and GetNonce/Nonce—back into the 'experimental' category in Trezor's protocol definitions. It does not fix or introduce a security bug; it just re-labels fields and messages as experimental again and updates generated code and tests accordingly. The change is administrative: it re-enables the experimental flag so these features are only usable when a device has experimental features turned on.

This is a trivial user-interface layout change. It switches one button in a warning screen from a single-line text button to a multi-line text button so longer button labels can wrap. There is no security relevance in the code change itself.

This commit tightens how a Trezor hardware wallet decides whether an Ethereum transaction is a standard ERC-20 token transfer/approval. Previously the code guessed based on the transaction's overall shape and size; now it also checks the actual function signature bytes. The change removes an assumption that any matching transaction must be either a transfer or approval, which could have led the device to display a token-style confirmation for contract calls that only happened to look similar. There is no public claim that this was exploited, and the commit does not label itself as a security fix.