This is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.
This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…
This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…
This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…
This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…
No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…
This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…
test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…
Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…
This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…
Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…
No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…
This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…
This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…
Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …
This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…
This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…
No security-relevant signals detectedPure feature removal / code cleanup
This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…
No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …
This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…
Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum