Trezor firmware

This commit only adds a new automated test for the Trezor hardware wallet. It simulates a user pressing the 'back' button while confirming a Bitcoin transaction amount, then completing the transaction normally. There is no change to the actual wallet firmware or production code, so it does not introduce or fix any security issue on its own.

This commit only updates expected test result fingerprints (hashes) in a UI test fixtures file and adds one new test case entry. It does not change any firmware, application, or cryptographic code. There is no indication of a security fix or vulnerability.

This commit only renames an internal test helper method from `_visit_menu_items` to `visit_menu_items` and adds a few calls to it in automated test scripts. It does not change any production firmware or device behavior. There is no security issue here.

This commit only updates version numbers and translation metadata. It changes the firmware version from 2.9.5 to 2.9.6, the secure monitor version from 1.0.4 to 1.0.5, and updates translation file headers and their signed metadata. There are no code changes that affect security or functionality.

This is a large cleanup commit that improves Python type annotations and fixes minor code-quality issues across build tools, helper scripts, and test utilities. It does not change any security-critical firmware behavior, cryptographic operations, or device-facing code. There is no indication this commit fixes a security vulnerability.

This is a routine housekeeping change to the project's code-style tooling. It removes a special 'limited' flake8 pass and makes all Python files follow the same style rules. There is no change to the actual wallet firmware or any user-facing behavior.

This commit only changes how the project runs its internal Python type-checking tool (Pyright). It expands type-checking coverage to more folders and adds a Makefile shortcut. There is no change to the actual wallet firmware, cryptography, or any user-facing behavior, so it has no security relevance.

This commit simply removes an outdated automated test that checked whether some Python helper scripts were compatible with old Python versions (3.7–3.9). It does not change any wallet, firmware, or security-sensitive code. There is no indication this is a security fix or that it introduces a vulnerability.

This is a minor test-only fix for the Trezor firmware test suite. It changes how a simulated user navigates through a device setup screen during automated testing so that the test visits an additional on-screen amount confirmation page. It does not change any production firmware code, cryptographic logic, or user-facing behavior, and there is no indication it fixes a security vulnerability.

This commit only updates expected test result hashes (called 'fixtures') in a single JSON file used for automated user-interface testing. No actual product code, cryptography, or device behavior was changed. It is a routine test-maintenance change with no security relevance on its own.

This commit is a test-infrastructure and UI-layout change for the upcoming Trezor Safe 5 (Eckhart layout). It lets automated UI tests detect whether a text screen has an external menu, and it swaps a red cancel menu item for a dedicated themed cancel button. There is no security-relevant behavior change visible in the diff.

This commit changes the default value of an optional UI parameter called `info` from `True` to `False` in a function that displays confirmation screens on Trezor hardware wallets. The change only affects documentation-style comments and a generated mock file, making the documented default match the actual implementation. There is no direct evidence this fixes a security vulnerability.

This is a minor Rust code cleanup that removes a compiler warning in non-debug builds. The change splits one function into two versions: one for debug builds that sets a test-only flag, and one for release builds that does nothing. There is no security-relevant change to actual device behavior.

This commit simply removes an 'experimental' label from a test file. It does not change any production code, security behavior, or test logic. There is no security relevance.

This commit removes the 'experimental' label from two existing Trezor features—PaymentRequest (used in several cryptocurrency transaction flows) and GetNonce (a management message). It also removes the need to enable an 'experimental features' flag to use them. The change is a feature graduation, not a security fix. There is no evidence in the commit of a vulnerability being patched.

This commit swaps out the 'ecdsa' Python library for the more widely used 'cryptography' library when verifying digital signatures on Trezor legacy firmware updates. It is a maintenance-style dependency change. There is no direct evidence in the commit that it fixes an active security vulnerability, but moving away from the older 'ecdsa' package reduces long-term supply-chain and implementation risk.

This is a routine Python dependency lock file update that removes the 'ecdsa' package from the project's dependency list. There is no indication of a security fix, vulnerability, or malicious change in the commit itself.

This commit changes the default build settings for the Trezor firmware so that a hardware security component called Tropic is enabled by default for real hardware builds, while keeping it disabled only for the software emulator used on PCs. It also removes the explicit default values for disabling Optiga and Tropic from the Makefile, making them optional overrides instead. There is no indication of a security vulnerability or fix in the change itself.

This commit only adds new expected screen-shot hashes (called 'fixtures') for an automated user-interface test covering the payment-notification feature. No firmware code, protocol handling, or cryptographic logic was changed. It is a test-data update and does not affect device security.

This commit adds a new feature to Trezor hardware wallets that lets users confirm on the device when they are buying cryptocurrency with regular money (fiat) through a third-party service. It changes how payment requests are verified and displayed on the device screen. The change removes the requirement that a payment amount be included in the request for these fiat-to-crypto purchases, because the amount being spent is in regular currency rather than cryptocurrency.

This commit only adds a new automated test for an existing feature called payment_notification, and makes a small helper function in the test code tolerate missing output data. There is no change to the actual Trezor firmware or to any code that runs on the device. It is a test-only change and does not introduce or fix a security issue.

This commit simply adds a routing entry so that when the Trezor device receives a 'PaymentNotification' message, it knows which internal module to run. There is no visible security fix or vulnerability here—only a new message handler being wired up.

This commit changes how Trezor handles payment requests that are not tied to a specific cryptocurrency coin type. Previously, payment notifications used a placeholder coin ID of 0 (Bitcoin). Now they use a new 'undefined' marker (0xFFFFFFFF). The change also adds a safety check so that refund memos cannot be used when no coin type is defined, because Trezor cannot hold coins of an undefined type. This appears to be a defensive refactor rather than a fix for an active vulnerability, but it removes a potentially misleading use of Bitcoin's coin ID in non-payment contexts.

This commit fixes two places in Trezor's payment-request handling where error objects were created but never actually thrown (missing 'raise'). One missing raise meant a payment request with memos but no nonce would be accepted instead of rejected; the other meant an unknown memo type would be silently ignored instead of rejected. The patch adds the missing 'raise' keywords, refactors nonce handling to support unit testing, and adds tests to confirm the errors are now raised. It is a genuine bug fix, but the practical security impact is bounded because the verifier still checks the cryptographic signature before any payment is approved.

This commit only changes the project's Python linter configuration file (.pylintrc) to enable two additional code-quality checks: 'pointless-exception-statement' and 'pointless-statement'. These checks flag code that has no effect, such as an expression or exception object written on its own line without being raised or used. There is no change to the firmware source code, runtime behavior, or any security-sensitive logic. It is a routine tooling/development hygiene change.