Trezor firmware

This commit is a minor user-interface cleanup. It removes a fallback English string ('Path ...') that was not part of the device's translation system and instead reuses an already-translated derivation-path label. It also stops the wallet from showing the same account information twice on screen when no proper account name is available. There is no security issue here.

This commit adds a back button (swipe-down gesture) to the transaction summary screen on Trezor's Delizia and Eckhart UI layouts. Previously, the summary screen only allowed swiping up to proceed to the hold-to-confirm step. Now, when the caller requests it, users can swipe down to go back. This is a user-interface feature change, not a security fix or vulnerability.

This commit changes how the Trezor hardware wallet displays a single property on screen. Previously, passing one property as a list used a different screen layout than passing the same property as a plain string. Now both cases use the same ConfirmValue screen. This is a UI consistency fix with no obvious security impact, though any UI change can in principle affect what the user sees and approves.

This commit is a large but purely cosmetic refactor of on-screen text labels across Trezor firmware. It removes trailing colons from many prompts (e.g., changing 'New fee rate:' to 'New fee rate') and adjusts capitalization for consistency. There is no change to security logic, cryptography, transaction validation, or how user confirmations work.

This commit adds a simple read-only command called 'crc-status' to Trezor's production-test tool. It lets a factory technician ask the device whether automatic CRC checks are currently turned on or off. The command does not change any settings, access secrets, or affect normal wallet operation. It is purely informational.

This commit fixes a tiny bug in Trezor's factory production-test command-line tool. The tool can require a CRC32 checksum at the end of each command to catch typos. The bug was that the checksum was accidentally calculated over an extra space character that sits just before the checksum value, so the device would reject commands whose checksum was computed the 'obvious' way. The patch removes that extra space from the checksum calculation and updates the README examples. It only affects the production-testing CLI, not normal wallet operation.

This is an automated dependency update by Dependabot that bumps the Python protobuf library from version 6.32.0 to 6.33.5 in the project's lock file. It also removes an unused 'ecdsa' dependency entry. There is no indication in the commit itself that this fixes a known security vulnerability, and no security advisory was supplied. Dependency updates can in principle include security fixes, but this change alone does not demonstrate any exploitable flaw.

This commit fixes a build configuration issue for the Trezor hardware wallet emulator. It makes sure that telemetry-related code (which reads device health data like temperature and battery statistics) is included when building the software emulator, and it adds a missing workflow decorator to the Python helper that requests telemetry. There is no direct security vulnerability here; it is a build/test fix that enables a feature to work correctly in the emulator.

This is a routine automated update by Dependabot that bumps the Python 'wheel' development dependency from version 0.45.1 to 0.46.2 in the project's lock file. It only changes a package metadata entry and does not alter any device firmware, wallet logic, or runtime code. There is no indication this fixes or introduces a security issue.

This commit changes the default logging setting on Trezor hardware wallets from 'no logging' to 'log warnings'. It is a routine configuration change that makes the device record more diagnostic information by default. There is no indication this is a security fix or introduces a security problem.

This commit is a code-quality refactor in Trezor's firmware that changes how the app loader reports failures. It replaces simple true/false return values with detailed error codes, adds cleanup paths, and makes the kernel halt if app-cache or app-loader initialization fails. The changes do not appear to fix a known exploitable bug, but they harden error handling and could prevent subtle failures from being silently ignored.

This commit simply adds a new error code constant named TS_EACCES (matching the standard Unix 'permission denied' code EACCES) to the Trezor firmware's internal error-handling library. It only defines the constant and its string representation; no code actually uses it yet. There is no functional change to device behavior and no security fix or vulnerability present in the diff.

This commit is a code cleanup: it replaces several copies of the same small block of code with a single helper function called systask_set_mpu(). The helper does exactly the same thing as the old repeated code—configures memory protection for an applet if one is attached, and does nothing otherwise. There is no change in behavior or security boundary.

This commit fixes a subtle C macro bug where a status value could be evaluated twice. In some cases, the value used for logging could differ from the value actually stored as the error result, which might hide or misreport what went wrong inside the Trezor firmware. The patch stores the status in a variable first, then logs that same stored value so the two always match.

This commit adds automatic error logging to internal Trezor firmware macros that handle failed security and status checks. It is a diagnostic/debugging improvement, not a fix for a security vulnerability. The change only affects what information is logged when errors already occur; it does not change how errors are handled or what code is allowed to run.

This commit simply widens the allowed version range for the Python 'click' command-line library used in Trezor's Python tools. It does not change any device firmware, wallet logic, or security-sensitive code. There is no indication this is a security fix or that it addresses any vulnerability.

This commit fixes a behavior quirk in the Python Trezor client library's cancel() method. Previously, calling cancel() on a TrezorClient object would use a session-level cancel that swallowed the Cancelled exception, which could hide the fact that the operation was cancelled from the main application flow. The fix makes cancel() simply send a Cancel message and lets the normal flow receive the ActionCancelled failure. This is a library-side correctness fix; it does not appear to be a security vulnerability in the hardware wallet firmware itself.

This is a straightforward bug fix in the Python command-line tool `trezorctl`. A missing internal variable (`_version`) caused the `get-session` subcommand to crash with an error when used with older (legacy) Trezor devices. The patch adds the missing variable declaration and resets it when the connection closes. There is no security vulnerability here—just a broken feature being repaired.

This commit expands the Trezor hardware wallet's ability to clearly display details for more Tron TRC20 token transfers on the device screen. Previously, only one test token was recognized; now a built-in list of popular tokens (like USDT, USDD, BTT, etc.) is shown with their proper names and decimal places when a user signs a transfer. This is a user-experience and safety improvement, not a fix for a known exploit.

This commit refactors how the Trezor hardware wallet changes its PIN. Previously, the storage layer itself re-checked the old PIN while changing it. Now the device must already be unlocked before changing the PIN, and the change-PIN function only sets the new PIN. The change is described as removing a redundant 'double check.' It also adds more detailed error codes so the firmware can tell the user exactly what went wrong. There is no direct evidence in the commit that this fixes an active security bug, but it is a meaningful change to a security-critical function.

This commit only updates expected test result fingerprints (called UI fixtures) in a single JSON file. It does not change any firmware, application, or test logic. There is no security-relevant code change here.

This commit changes how the Trezor emulator (Unix/SDL build) redraws the screen and the suspend overlay. Previously, SDL drawing functions could be called from any internal task. The patch forces those SDL calls to run in the special 'kernel task' context, likely to avoid crashes, graphics corruption, or thread-safety problems when another task tries to update the display. It is a hardening/robustness fix for the emulator, not a live hardware wallet fix, and there is no direct evidence it closes a user-exploitable security vulnerability.

This commit changes how the Trezor hardware wallet's display is driven, mainly to save battery. It adds the ability to switch between 60 Hz and 30 Hz refresh rates depending on whether the screen is showing animations or a static image. It also reorganizes display timing numbers into panel-specific configuration files. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a power-optimization and code-cleanup change.

This commit fixes the length arguments passed to display-panel initialization commands in Trezor firmware. The wrong lengths could have caused some display panels to fail to initialize correctly, but there is no direct evidence this is exploitable for security harm. The commit also wraps the panel driver code in a KERNEL_MODE preprocessor guard so it only compiles in the appropriate build mode.

This commit changes a GitHub Actions workflow so that nightly automated test runs exercise all supported device languages, not just English. It is purely a testing/CI configuration change and does not modify any firmware code, cryptography, or user-facing behavior. There is no security relevance.