Trezor firmware

This commit only rewrites code comments in a header file to use a more formal documentation style. No actual program logic, function behavior, or security checks were changed. It is not a security fix and does not introduce any security issue.

This commit updates the production-test configuration for a Trezor hardware model (T3W1 revC) to use a newer revision of an external secure-element firmware file and a matching compile-time identifier. It is a build-configuration change, not a patch to cryptographic or wallet code. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine hardware bring-up or compatibility update.

This commit adds a visual LED effect and a short 'finalized' animation to the hold-to-confirm action on Trezor's newer Eckhart-style user interface. It changes when the device reports a confirmation: instead of confirming the instant the user releases the button, the device now waits for a brief 500 ms animation to finish. During that animation it ignores further button input and lights the RGB LED in a color matching the on-screen confirmation. There is no indication this fixes a security bug; it appears to be a user-experience and visual-feedback feature.

This commit adds a new device state flag so the Trezor hardware wallet can tell a connected computer: 'this session replaced an existing channel, so the user does not need to confirm again.' The host-side library is updated to recognize the new state. It is a feature change, not an obvious vulnerability fix, but it touches the authentication/authorization boundary between device and host.

This commit simply shortens a French translation string used on the device screen. It changes 'Effacer les données de l'appareil' to 'Effacer l'appareil' and updates the corresponding translation signature file and UI test snapshots. There is no code behavior change and no security relevance.

This commit fixes a regression in the Trezor hardware wallet's user-interface code. A previous change had started waiting for a synchronization signal (called a 'mailbox') during every button request, but that wait was only needed for newer THP-style communication. On older non-THP devices, the extra wait could cause the device to hang or behave incorrectly when confirming actions on screen. The patch restores the old behavior for non-THP devices while keeping the new behavior for THP devices.

This commit is a small hotfix in Trezor's factory production-test tool (prodtest), which is used during manufacturing, not in normal end-user wallets. It changes how a certificate read from the Infineon OPTIGA secure chip is parsed. Previously, the code carefully checked a multi-certificate chain format; now it simply skips 9 bytes and assumes there is only one certificate. The change removes safety checks and could make the tool accept malformed or unexpected certificate data, but it only affects an internal manufacturing diagnostic command, not the wallet firmware users rely on for funds.

This is a tiny type-hint cleanup in a logging helper. It changes the signature of an internal no-op function so that static type checkers better match how it is actually used. There is no runtime behavior change, no security fix, and no vulnerability.

This commit fixes a bug in Trezor's T3W1 hardware wallet where, if a user first paired their device over USB instead of Bluetooth, the device failed to remember the computer/app name for later use. The fix makes sure the host and app name are saved during credential-based pairing even when there is no Bluetooth MAC address. There is no direct evidence this is a security vulnerability, but missing pairing metadata could weaken future security checks or user trust.

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

This update fixes a Bluetooth pairing screen bug in Trezor hardware wallets. Previously, if an already-paired (bonded) host device connected while the wallet was showing a pairing screen, the wallet did not automatically exit that screen. The fix adds a new internal event, 'pairing not needed,' so the user interface can close the pairing screen in that situation. The change is a user-experience and minor reliability fix; the commit itself does not describe a security vulnerability.

This commit fixes a potential integer overflow in the Trezor hardware wallet's storage code. A variable that holds a flash memory offset was declared as a 16-bit unsigned integer (uint16_t), which could overflow if the sector offset plus the amount of data already written exceeds 65,535. The fix widens that variable to a 32-bit unsigned integer (uint32_t), giving it enough room for larger flash addresses. If exploited, this kind of overflow could corrupt where data is written in the device's storage, potentially leading to data loss or unexpected behavior.

This commit only adds a missing cleanup step in the project's build Makefile. It ensures that when developers run 'make clean', a newly introduced emulator build directory for the production-test tool is also deleted. There is no change to device firmware, no security fix, and no vulnerability.

This commit adds a debug-only log message that records when a fragmented THP (Trezor Host Protocol) message has been successfully put back together. It does not change how messages are processed, validated, or secured. The logging is wrapped in `__debug__`, meaning it is normally stripped out of production firmware builds. There is no security-relevant change visible in the diff.

This commit only adds a debug-only error log message when a Trezor hardware wallet's THP (Trezor Host Protocol) channel reports an error. It does not change how errors are handled, what data is sent, or any security behavior. The logging is wrapped in `if __debug__:` so it only runs in debug builds and is stripped from production firmware.

This is a small bug fix in the Trezor hardware wallet firmware. It clears a temporary communication channel when the device reports it is locked during a specific handshake process. Without the fix, the device could get stuck alternating between two error states, potentially disrupting normal USB communication and requiring a reconnect or restart. There is no direct evidence this can be used to steal funds, but any disruption to a security device's communication channel is treated cautiously.

This commit removes a small optimization in the Trezor firmware's THP (Trezor Host Protocol) message reassembly code. Previously, small ACK (acknowledgment) packets used a slice of the existing packet buffer instead of allocating a separate buffer. Now all packets, including ACKs, use the same buffer allocation path. The change is described by the developer as a simplification that does not affect security because the buffers are already owned by the channel. There is no direct evidence of a security vulnerability being fixed.

This commit simply deletes two helper functions that were no longer being used anywhere in the code. It is a routine cleanup with no visible security effect.

This is a minor code cleanup: a developer removed an unused channel ID argument from an internal helper class called Reassembler. There is no user-visible change, no bug fix, and no security relevance in the commit itself.

This commit only adds on-screen progress indicators to several cryptocurrency signing flows (EOS, Ethereum, Stellar). It does not change any security logic, cryptography, or transaction validation. The large diff is mostly updated test screenshot fingerprints (fixtures.json) because the new progress screens change the device's displayed images during automated UI tests.

This commit is a routine user-interface redesign for the Trezor hardware wallet (specifically the T3W1/Eckhart layout). It moves the name of the connected app from the Bluetooth connection button onto a separate 'Host Info' screen, and adjusts how long text is clipped in buttons. There is no security-relevant change here.

This is a routine user-interface cleanup for the Trezor hardware wallet's new 'Eckhart' layout. It simplifies how long button labels scroll (marquee) so that only the smaller 'subtext' line uses the scrolling animation, rather than having two separate rendering paths. The change only affects on-screen text display and updates the corresponding screen-shot test hashes. There is no indication it fixes or introduces any security vulnerability.

This commit adds a new cryptographic signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. There is no code change and no visible security defect. It appears to be a routine administrative step to authorize a new set of translated strings.

This commit swaps out several pre-built binary files for the T3W1 hardware model: a newer bootloader version, a security monitor binary, and a Bluetooth firmware binary. The change is described as a routine chore with no changelog entry. Because the files are binary blobs, the actual code changes inside them cannot be inspected from the diff alone, and there is no stated security relevance.

This commit simply adds a new firmware version number (2.9.2) for a new hardware model (T3W1) to a release tracking file. It does not change any code, cryptographic logic, or security behavior. There is no security issue here.