Trezor firmware

This commit simply deletes an unused helper class called BusyDecoder from a cryptography file in the Trezor firmware. There is no change to active code, no bug fix, and no security-relevant behavior change.

This commit replaces ordinary byte-string comparisons with a constant-time equality check (consteq) when verifying authentication tags in Trezor's THP (Trezor Host Protocol) cryptography. In theory, a standard '==' comparison can leak timing information that might help an attacker forge or tamper with encrypted messages. The change is defensive and reduces the risk of timing side-channels, but the commit itself does not claim a fix for any known exploitable vulnerability.

This is a minor code cleanup that simplifies a type annotation and removes a now-unnecessary runtime type check. It does not change security behavior or fix any vulnerability.

This commit only changes Python type annotations for the loop.Task class, adding a generic type parameter [None]. It does not alter any runtime behavior, logic, or security checks in the Trezor firmware code.

This commit only updates the project's README file. It expands the description of the 'core' folder to mention additional Trezor Safe hardware models and makes minor grammar and formatting fixes. There are no code or security changes.

This commit fixes the Trezor Python host library so it correctly handles a protocol optimization called 'piggybacked ACKs.' In the Trezor THP (Trezor Host Protocol), a data message can also carry an acknowledgment (ACK) bit, meaning one side can confirm it received the previous message while simultaneously sending new data. Previously, the Python library apparently treated such combined messages as invalid ACKs and would keep waiting or retry, which could cause communication failures or timeouts. The change lets the library accept the ACK part of such a message, save the data part for the next read, and continue normally.

This commit only adds new user-visible text labels for two backup types ('N4W1 backup' and 'Wordlist backup') to the Trezor firmware's translation system. It does not change any security logic, cryptographic code, or user-flow behavior. The strings are empty on most device layouts and only populated for the 'Eckhart' layout. The translation signature metadata was also updated as part of the normal build process.

This is a small internal code cleanup in the Trezor firmware's device-recovery flow. It moves the 'invalid mnemonic' warning screen from one helper object into another function and switches the control flow from returning an awaitable to raising a custom internal exception. There is no user-visible behavior change and no security fix or vulnerability introduced.

This commit is a routine cleanup that removes informal developer notes ('!@# TODO' markers) from six source files and makes one tiny code improvement (using an unsigned integer conversion function). There is no security-relevant change and no indication of a vulnerability being fixed.

This commit simply raises a test-coverage threshold from 84% to 85% for all hardware models in the project's continuous-integration workflow. It removes a temporary exception that had been made for one model (T3B1). There is no change to the firmware code that runs on devices, no bug fix, and no security-related content.

This commit updates the Trezor firmware's translation (language) file parser to support a new version 2 format. It adds support for reading font kerning data (small spacing adjustments between letter pairs) and relaxes a strict check that previously rejected any trailing data after the font section. The change is a feature update, not a documented security fix, but it touches low-level binary parsing code where mistakes can create security risks.

This commit updates how the Trezor device calculates spacing (kerning) between pairs of text characters so it also works for non-ASCII characters used in translations. It is a UI rendering feature change, not a security fix.

This commit fixes a text-rendering bug in the Trezor hardware wallet's user interface. Previously, when laying out text on screen, the code measured each character's width individually but forgot to add the small spacing adjustments (called kerning) between certain pairs of letters. This could cause text lines to be slightly misaligned or overflow their intended boundaries. The fix tracks the previous character and adds the correct kerning amount to each character's width during layout.

This commit is a routine feature addition to the font-generation tooling for the Trezor hardware wallet firmware. It teaches the build-time font generator to read kerning (letter-spacing adjustment) data from TrueType font files and include that data in the generated Rust font tables. There is no indication this change fixes a security bug or introduces a security-relevant behavior.

This commit only updates a large test data file (tests/ui_tests/fixtures.json) used for UI regression testing. It changes expected screen-shot hashes for many test cases but does not modify any firmware, application, or cryptographic code. There is no indication of a security fix or vulnerability.

This commit updates an internal font-generation tool so that it also extracts character spacing (kerning) data for non-English characters. It is a build-time developer script change with no effect on device firmware at runtime and no security relevance.

This commit refactors how font kerning (fine-tuning space between letter pairs) is stored and looked up in the Trezor firmware. It changes the data structure from a flat list of triplets to a two-level index/pairs table, adds a Rust feature flag to enable or disable kerning, and updates the font generation tools to extract kerning from modern OpenType GPOS tables. The changes are primarily a data-format and build-tooling improvement, not a fix for a known vulnerability. The commit does not describe itself as security-related.

This commit updates the Trezor library's translation-blob generator from version 1 to version 2. The main change is adding support for a new 'kerning table' that adjusts spacing between font characters. It also adjusts how font glyph data is read from JSON files. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a feature update for font rendering.

This commit changes the font system so that kerning (spacing adjustments between letter pairs) can be omitted when generating a font. It is a build/code-generation feature change, not a security fix or vulnerability.

This commit adds font kerning support to Trezor's Rust-based UI text rendering. Kerning adjusts the spacing between specific pairs of characters to make text look better. There is no security issue visible in the change; it is a normal typography feature.

This commit regenerates font data files for the Trezor firmware user interface. It adds optional kerning (letter-spacing adjustment) tables to several fonts, gated behind a compile-time feature flag named `ui_font_kerning`. Other fonts simply add a `None` kerning placeholder under the same feature flag. There is no indication of a security fix or vulnerability being addressed.

This commit is a routine user-interface change: it adds a new optional 'kernings' field to font description structures in the Trezor firmware's Rust code. Every font is simply set to 'None' (no kerning data), so nothing actually changes in behavior. There is no security issue visible in this patch.

This commit is a routine regeneration of font data files used for displaying translated text on Trezor hardware wallets. It only changes glyph bitmap data for accented characters in various languages and font styles. There is no executable code change, no change to cryptographic logic, and no indication of a security fix or vulnerability.

This commit is a test-only cleanup that renames parameters, refactors emulator selection logic, and fixes test helpers for navigating on-screen keyboards during recovery tests. It does not change any firmware, device, or production code, and there is no indication it fixes or introduces a security vulnerability.

This commit only changes automated test code for firmware upgrade scenarios. It does not modify the Trezor firmware itself, wallet logic, or any code that runs on user devices. There is no security-relevant change to end users.