Trezor firmware

This commit adds support for a new 'version 2' format for external definitions in Trezor firmware. The key change is that version 2 requires only one cryptographic signature to validate a definition, whereas version 1 required two. This is a deliberate design change, not a bug, but it reduces the number of independent parties that must sign off before a definition is trusted by the device. The commit does not by itself introduce an exploit, but it lowers the bar for an attacker who could compromise a single signing key or signer.

This commit is a minor localization cleanup. It removes a trailing period from the 'Cancel sign' translation string in older product layouts (Bolt, Caesar, Delizia) and keeps the period only in the newest layout (Eckhart). It also updates the translation signature file. There is no security relevance.

This is a UI graphics bug fix in the Trezor hardware wallet firmware. When drawing a circular progress indicator or pie-chart-like shape spanning a full 360 degrees, the code mistakenly treated it as an empty slice and drew nothing. The patch detects a full-circle span before normalizing the angles and forces it to draw all eight segments plus the center pixel. There is no direct security vulnerability here; it is a rendering correctness fix.

This commit adds a new informational field to the Trezor device's 'Features' message that tells connected software the maximum passphrase length the device supports. It does not change how passphrases are validated or stored, and it does not fix any known security bug. It is a feature addition to improve compatibility between different Trezor models and wallet software.

This commit simply raises the maximum allowed passphrase length on newer Trezor Core devices from 50 bytes to 128 bytes. It is a feature change, not a security fix or vulnerability. Older and legacy models keep the 50-byte limit. The change is accompanied by updated tests and a new device capability field so software can read the current limit.

This commit is a routine localization update. It adds one new translated button label ('Cancel sign'), fixes a punctuation mark in another label, and refreshes the generated translation files and their cryptographic signatures. There is no indication of any security issue.

This commit is a routine localization update. It adds one new user-facing button label, 'Review', to the Trezor hardware wallet's translation system and regenerates the files that store translated strings and their cryptographic signature. There is no change to security logic, no bug fix, and no vulnerability.

This is a harmless user-interface wording change. It swaps the label shown beneath two backup-related menu items from a generic 'Review' translation key to a dedicated 'Review' button translation key, and adds that button text to the English translation file. There is no security relevance.

This commit simply deletes an unused helper function called confirm_amount from four different user-interface layout files. Because the function was not being called anywhere, removing it cannot change device behavior or introduce a security issue. It is a routine code cleanup.

This commit fixes a function that shuffles arrays (like recovery-seed word order or on-screen PIN layouts) in Trezor's cryptographic code. The original code could misbehave or even crash when given very short or very long inputs, and it used a signed integer type that could turn negative in unexpected ways. The patch adds a safety check, skips shuffling when there is nothing to shuffle, and uses the correct unsigned type. The practical security impact is moderate: it removes a source of non-random or buggy shuffling that could leak information or cause crashes, but the commit itself does not claim to fix an active exploit.

This change removes unused error-message text from the bootloader's copy of the nanopb library to free up about 1 kB of flash storage. The bootloader never looked at these error strings anyway, so the change is a size optimization with no security effect.

This commit only adds new automated tests and a helper script for generating test data. It does not change the firmware's random number generator, wallet operations, or any user-facing behavior. The goal is to catch future bugs where a hardware model's entropy source might accidentally be left out of the strong randomness mix.

This commit adds deterministic (predictable) fake random-number generators for Trezor's software emulator only, so automated tests can reproduce exact outputs. It removes the old insecure-prng feature flag from production build paths and gates the new mocks behind emulator-only compile checks. The change is designed to keep fake randomness out of real hardware wallets, but it still increases the amount of insecure-prng code in the repository.

This commit simply increases the maximum size of a commonly used short text buffer in the Trezor firmware from 50 bytes to 128 bytes. The stated purpose is to support longer passphrases on Trezor Core devices, while keeping the PIN length limit at 50 bytes. There is no indication in the commit that this fixes a security vulnerability or introduces a security-relevant bug.

This is a routine code cleanup that replaces the older Optional[Type] style with the newer Type | None style in a few Python files. It also updates the project's automated style checker to enforce the newer style. There is no functional change to the code and no security impact.

This commit is a routine code cleanup that updates Python type annotations to follow a newer Python style guide (PEP 585). It replaces older-style imports like `List`, `Tuple`, and `Dict` from the `typing` module with built-in equivalents like `list`, `tuple`, and `dict`. It also adjusts the project's linting configuration to enforce this style. There is no change to runtime behavior, no security fix, and no vulnerability introduced.

This commit is a routine code cleanup that updates Python type annotations to a newer, recommended style (PEP 585). It does not change any program logic, security behavior, or runtime functionality. There is no security issue here.

This is a large but purely cosmetic code cleanup in the Trezor firmware repository. It replaces old-style Python type-hint imports (such as typing.Sequence) with their modern equivalents (collections.abc.Sequence) to follow the PEP 585 style guide. No program logic, security checks, cryptography, or user-facing behavior was changed. The commit explicitly says '[no changelog]' and labels itself as a 'chore'.

This commit is a routine code cleanup that updates Python type annotations to a newer, recommended style. It does not change what the code actually does, only how type hints are written. There is no security issue here.

This commit is a small UI cleanup in Trezor's firmware. It replaces several places where a colon was manually added to on-screen text descriptions with a helper function called with_colon(). The change only affects two visual themes (Bolt and Caesar). It is not a security fix and does not change how funds, keys, or transactions are protected.

This commit simply refreshes the digital signature metadata for translation files in a JSON configuration. There is no code change, no new feature, and no apparent security fix. It appears to be routine maintenance.

This commit only adds a new unit test file for the Solana transaction parser in the Trezor firmware. It does not change any production code, fix bugs, or alter behavior. It is purely a test/quality improvement with no security relevance.

This commit adds a single missing Portuguese-Brazilian character (É) to font files used by the Trezor hardware wallet. It is a routine translation/localization fix with no security relevance.

This commit is a routine cleanup: it removes the 'ª' (feminine ordinal indicator) character from font files and a code generator list because it is no longer used in the Portuguese-Brazil translation. There is no security relevance.

This commit removes the unused Spanish masculine ordinal indicator glyph (º) from font files and a code generator list. It is a routine cleanup with no security relevance.