Trezor firmware

This commit changes how the Trezor emulator's Rust code is compiled. It makes debug builds use the Rust 'dev' profile (which keeps extra internal safety checks) not only when an explicit debug flag is set, but also whenever the firmware is built with Python optimizations disabled (PYOPT='0'). This is a build-hardening change for the emulator/debug environment and does not alter runtime behavior of production devices or introduce a security vulnerability.

This commit only updates version numbers and translation metadata across the Trezor firmware repository. It does not change any executable code, fix any behavior, or alter security logic. There is nothing in the diff that introduces or fixes a security issue.

This commit is a routine tooling update. It adds a new configuration field called `riscv_fw_version` to a script that generates test configuration files for the Tropic secure element model. The generated value is a simple, hard-coded version number (1.0.0). There is no indication this change fixes or introduces a security vulnerability.

This commit only changes a test file for the Tropic cryptographic module. It swaps the hardcoded key index from 0 to 31 in a unit test. There is no change to production firmware code, no security fix, and no vulnerability being introduced or patched.

This commit only cleans up import statements in Python unit test files. It removes redundant imports and switches some files to use a wildcard import from a shared test helper. There is no change to the actual firmware code that runs on Trezor devices, so this cannot affect device security or user funds.

This commit only adds two changelog files stating that a third-party library called libtropic was updated to version 3.0.0. There is no actual code change, no bug fix, and no security patch in the diff itself.

This commit is a routine compatibility update so the Trezor firmware builds and works with version 3.0.0 of an external chip library called libtropic. It renames constants, updates function signatures, swaps some source files in the build lists, and removes a couple of manual mode checks that are no longer needed. There is no indication this fixes a security vulnerability or introduces one.

This commit is a routine build-system and source-code rename. It swaps one emulator-only networking helper from the libtropic library for an equivalent one with a different filename. There is no functional change visible in the diff and no security relevance is stated.

This commit updates a third-party vendor component called ts-tvl from one version to version 2.3. The actual code changes are not visible because the diff was not provided, so we cannot tell whether this update fixes a security issue, adds a feature, or is purely routine maintenance.

This is a one-line cleanup change that removes an unused compiler flag from the build configuration for a Trezor emulator model. It does not change any runtime code, security logic, or cryptographic behavior. There is no indication this is a security fix.

This change makes the Trezor software emulator stop with a clear error message if a component called 'tropic' fails to initialize, instead of silently continuing. It is a hardening improvement for the emulator build, not a fix for a known exploitable vulnerability in real devices.

This commit changes how Trezor firmware talks to a Tropic secure chip. It replaces a larger, possibly variable slot size (R_MEM_DATA_SIZE_MAX, 475 bytes) with a fixed smaller size (TROPIC_SLOT_MAX_SIZE_V1, 444 bytes) for backwards compatibility with older Tropic firmware. The change is described as a compatibility fix, not a security fix. It adds a compile-time size check to make sure a KEK mask buffer still fits in the smaller slot. There is no direct evidence in the commit of an exploitable vulnerability, but using a smaller fixed size reduces the risk of mismatched buffer sizes between the Trezor and Tropic chip.

This commit updates a bundled third-party library called libtropic from one version to another. No code changes are visible in the commit itself, and no security-related explanation is provided. There is not enough information to determine whether this update fixes a security issue, adds a feature, or is routine maintenance.

This is a small cleanup change in Trezor's firmware build setup. It swaps one secure-memory-wiping helper for another equivalent one already used elsewhere in the project. There is no direct evidence this fixes a security bug; it appears to be a routine code-maintenance chore.

This is a small code maintenance change in Trezor firmware for a secure chip driver. It adds a new cryptographic context field to an internal data structure and wires it into an existing library handle. There is no indication this fixes or introduces a security vulnerability; it appears to be routine plumbing needed by an updated external library (libtropic).

This is a routine CI (Continuous Integration) maintenance change for Trezor firmware. It updates how automated test servers are configured so that test emulators use the same configuration file as the real firmware tests. There is no indication this fixes a security vulnerability or affects end-user devices.

This commit changes how the Trezor hardware wallet reports certain pairing errors. Previously, invalid data sent during the Trezor-Host Pairing (THP) process triggered an internal 'FirmwareError' code. Now it returns a more appropriate 'DataError' code. This is mainly a correctness and user-experience improvement: callers see a clearer error and are less likely to mistake bad host input for a device firmware bug. It does not appear to fix a memory corruption, bypass, or direct asset-stealing vulnerability.

This commit fixes how cryptocurrency addresses are visually grouped into chunks on Trezor device screens for several wallet models. Previously, addresses could be displayed with missing or incorrect spacing, which might make it harder for users to visually verify an address before approving a transaction. The fix changes the low-level text layout code and passes the chunking option through two user-interface layouts. It is a display/rendering bug fix rather than a cryptographic flaw, but because address verification is a key anti-phishing step, any display issue has security relevance.

This commit is a cosmetic wording fix for the Trezor hardware wallet's backup quiz screen. It changes how the device labels the word the user must select, switching from English-style ordinal text like '2nd' to a neutral '2 of 20' format. There is no security issue here; it is purely a user-interface and localization improvement.

This commit relaxes a version check so that Trezor devices can load translation (language) files even when the translation file's build number differs from the firmware's build number. Previously, the version had to match exactly, which could block users from changing languages after a small firmware update. The change still requires the major, minor, and patch version numbers to match, and it adds a check that the version field is exactly four parts long. There is no direct security vulnerability here; it is a usability fix.

This commit updates the regulatory information screen on the Trezor T3W1 hardware wallet. It adds new country certification icons, reorganizes the order of regions shown, and displays the device's production year on the South Korea page. There is no security-relevant change here—only user-interface text, images, and layout.

This commit fixes a UI bug in the Trezor hardware wallet where scrolling through FIDO/WebAuthn credentials could behave incorrectly. The change updates the displayed account name in place rather than recreating the whole text element each time the page changes. There is no direct evidence this is a security vulnerability; it appears to be a user-experience fix for on-screen credential navigation.

This commit fixes how the hardware's memory protection unit (MPU) is set up inside two power-management interrupt handlers. Before the fix, these interrupt routines may have run with the wrong MPU configuration, which could allow them to access memory regions they shouldn't or, conversely, crash because a needed region was blocked. The patch now switches the MPU to a safe default mode at the start of each interrupt and restores the previous mode before returning.

This is a small UI bug fix in the Trezor hardware wallet firmware. It ensures that when a user swipes between on-screen pages, the device correctly sends a 'ButtonRequest' event at the moment a new page is attached. Without this, automated tests for the device recovery process failed on the newer 'Delizia' screen layout because the expected button request was missing or duplicated. There is no indication this allows theft of funds, bypass of security, or user data exposure.

This commit fixes an off-by-one error in a debug-only assertion inside a Trezor hardware wallet screen. The assertion checks whether a button index is valid, but it previously rejected the last valid button (the 'cancel' button). The fix changes '<' to '<=' so the assertion no longer falsely triggers. This is a minor correctness fix in debug builds and does not change release behavior or user-facing security.