Trezor firmware

This is a test-only change that updates how a numeric pairing code is converted into bytes for Trezor's THP (Trezor Host Protocol) pairing tests. It switches from raw binary encoding of the number to a 6-digit ASCII string encoding. The change does not touch any production firmware or host library code, only a single Python test file.

This commit fixes a bug in the Trezor Python library where a numeric pairing code was converted to raw bytes instead of being formatted as a six-digit ASCII string. The change aligns the client-side code with the expected protocol format used by the Trezor device, likely preventing authentication failures or mismatches during the CPace pairing flow.

This commit changes how a numeric pairing code is converted into bytes before being used in a cryptographic protocol called CPace. Previously the code was treated as a raw 6-byte binary number; now it is formatted as a 6-digit ASCII string (e.g., '000123') and then encoded to bytes. The change is described as a routine chore with no changelog. On its own, the diff does not show a fix for a known vulnerability, but it removes a potentially risky encoding choice that could have interacted badly with the CPace protocol.

This commit only adds explanatory comments and a small constant to the CPace cryptographic code. It does not change what the code actually does, and there is no indication of a security bug being fixed.

This commit fixes Bluetooth Low Energy (BLE) pairing behavior in the Trezor hardware wallet firmware. It changes how the device advertises itself, handles pairing requests, disconnects existing connections before pairing, and resets the advertising name after pairing ends. The changes are framed as a functional bug fix rather than a security fix, but they touch on sensitive pairing state management that could affect whether an attacker could trick the device into pairing unexpectedly or stay connected when it should not.

This commit swaps out two pre-built binary files for the T3W1 hardware model (a QA bootloader and a Bluetooth firmware blob) and updates the corresponding SHA-256 hashes in a header file. The actual code inside the binaries is not shown, so we cannot tell from this diff alone whether the change fixes a bug, adds a feature, or is purely routine. There is no mention of security in the commit message or any supplied reference.

This commit is a developer-facing refactor that moves the emulator-only debug overlay and screenshot recording logic from Python into Rust. It does not change production firmware behavior; the new features are gated behind debug/emulator build flags and are not present in release builds. There is no obvious security vulnerability introduced, but the change touches low-level display code and removes some old Python APIs.

This commit is a simple rename from 'debug overlay' to 'performance overlay' across build files and Rust source code. It changes only identifiers, feature flags, and comments; no program logic or security behavior is altered. The overlay remains an optional developer-only feature that is disabled by default.

This commit fixes the visual alignment and font of a performance debugging overlay on the Trezor Safe 5 (Eckhart layout). It changes where on-screen text is drawn so numbers are not clipped by rounded screen corners. There is no security relevance: it only affects a developer-only overlay that shows rendering timing statistics.

This commit is a user-interface improvement for the Trezor hardware wallet bootloader. It makes the Bluetooth pairing code display much larger and easier to read, and spaces out the digits. There is no security vulnerability here; it is purely a usability and accessibility change.

This commit is a cosmetic UI change for the Trezor hardware wallet's welcome screen. It replaces the old text-only welcome display with a shared logo-rendering helper and removes two unused icon image files. There is no security-relevant change visible in the code.

This commit is a cosmetic tweak for the Trezor hardware wallet's screen border. It shifts the decorative border inward by one pixel and updates the corner icons so the line looks evenly thick on different physical screens. There is no security-relevant change here.

This commit fixes a low-level crash-recovery bug in Trezor hardware wallets. If the device crashed while interrupts were temporarily disabled (a common protective state during sensitive operations), the emergency rescue code could fail to re-enable normal interrupts before showing the Red Screen of Death (RSOD). The fix adds one line to re-enable interrupts so the recovery screen works reliably. There is no direct evidence this is exploitable as an attack; it is primarily a reliability/resilience fix.

This commit changes how some Trezor hardware wallets generate a secret internal 'entropy' value used to protect stored data. For newer devices (STM32U5-based models), the entropy is now derived from a master key already inside the secure chip, using a new 'fw_type' field in the firmware vendor header. For older devices, the previous method using CPU ID and one-time-programmable memory is kept. The change also updates the vendor header format to include a firmware-type byte. There is no direct evidence in the commit of a security vulnerability or fix; it appears to be a design/architecture change.

This commit simply updates the QR code shown during wireless device setup so it points to the correct web link (trezor.io/setup/ts7) and slightly adjusts the surrounding padding. There is no security issue here.

This commit changes how special characters in translated text are normalized (converted to a standard form) from a stricter method (NFKC) to a less strict one (NFC). It also adds the masculine ordinal indicator (º) to Spanish and Portuguese font glyph sets and updates many translation strings and test snapshots. The change is a routine internationalization/translation tooling fix. There is no direct evidence in the commit that this fixes an active security vulnerability.

This is a routine font-generation tooling update. It adds a warning when a character is not supported by a font and specifically falls back the Spanish/Portuguese masculine ordinal indicator 'º' to a plain 'o' glyph. The generated font files are updated accordingly. There is no security issue here.

This commit simply deletes a one-line changelog file that described a feature ('[T3W1] Added SLIP-24 swaps.'). No source code, firmware logic, or security behavior was changed. It is a documentation cleanup only.

This commit changes how Ripple (XRP) amounts are displayed on a Trezor hardware wallet screen. Instead of gluing the number and the 'XRP' label together with a simple string join, it now uses a dedicated helper called format_amount_unit. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a formatting cleanup or consistency improvement.

This commit adds a new on-screen confirmation flow for Ripple payment requests on newer Trezor hardware wallets. It replaces a placeholder TODO with a proper user-interface that shows the recipient, memos, refund details, and trade details before signing. There is no obvious security bug in the change; it is a feature implementation that improves transparency for users.

This commit fixes a validation check in the Trezor hardware wallet's Bitcoin signing code. The device accepts 'payment request memos' that can contain different memo types, and it should reject requests where more than one type is set at once. A newly added memo type ('text details memo') was accidentally left out of the 'pick exactly one' check, so a malicious or buggy host could potentially include both a text memo and a text-details memo in the same payment request, confusing what the user sees or breaking an invariant the firmware relies on.

This commit updates the on-screen user interface shown when approving Bitcoin payment requests on a Trezor device. It replaces an older screen that merely asked whether to show details with a new screen that actually displays the payment request details (recipient, address, memos, refunds, trades, account path). There is no indication of a security bug or vulnerability fix in the change itself or the commit message.

This commit only changes test files for Trezor hardware wallet firmware. It updates which cryptocurrencies are used in automated tests, adds a new test case for a basic swap scenario, removes an outdated manual input-flow test, and adjusts which device models certain tests run on. There are no changes to the actual wallet firmware code that users rely on, so this cannot directly affect device security.

This commit only updates expected test result fingerprints (hashes) in a JSON test-fixtures file. It does not change any firmware, application, or cryptographic code. There is no direct security relevance visible in the diff.

This commit is a code cleanup that moves the user-confirmation screen for SLIP-24 payment requests out of Ethereum-specific code and into shared UI code. It does not change security checks or add new features; it only reorganizes how account, network, and token details are passed to the display layer. There is no clear security bug in the change itself.