Trezor firmware

This commit adds software 'stubs' that let the Trezor firmware emulator (a simulated version used for development/testing) compile and run on a regular computer. These stubs replace real hardware security features—such as tamper detection, secure memory, hardware encryption, and the secure chip (Optiga)—with no-op or always-success placeholders. There is no indication this code is meant for real Trezor devices, and the commit message explicitly frames it as emulator-only driver implementation. It does not appear to be a security fix or vulnerability patch.

This commit is a code reorganization: it moves the code that initializes the hardware security boundary (TrustZone) from one internal system module into a dedicated security module, and makes sure every startup program calls it at the very beginning. The actual security settings look unchanged from the diff. It is not a fix for a known bug or vulnerability, but it changes where and when sensitive hardware is configured, which could matter for security if the move accidentally changes behavior or ordering.

This commit fixes a type mismatch in the Trezor firmware emulator's bootloader code. The FIRMWARE_START symbol was declared as a pointer to bytes (uint8_t*) but was being assigned a raw memory address value. On 64-bit emulator builds this could lead to incorrect memory handling or crashes because the sizes and interpretations of the two types differ. The fix changes the symbol to a plain integer address type (uintptr_t), which is the correct way to store raw memory addresses in portable C code. This change only affects the emulator (software simulation), not real Trezor hardware.

This commit is a code cleanup that moves a small data table (the 'coreapp header') out of the processor's interrupt vector table file and into its own dedicated file. It does not change what the firmware does, only where the table is defined in the source code. There is no indication this fixes or introduces a security problem.

This commit updates the hardware wallet's build configuration files (linker scripts) so they work with a newer linker tool called LLD. The changes replace a non-standard memory permission flag 'wal' with the standard 'rw' flag, and change how empty placeholder sections reserve stack/heap/header space. There is no direct evidence this fixes an exploitable security bug; it appears to be a build-tool compatibility cleanup. However, because linker scripts control where code and data live in memory, any mistake could theoretically affect memory protections, so the change warrants careful review.

This is a code cleanup and build-fix change for the Trezor firmware bootloader. It moves the bootloader's binary header definition from a shared security file into a bootloader-specific file, and fixes the build configuration for a special continuous-integration (CI) bootloader variant. There is no direct evidence in the commit that this fixes an exploitable security vulnerability; it appears to be a refactoring and build repair.

This commit simply moves a source file from one directory to another within the Trezor firmware build system. The actual code content is unchanged. There is no security-relevant change visible in the diff.

This commit is a straightforward code cleanup: it changes the way source files locate shared header files from absolute-style paths to relative paths. There is no change to program logic, no bug fix, and no security-relevant behavior.

This commit moves a security setting for the screen framebuffer from a per-app switching routine to a one-time enable during system startup. It makes the framebuffer permanently accessible to less-privileged code, rather than toggling access on and off as apps start and stop. The change is described by the developer as a refactor and has no changelog entry. On its own it looks like a deliberate design relaxation, not an accidental bug, but it removes a layer of isolation that previously restricted unprivileged tasks from touching display memory.

This commit is a code cleanup that changes how a special testing-only feature is enabled in Trezor firmware. Previously, the feature was enabled whenever Python optimization was disabled (PYOPT == 0). Now it is enabled through a dedicated flag called USE_OPTIGA_TESTING. The feature itself—raising the Optiga security event counter to maximum—remains a debug/testing capability and is not intended for production. The change does not remove the feature; it only changes the build condition that turns it on. There is no direct evidence in the commit that this fixes an active security vulnerability.

This commit changes one line in the Trezor firmware emulator's bootloader simulation. It replaces a function that writes a single 32-bit word to flash storage with a more general 'write data' function. The change appears to be a code cleanup or portability fix for emulator behavior, not a security patch for a real device vulnerability. There is no indication in the commit that this fixes a security issue.

This commit adds a new mechanism for passing small data structures (called 'startup arguments') from one boot stage to the next inside Trezor hardware wallets. It changes how the device hands control from the boardloader/bootloader to the next firmware stage. The change is a feature addition, not a fix for a known bug or vulnerability. There is no evidence in the commit message or diff that this is a security patch or that it addresses a disclosed issue.

This commit adds a Python 'with' statement feature to Trezor's Rust-based UI layout objects. It lets code explicitly clean up a UI layout when leaving a block, and raises an error if someone tries to use an already-destroyed layout. There is no direct security bug visible in the change; it is a feature addition for explicit resource management.

This commit is a routine code cleanup in the Rust portions of the Trezor firmware. It fixes compiler lint warnings by modernizing syntax (for example replacing manual remainder checks with built-in methods, adding explicit lifetime markers, and simplifying match statements). There is no indication it fixes a security bug or changes product behavior.

This commit is a routine localization and user-interface wording update. It changes the text shown on Trezor hardware wallets for Ethereum token-contract screens, adding a new title string and adjusting labels like 'Token contract' to 'Token contract address' across different device layouts. There is no code behavior change and no security fix or vulnerability present in the diff.

This commit simply deletes an unused helper class called BusyDecoder from a cryptography file in the Trezor firmware. There is no change to active code, no bug fix, and no security-relevant behavior change.

This commit replaces ordinary byte-string comparisons with a constant-time equality check (consteq) when verifying authentication tags in Trezor's THP (Trezor Host Protocol) cryptography. In theory, a standard '==' comparison can leak timing information that might help an attacker forge or tamper with encrypted messages. The change is defensive and reduces the risk of timing side-channels, but the commit itself does not claim a fix for any known exploitable vulnerability.

This commit is a routine user-interface change: it adds a new optional 'kernings' field to font description structures in the Trezor firmware's Rust code. Every font is simply set to 'None' (no kerning data), so nothing actually changes in behavior. There is no security issue visible in this patch.

This commit regenerates font data files for the Trezor firmware user interface. It adds optional kerning (letter-spacing adjustment) tables to several fonts, gated behind a compile-time feature flag named `ui_font_kerning`. Other fonts simply add a `None` kerning placeholder under the same feature flag. There is no indication of a security fix or vulnerability being addressed.

This commit is a routine regeneration of font data files used for displaying translated text on Trezor hardware wallets. It only changes glyph bitmap data for accented characters in various languages and font styles. There is no executable code change, no change to cryptographic logic, and no indication of a security fix or vulnerability.

This commit only changes automated test code for firmware upgrade scenarios. It does not modify the Trezor firmware itself, wallet logic, or any code that runs on user devices. There is no security-relevant change to end users.

This commit is a test-only cleanup that renames parameters, refactors emulator selection logic, and fixes test helpers for navigating on-screen keyboards during recovery tests. It does not change any firmware, device, or production code, and there is no indication it fixes or introduces a security vulnerability.

This is a routine build-system cleanup. It lets the firmware compile without the optional telemetry feature by replacing a hardcoded feature name with a variable. There is no security bug being fixed here.

This is a clean-up change in the build system for the Trezor hardware wallet firmware. It introduces a dedicated feature flag called 'n4w1' so the code no longer decides behavior based on the hard-coded device model 'T3W1'. There is no user-facing behavior change and no security fix or vulnerability introduced.

This commit restores an initial on-screen summary step when confirming large Ethereum transaction data on newer Trezor device layouts (Delizia and Eckhart). It is a user-experience fix, not a security patch, and does not change how transaction data is validated or signed.