Trezor firmware

This commit is a routine user-interface cleanup. It adds new translation strings for showing Ethereum transaction data size (for example, "Input data: 12 / 100 bytes") and moves the code that displays streaming data chunks so it can be shared across all Trezor firmware variants. There is no security-relevant change visible in the code.

This is a small, safe code cleanup in the user-interface layer of the Trezor firmware. It lets menu screens use a different visual layout type in the future, but does not change any existing behavior or fix a security problem. There is no indication of a vulnerability.

This commit is a straightforward internal code reorganization. It moves the `_DisplayHandler` class and related helper functions from one file to another within the recovery device feature, without changing what the code actually does. There is no security-relevant change visible in the diff.

This commit is a simple code cleanup: it takes an existing loop that walks the user through backing up each recovery-share and moves that loop body into a new helper method named `_backup_share`. There is no change to what the code does, what data it handles, or how it interacts with the user. It is purely a structural refactor.

This commit changes a debug-only mock file for the N4W1 hardware feature in Trezor firmware. It adds a user-facing 'hold the tag' screen that waits for a simulated tap/connection event before continuing. The change is confined to a debugging helper and does not appear to alter normal wallet security logic.

This is a small internal code cleanup in the Trezor firmware's user-interface layer. It changes how the 'show address' screen is wrapped so that the layout object is managed within a scoped context manager rather than passed directly to a helper function. There is no indication this fixes a security bug or changes user-visible behavior.

This is a code cleanup change in the Trezor hardware wallet's user-interface layer. It introduces a new 'LayoutContext' wrapper so that on-screen keyboards and menus are always used inside a 'with' block, ensuring their memory is released promptly. The commit itself does not claim to fix a security bug, but it references an internal issue (#6811) about lifetime management, suggesting it is a defensive step against possible UI object lifetime problems.

This is a routine automated dependency update by Dependabot, bumping the pinned Python protobuf package from version 6.32 to 6.33.5. The change only edits two version pins in project configuration files and contains no code changes. There is no indication in the commit that this fixes or introduces a security issue.

This commit updates the mldsa-native submodule to a new beta version and adjusts the build system and source code to use the new API names and file paths. ML-DSA is a post-quantum digital signature algorithm used for device attestation in production testing. The change itself is a routine dependency/API migration, but because it touches cryptographic verification and key generation code, it warrants a security-aware review. There is no direct evidence in the commit of a vulnerability being fixed.

This commit is a code cleanup (refactor) that moves the handling of a device certificate stored in secure memory into dedicated helper functions. It does not change what data is stored or how it is protected; it only makes the code more maintainable. There is no indication this fixes a security bug.

This commit adds hardcoded test-only cryptographic credentials used by the Trezor emulator (software simulator) for a new ML-DSA device-attestation feature. It does not change real hardware firmware. The credentials are clearly emulator-only placeholders and are not intended for production devices.

This is a code-maintenance refactor, not a security fix. It moves public HSM (Hardware Security Module) and device-authenticity root keys from a C header file into a shared JSON file, then auto-generates both the C header and a Python file from that JSON. The actual key values do not change. A few related C files are updated to use a new feature flag (USE_MCU_ATTESTATION) and consistent size constants for the ML-DSA algorithm. There is no evidence in the commit of a vulnerability being patched.

This commit fixes a bug in how the Trezor hardware wallet's secure chip (Optiga) handles masked digital signatures. The fix changes two things: it now uses the actual returned signature length rather than the maximum buffer size when parsing the signature, and it explicitly uses the NIST P-256 curve instead of a variable curve parameter when removing the masking. The bug could potentially cause signature parsing to fail or behave incorrectly, especially if the returned signature was shorter than the maximum expected size. There is no public statement linking this to an active security vulnerability or attack.

This commit only adds two new optional data fields to an existing device-authentication proof message used in Trezor hardware wallets. It extends the protocol definition and the matching generated code in Python, Rust, and the core firmware so that future firmware can include an MCU (microcontroller) certificate and signature alongside the already-present Optiga and Tropic proofs. The change is additive and does not by itself alter any verification logic, cryptographic checks, or access controls visible in the diff.

This commit adds a new hardware-based device authentication feature for the Trezor T3W1 model. It lets the device prove its identity using a cryptographic certificate and signing key stored in the microcontroller (MCU). The change is a feature addition, not a fix for a known vulnerability. There is no evidence in the commit or supplied references that this resolves an active security issue or introduces a new attack path.

This commit adds a new debug-only protocol message called DebugLinkSetBatteryState. It lets developers or test tools tell the Trezor emulator (a software version of the device used for testing) what battery and charging state to simulate. The change only touches protocol definitions and generated code; it does not add any logic that runs on a real device or handles secrets. It is marked for debug use only and is skipped in the legacy firmware build.

This commit adds a debug-only feature to the Trezor firmware emulator that lets software tests fake the device's battery and charging state. It does not change real hardware behavior. The new function is only compiled into emulator builds and only when Python optimization is disabled (debug builds). It is intended for automated testing, not for end-user devices.

This commit adds a debug-only feature that lets developers or automated tests tell the Trezor emulator what battery state to report (charge level, charging, temperature, etc.). It only works when the device is compiled in debug mode and is running in the software emulator, not on a real hardware wallet. There is no indication this is a security fix or that it exposes real user funds to risk.

This commit only adds automated user-interface tests for the battery indicator on one Trezor device model. It does not change any firmware code that users run, so it cannot introduce a security vulnerability or fix one.

This commit only adds a new test marker called 'emulator' so that certain automated tests can be skipped when running on real Trezor hardware instead of the software emulator. It does not change any wallet, firmware, or security code that end users rely on.

This commit adds a new Python helper and command-line tool to control the emulated battery state on Trezor hardware simulators (emulators). It does not change firmware running on real devices. The feature is intended for testing only and is gated behind the existing debug-link mechanism, which already requires special debug access to the device or emulator.

This is a routine developer tooling change that improves how code-coverage reports are generated for the Trezor firmware. It makes coverage measurements more accurate by using the same preprocessed source files that are actually compiled into test builds, and avoids redundant rebuilds in CI. There is no user-facing change and no security relevance.

This commit simply updates a Python testing tool called 'coverage' from version 5.5 to 7.13.5. The coverage tool is only used during software testing to measure which parts of the code were executed by tests. It is not part of the actual Trezor device firmware or wallet software that users interact with. There is no indication this update fixes or introduces any security issue.

This is a harmless build-system cleanup. It teaches the firmware build scripts to remove haptic (vibration) and RGB LED code from devices that do not have those hardware features, and it sorts the list of feature flags alphabetically for easier reading. There is no security bug being fixed here.

This commit is a code refactor in Trezor's Rust THP (Trezor Host Protocol) library. It moves responsibility for assigning channel IDs from the internal library mux to the application using the library. The change also removes the requirement that credential stores/cloners implement the Clone trait, and adds a helper allocator for consecutive channel IDs. There is no direct evidence in the commit or supplied references that this fixes an active security vulnerability; it appears to be an architectural cleanup that may make misuse harder but also places more correctness burden on the application.