Trezor firmware

This update fixes a bug in Trezor hardware wallets when signing certain Ethereum token-approval transactions. Some legitimate DeFi transactions include extra data that the wallet did not expect, which previously caused the device to crash instead of signing. The fix makes the wallet fall back to a simpler, generic signing mode for these unusual transactions. It is a reliability/usability fix rather than a theft-of-funds vulnerability, but a crash could still be used to deny service or trick a user into a less safe workflow.

This update changes how Trezor handles one specific Solana instruction (SetComputeUnitLimit) so it can optionally accept a reference to another program account. Previously the device rejected or could not parse transactions that included this extra account reference, which is used by some services such as Jito. The change is a compatibility fix rather than a clear-cut security patch, but the prior strict parsing could have caused transaction failures or user confusion when signing legitimate Solana transactions.

This is a routine dependency update generated by Dependabot. It bumps the Rust crate `tracing-subscriber` from version 0.3.19 to 0.3.20 in a Cargo.lock file. The change only affects lockfile entries and transitive dependencies used for logging output formatting. There is no indication of a security fix or vulnerability being addressed.

This commit removes code that turned off the screen backlight when a power-voltage drop (PVD) interrupt fired. The change is described as a simple internal cleanup ('refactor') with no changelog entry. It is not clearly a security fix, but removing a safety behavior during a low-power event could have minor security or reliability implications if the backlight was meant to blank the screen before shutdown.

This commit is a code reorganization (refactor) that moves the suspend/resume functionality from one part of the codebase to another. It splits the suspend module into an I/O layer and a security layer, updates include paths, and adjusts build configuration files. There is no indication of a security fix or vulnerability being addressed.

This commit is a pure code reorganization: it moves the I2C bus driver files from one directory (io/i2c_bus) to another (sys/i2c_bus) and updates all include paths accordingly. No functionality, logic, or behavior of the firmware was changed. It is a housekeeping refactor with no user-visible or security-relevant effect.

This commit only adds a new automated test for the Trezor hardware wallet. The test checks that a user can cancel a Bitcoin transaction signing flow from the amount confirmation screen on newer device models. It does not change any firmware, wallet logic, or security behavior. There is no security issue here.

This is a small debugging improvement for Trezor's Rust firmware code. It changes panic error messages so that, in debug builds, the actual panic message text is shown instead of a generic placeholder 'rs'. There is no security vulnerability or fix here—just better diagnostic output for developers.

This change adjusts how the Trezor firmware's Rust code is built for the debug software emulator. Previously, all builds used a setting that makes the program immediately stop (abort) if a panic occurs. Now, the debug emulator keeps the normal panic mechanism so that internal debug assertions can be reported instead of silently crashing. This is a build/developer-experience change, not a fix for an exploitable security flaw in shipped hardware wallets.

This commit simply adds a new digital signature entry to a JSON file that records approved language translation packages for Trezor devices. There is no code change, no bug fix, and no apparent security issue. It appears to be routine release housekeeping.

This commit is a routine translation update. It changes translated text strings in Czech, German, Spanish, French, and Portuguese, updates the cryptographic signature that verifies those translations, and refreshes the expected screen hashes used by automated UI tests. There is no code behavior change and no security issue visible in the diff.

This commit only adds a new test case for the Base cryptocurrency network. It does not change any production firmware code, so it cannot introduce a security vulnerability or fix one. It is purely a testing update.

This commit adds a new cryptographic signature entry to a JSON file that records approved translations for the Trezor hardware wallet firmware. The signature verifies that the translation data for version 2.9.5.0 is authentic and has not been tampered with. There is no code change and no direct security vulnerability visible in the diff itself.

This commit is a routine synchronization of translated user-interface text strings from the Crowdin translation platform. It updates wording in Czech, German, Spanish, French, and Portuguese translation files, refreshes the cryptographic signature that authenticates those translations, and updates the corresponding visual test snapshots. There are no code logic changes, no security fixes, and no behavior changes beyond the exact text shown on screen.

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 simply adds a new digital signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. It is a routine metadata update with no code changes and no apparent security relevance.

This commit is purely a documentation change: it compiles the release notes for Trezor firmware version 2.9.4 by moving individual changelog fragments into the main CHANGELOG files. No source code, configuration, or executable files were modified, so it cannot introduce or fix a security vulnerability on its own.

This commit is a code cleanup: it moves the Tropic chip certificate cache out of the production-test command file and into the shared Tropic driver, then exposes two helper functions so other code can fetch the cached public key and certificate chain. There is no visible security bug being fixed or introduced in the diff itself.

This commit simply removes the Italian language translation files and related font glyph definitions from the Trezor firmware. It is a routine localization cleanup with no security relevance. No code that handles cryptography, authentication, or device security is changed.

This commit is a routine cleanup of translation files for the Trezor hardware wallet firmware. It removes or empties text strings used only by the older 'Bolt' user-interface layout from newer layouts (Caesar, Delizia, Eckhart) to make translation files smaller. There is no code change, no security fix, and no vulnerability introduced.

This commit is a cosmetic user-interface change. It replaces a non-breaking space between a number and its unit (like '1.23 BTC') with a regular space so the unit can wrap to the next line on small screens. There is no security impact.

This commit only updates a generated metadata file (signatures.json) that records the latest approved translation bundle for the Trezor device. It changes a timestamp, commit hash, and Merkle root pointer. There is no code change and no security-relevant behavior change visible in the diff.

This commit adds two missing Portuguese characters, 'À' and 'ª', to the device's font files and fixes a spelling typo in a code generator file ('portugese' to 'portuguese'). It is a routine localization/typography update with no security relevance.

This commit only adds a new test case for Ethereum transactions. It does not change any production code, so it cannot directly introduce or fix a security vulnerability. The test checks how the device displays a transaction when the called function, token, and blockchain are all unknown. The commit message hints at a user-interface design concern—avoiding unnecessary warning screens so users don't learn to ignore them—but that concern is not implemented in this change.

This commit removes a safety check that ensured each memo inside a Bitcoin payment request contained exactly one memo type. The change is described by the developer as removing a redundant sanitizer, suggesting the validation is believed to happen elsewhere. Without access to the rest of the codebase or vendor confirmation, it is unclear whether this weakens security or is genuinely redundant.