Trezor firmware

This is a massive Trezor firmware commit that replaces the old SCons-based build system with Cargo (Rust's build tool) for compiling the embedded C code. It adds many new Cargo.toml files, build.rs scripts, and a custom xbuild helper crate, but does not change the actual security logic of the wallet. The main risk is that a build-system change of this size could accidentally alter compiler flags, included source files, or linker settings, which might affect the produced binary. There is no direct vulnerability shown in the diff, and the commit message explicitly says it is a feature with no changelog entry.

This is a routine automated dependency update by Dependabot that bumps the urllib3 library from version 2.6.3 to 2.7.0 inside a small internal testing tool (automatic_battery_tester). The change is a single line in a requirements file. There is no indication in the commit that this fixes a security issue, and the tool is not part of the Trezor firmware that runs on user devices.

This commit only changes a test file so that a Decred signing test is skipped when the firmware is built in Bitcoin-only mode. It does not modify any production firmware code, wallet behavior, or cryptographic logic. There is no security issue here.

This commit only changes how long hexadecimal fingerprints and hashes are displayed to users. It inserts spaces every four characters so the strings are easier to read and compare visually. There is no change to security logic, cryptography, or how firmware is verified.

This commit only adds a new test case for Solana message signing with 64 cosigners and updates the expected screen snapshots used by automated testing. It does not change any firmware code that runs on the Trezor device, so it cannot introduce a security vulnerability or fix one.

This is a minor GitHub workflow change that stops an automatic pull-request assignment job from running when the pull request is opened by a bot account (whose username ends with '[bot]'). It has no security relevance to the Trezor firmware itself or to user funds.

This commit only updates documentation links inside the Trezor firmware repository. It fixes broken links, replaces GitHub URLs with relative links, and removes a symlinked documentation file. There are no code changes and no security impact.

This commit fixes a crash in the Trezor device's on-screen 'About device' menu when the device lacks a serial number. It wraps the serial-number lookup in a try/except block and displays 'N/A' instead of crashing. There is no indication this can be exploited by an attacker; it is a robustness fix for a user-interface screen.

This commit adds a new optional sanity-check layer to the Python code that parses Trezor firmware files. It verifies that re-encoding a parsed firmware image produces the exact same bytes, and that any 'reserved' fields are all zeroes. The change is defensive: it can help detect malformed or tampered firmware images during analysis, but the strict mode is off by default, so existing behavior is preserved unless a caller explicitly opts in.

This commit only renames a single JSON key from '_reserved' to 'reserved' across 14 vendor header configuration files. No security settings, permissions, or values are changed. It appears to be a routine cleanup to match a naming convention elsewhere in the build tooling.

This commit is a straightforward internal code cleanup in the Trezor firmware's user interface code. It moves header-related helper methods (like title alignment, cancel/menu buttons, and styling) from the Frame component to the Header component. All existing call sites are updated to build a Header first and then pass it into a Frame. There is no change to user-visible behavior or security logic.

This commit simply moves a small helper function that checks whether a string contains only normal printable characters from one file to another shared location. No behavior changes, no bug fixes, and no security implications are visible in the code change itself.

This commit adds a new Trezor feature: signing and verifying Solana off-chain messages. It is a feature implementation, not a fix for a known vulnerability. The code introduces new message types, parsing logic, user confirmation screens, and client helpers. There is no direct evidence in the commit of a security bug, but any new signing path increases the attack surface and must be reviewed carefully for parsing mistakes or user-interface spoofing.

This commit only adds new automated tests for a Solana feature that signs and verifies off-chain messages. It does not change the actual wallet firmware code that users rely on, so it cannot by itself introduce a security vulnerability or fix one. The tests exercise parsing, signing, and verification logic and include checks for invalid inputs.

This commit updates the Trezor firmware's Solana support so that the standard 'Transfer' instruction can be used with multi-signature accounts. Previously, the firmware treated this instruction as non-multisig, which likely caused it to reject or mis-handle legitimate Solana transactions that required multiple signers. The change is a feature/fix to broaden supported transaction shapes, not a patch for an active vulnerability.

This commit changes one German translation string to add the word 'ist' (is) for consistency, and updates the corresponding translation signature metadata. There is no code or security change.

This commit only updates translated text strings in Czech, German, Spanish, French, and Portuguese for the Trezor hardware wallet firmware. It changes wording for things like Ethereum transaction prompts, Bluetooth device labels, backup/recovery instructions, and passphrase prompts. There are no code logic changes, no new features, and no security fixes.

This commit adds new regulatory certification screens for Brazil, Ghana, and Nigeria to the Trezor hardware wallet's user interface. It is purely a compliance/labeling change: new image files are included and a list of regulatory regions is updated. There is no indication of any security bug, vulnerability, or behavior change affecting funds or device security.

This commit is a routine user-interface update for the Trezor hardware wallet's 'About' screen. It adds a 'Made in Ostrava, Czechia' label and, on devices that use serial numbers, displays the serial number. There is no security-relevant change.

This is a small internal tuning change for Trezor's Ethereum app. It increases the amount of transaction data the device preloads from 4 KB to 6 KB before asking the user to confirm. The only visible effect is fewer back-and-forth data requests for Ethereum transactions with large data payloads. There is no direct security fix or vulnerability being patched.

This commit only adds new test cases for Ethereum transaction signing. It does not change any production code, so it cannot introduce a security vulnerability by itself. The test data includes sample transactions and their expected signatures, used to verify the device signs complex DeFi transactions correctly.

This is a routine Python code change in Trezor's firmware handling library. It adds support for a new Nordic (NRF) firmware header type and helper methods to insert cryptographic signatures into firmware image structures, plus a minor formatting tweak. There is no indication of a security vulnerability or fix.

This commit fixes how Trezor's Python library validates signatures for a new bootloader image format (BootloaderV2). Before the fix, the code ignored the signature bitmask and simply checked every signature against every public key in order. This could let an invalid or mismatched signature slip through, or cause validation to fail incorrectly. The patch makes the library read the bitmask, count signatures correctly, and only verify the signatures the image actually claims to have signed with. It also adds a missing signature-status line to the printed header. The change is in developer/CLI tooling, not the device firmware itself, so a direct attack on a real device is unlikely, but the library is used to inspect and validate firmware files.

This is a minor user-interface cleanup for the Trezor hardware wallet's Eckhart layout. It removes the warning header from a screen when the title text is empty, so users don't see a blank header. There is no security-relevant change.

This commit changes the Trezor hardware wallet so that a large secondary device-attestation proof (the MCU attestation) is only sent when the caller explicitly requests streaming support. The goal is to avoid sending one oversized response. It is a defensive hardening change rather than a fix for an active vulnerability, and the commit message does not claim it resolves a security issue.