Trezor firmware

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 only changes the protocol definitions (the 'language' the Trezor device and apps use to talk to each other). It adds a new optional streaming mode for requesting device-authenticity proofs, so large proofs can be sent in smaller chunks instead of one big message. There is no actual device firmware logic shown here—only generated message bindings—so it is not a security fix or vulnerability by itself. It is a feature addition that could, in theory, introduce new attack surface once the corresponding firmware code is implemented, but that code is not present in this commit.

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.

This commit adds a new optional 'streaming' mode for retrieving device authenticity proofs on Trezor hardware wallets. Instead of sending all attestation data (certificates and signatures) in one large message, the device can now send it in smaller chunks. This is intended to improve reliability over lossy transports like Bluetooth Low Energy. The old one-shot mode is kept for backward compatibility. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a reliability/feature improvement.

This commit re-enables a security feature called 'MCU device attestation' for the T3W1 hardware wallet model. It is not a vulnerability fix; it restores a previously removed capability that lets the device cryptographically prove its microcontroller is genuine using a modern quantum-resistant signature scheme (ML-DSA-44).

This commit only adds and reorganizes automated tests for the device-authentication feature on Trezor hardware wallets. It does not change the firmware code that runs on the device, so it cannot introduce a security vulnerability or fix one in the shipped product. The changes make the test suite exercise both the Optiga and Tropic authentication flows, test chunking sizes, and verify that invalid requests are rejected with proper error messages.

This commit simply restores a missing Python test dependency called pytest-retry. It only affects the project's testing environment and does not change any code that runs on the Trezor device or any production software. There is no security issue here.

This is a code cleanup (refactor) of the on-screen button drawing and touch/hold logic for the Trezor hardware wallet's Caesar UI layout. It removes unused style-sheet abstractions, simplifies how buttons are described, and makes the hold-to-confirm component always assume it sits on the right side of the screen. The commit is tagged [no changelog] and contains no explicit security claims. The only behavior-visible change is a small simplification in the page component: when the left button is triggered on the first page, it now always returns a Cancel message instead of first checking whether a cancel button was configured. That change is a simplification based on an existing invariant, not a fix for a known vulnerability.

This commit only changes test files so that ten unit tests are skipped when running against the Bitcoin-only firmware variant. It does not modify the actual Trezor firmware code that users run, so it cannot directly affect device security or user funds.

This commit adds support for a new Ripple transaction type called AccountDelete to Trezor hardware wallets. It is a feature addition, not a security patch. The change lets users sign transactions that delete a Ripple account and send any remaining balance to a chosen destination. The code adds user-facing confirmation screens and enforces that a transaction cannot be both a payment and an account deletion. There is no direct evidence in the commit of a security vulnerability, but any new signing path deserves careful review because bugs could let an attacker trick a user into deleting an account or signing an unintended transaction.

This commit adds emulator-only support for a new Trezor device (T3W1) to wake from a simulated low-power sleep state when the user taps the emulated touchscreen. It only affects the software emulator build, not real hardware, and does not change how secrets or user data are handled. There is no indication this is a security fix.

This commit corrects the wrong GPIO pin assignment for the interrupt line of the Tropic01 secure chip on Trezor T3W1 hardware revisions A, B, and C. Previously the interrupt pin was set to the same pin as the power-control line, which does not match the hardware schematic. The commit message says this interrupt pin has not been used so far, so the practical security impact appears low.

This commit is a routine synchronization of translated user-interface text for the Trezor hardware wallet. It updates wording, adds missing translations, and removes obsolete translation keys across several language files. There are no code changes that affect security, cryptography, transaction signing, or device behavior.