Trezor firmware

This commit only removes unused link definitions from several changelog files. It does not change any software code, behavior, or security functionality. There is no security issue here.

This commit simply changes one version number in a release metadata file, from 2.11.2 to 2.12.0. There is no code change, no bug fix, and no security-related content.

This update fixes how Trezor displays Solana transactions that use Address Lookup Tables (ALTs). Previously, the device could misidentify or fail to show the real recipient when an ALT was involved, which might let an attacker trick a user into approving a transfer to an unexpected address. The patch also blocks ALT references in payment requests and some staking flows where the device cannot safely verify the destination.

This patch changes how a Trezor hardware wallet handles EIP-712 typed data signing for Ethereum. It now caches (stores) the values shown to the user for the domain's name and version fields, and reuses those same cached values when later computing the cryptographic hash. The goal is to prevent a malicious computer or app from showing the user one set of values on screen, but then tricking the device into signing a different set of values. The changelog file labels this as a security fix: 'Cache confirmed EIP-712 domain.'

This commit simply adds a new cryptographic signature entry to a JSON file that records approved translation data for Trezor devices. There is no code change, no bug fix, and no visible security issue. It appears to be routine release housekeeping: signing the translation bundle for firmware version 2.11.2.0.

This commit simply 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, no bug fix, and no visible security issue. It appears to be routine release housekeeping.

This commit replaces the signed bootloader binary for the Trezor T3W1 hardware wallet model and updates the matching cryptographic hash list. The change is a routine version bump from bootloader version 2.1.16.0 to 2.1.17.0. The commit message and diff provide no information about why the bootloader was rebuilt or whether any security issue was fixed. Because the actual bootloader binary is a compiled blob, its contents cannot be reviewed from this diff alone.

This update fixes a bug in how Trezor hardware wallets classify accounts inside Solana transactions. The bug could mislabel read-only signer accounts as writable, or writable accounts as read-only. Because Trezor uses these labels to decide what the user must approve on screen, a crafted transaction could trick the wallet into showing a harmless-looking account while actually requiring it to sign or authorizing unexpected changes. The changelog files explicitly mark this as a security fix.

This commit updates a QA/testing bootloader binary and its recorded cryptographic hash for the T3W1 hardware model. It is a routine development chore with no visible security fix or vulnerability.

This commit is a documentation-only changelog update for the Trezor firmware releases core 2.11.2 and bootloader 2.1.17. It does not change any code. The changelog lists several previously fixed security issues, including bugs in Solana account handling, EIP-712 domain caching, and an out-of-memory fix. Because the actual code changes happened in earlier commits, this single commit cannot introduce or directly fix a vulnerability, but it confirms the vendor considers multiple items security-relevant for the release.

This commit replaces a binary file called secmon.bin for the T3W1 hardware model with a newly built version. The diff shows only that the binary file changed; no source code or human-readable documentation is included, so we cannot determine from the commit itself whether the change fixes a security issue, adds a feature, or is routine maintenance.

This commit only updates changelog files by removing issue reference numbers (like [#246], [#248], [#249]) from three existing security-related entries. It does not change any source code, firmware behavior, or fix any bug. The actual security fixes were already made in earlier commits; this is purely a documentation formatting cleanup.

This commit simply updates a timestamp and a matching numeric version constant used for Ethereum network definitions in Trezor firmware. There is no code logic change, no security fix, and no vulnerability present in the diff.

This commit only updates changelog files. It renames an upcoming release version from 2.11.2 to 2.12.0 and removes one feature note about MCU device attestation from the T3W1 changelog. No code, logic, or security behavior changes are present.

This commit simply updates the version of a third-party GitHub Action used to install the Nix package manager in Trezor's automated build and test workflows. It is a routine dependency bump with no visible security relevance to the Trezor firmware or device itself.

This commit fixes a labeling error in the Trezor firmware's protocol definitions. Two message types used for device authenticity checks had their directions swapped: one was marked as outgoing when it should be incoming, and the other as incoming when it should be outgoing. The fix only changes metadata annotations and the matching generated Rust code; it does not change actual message handling logic. Because the patch is small and limited to generated descriptors, the direct security impact is low, but incorrect wire direction metadata could theoretically confuse host software or protocol validation tools.

This commit updates the on-screen confirmation prompts shown when signing Stellar transactions on Trezor hardware wallets. It does not change how transactions are validated or signed, but it reorganizes and improves the clarity of what the user sees before approving. The changes are purely user-interface related, with updated test snapshots reflecting the new screen layouts.

This commit is a user-interface improvement for Tron (TRX) transfers on Trezor hardware wallets. It changes the on-device confirmation screens to show the sending account name, derivation path, recipient address, and amount in a clearer layout. There is no indication it fixes a security vulnerability; it is a usability and consistency refactor.

This commit is a routine housekeeping change that only updates version numbers in several files. It does not change any program logic, fix any bug, or alter any security behavior. There is nothing here that could be exploited or that affects user security.

This commit adds a new user-facing setting called 'tap to wake' to the Trezor hardware wallet firmware. It lets users choose whether tapping the touchscreen wakes the device, and stores that preference in device memory. It also adds the low-level system calls needed for the firmware to turn the feature on or off. There is nothing in the commit that fixes a bug or addresses a security vulnerability.

This commit simply adds a way for the device's Python code to ask whether the hardware supports waking from sleep by touch, and to turn that feature on or off. It is a normal feature-exposure change with no security bug visible in the diff.

This commit is a straightforward build-system wiring change for the Trezor T3W1 hardware wallet. It enables a feature called USE_TOUCH_WAKEUP, which lets the device wake from a low-power suspend state when the touch screen is touched. The change only affects how firmware is compiled for specific T3W1 revisions and does not alter security-critical code, cryptographic operations, or user data handling. There is no indication this is a security fix or vulnerability patch.

This commit adds a user-facing 'Tap to Wake' on/off toggle to the device menu on the Trezor T3W1 hardware wallet. It stores the preference in device storage and applies it at startup and when settings are reloaded after unlocking. There is no security issue visible in the change.

This commit adds a new power-saving feature for Trezor hardware wallets: the device can now optionally wake from suspend when the touchscreen is touched. It restructures how the display and touch drivers suspend and resume, choosing between a 'light sleep' path (screen stays powered, touch sensor stays armed) and a 'full shutdown' path. The change itself is a feature implementation, not a fix for a known vulnerability, and there is no direct evidence in the commit or references that it addresses a security bug.

This commit only adds a help description (docstring) to an existing command-line option. No code behavior changed, so it has no security effect.