Trezor firmware

This commit is a routine cleanup of the GitHub Actions workflow that builds Trezor emulator releases. It removes unused matrix dimensions (like ASan variants), drops environment variables that were no longer needed, changes a default so the bootloader build step is skipped unless explicitly requested, and passes the device model into the build command. There is no change to the firmware code that runs on user devices, no fix for a vulnerability, and no security-relevant behavior change.

This commit removes the full build directory path from the firmware binary by switching from __FILE__ to __FILE_NAME__ in two error-handling locations. The change reduces information leakage but does not fix a memory corruption or logic bug. It is a hardening/information-disclosure reduction patch, not a fix for an actively exploitable vulnerability.

This commit updates a build script to look for compiled firmware files in a new directory path (`build-xtask/artifacts/...`) instead of the old path (`build/...`). It is a routine build-system path adjustment with no apparent security relevance.

This commit only updates expected test result fingerprints (hashes) in a UI test fixtures file for the T3W1 device model. No actual product code, firmware logic, or user-facing behavior was changed. It is a routine test-maintenance change with no security relevance.

This commit only adds comments explaining why the code does not overwrite SD card salt files with random data before deleting them. It changes no behavior, logic, or security controls. The documentation argues that overwriting is unnecessary because the encrypted data key stored inside the device is already wiped when the salt is changed, so an old recovered salt cannot decrypt anything.

This is a routine automated dependency update by Dependabot that bumps the urllib3 library from version 2.6.3 to 2.7.0 inside a small internal testing tool (automatic_battery_tester). The change is a single line in a requirements file. There is no indication in the commit that this fixes a security issue, and the tool is not part of the Trezor firmware that runs on user devices.

This is a routine build-environment cleanup. The developers removed an old copy of Nix packages (oldNixpkgs) used only for older SDL2 graphics libraries, because the project now uses SDL3. They added a compatibility package so old test emulators still work, and updated documentation and a download script to use a fuller Nix shell environment. There is no indication this changes any wallet, firmware, or cryptographic code, and no security relevance is claimed.

This commit only changes a test file so that a Decred signing test is skipped when the firmware is built in Bitcoin-only mode. It does not modify any production firmware code, wallet behavior, or cryptographic logic. There is no security issue here.

This commit only changes how long hexadecimal fingerprints and hashes are displayed to users. It inserts spaces every four characters so the strings are easier to read and compare visually. There is no change to security logic, cryptography, or how firmware is verified.

This commit only adds a new test case for Solana message signing with 64 cosigners and updates the expected screen snapshots used by automated testing. It does not change any firmware code that runs on the Trezor device, so it cannot introduce a security vulnerability or fix one.

This is a minor GitHub workflow change that stops an automatic pull-request assignment job from running when the pull request is opened by a bot account (whose username ends with '[bot]'). It has no security relevance to the Trezor firmware itself or to user funds.

This commit only updates documentation links inside the Trezor firmware repository. It fixes broken links, replaces GitHub URLs with relative links, and removes a symlinked documentation file. There are no code changes and no security impact.

This commit only changes the automated message used when the project pulls translation updates from Crowdin. It adds a '[no changelog]' tag so the translation sync does not appear in release notes. There is no security relevance.

This is a routine GitHub workflow change for managing translation updates. It removes a restriction that previously allowed the workflow to run only from the 'main' branch, and it makes the automatically created pull request a draft instead of a normal one. There is no security relevance in the code change itself.

This commit fixes a crash in the Trezor device's on-screen 'About device' menu when the device lacks a serial number. It wraps the serial-number lookup in a try/except block and displays 'N/A' instead of crashing. There is no indication this can be exploited by an attacker; it is a robustness fix for a user-interface screen.

This commit only adds new automated tests for the 'tap to wake' feature on the T3W1 hardware model. It does not change any firmware code that runs on the device, so it cannot introduce a security vulnerability or fix one. The tests verify that the setting is on by default, that the checkbox toggles it, and that the option is hidden on an uninitialized device.

This commit only renames a single JSON key from '_reserved' to 'reserved' across 14 vendor header configuration files. No security settings, permissions, or values are changed. It appears to be a routine cleanup to match a naming convention elsewhere in the build tooling.

This commit adds a new optional sanity-check layer to the Python code that parses Trezor firmware files. It verifies that re-encoding a parsed firmware image produces the exact same bytes, and that any 'reserved' fields are all zeroes. The change is defensive: it can help detect malformed or tampered firmware images during analysis, but the strict mode is off by default, so existing behavior is preserved unless a caller explicitly opts in.

This commit is a straightforward internal code cleanup in the Trezor firmware's user interface code. It moves header-related helper methods (like title alignment, cancel/menu buttons, and styling) from the Frame component to the Header component. All existing call sites are updated to build a Header first and then pass it into a Frame. There is no change to user-visible behavior or security logic.

This commit only changes the project's automated testing configuration. It adds a nightly CI job that runs Python unit tests against a Bitcoin-only firmware build in addition to the existing universal build. There is no change to the actual firmware code, no bug fix, and no security-relevant behavior change.

This commit only adjusts how long automated test jobs are allowed to run in GitHub Actions for one Trezor hardware model (T3W1). It extends a pytest session timeout from 40 minutes to 50 minutes and the overall CI job timeout from 50 minutes to 60 minutes, but only for the T3W1 model. There is no change to firmware code, cryptography, user data handling, or device behavior. It is purely a CI configuration tweak to prevent false timeout failures when running tests with two workers.

This is a routine code cleanup that fixes a Python import cycle (two files importing each other) by moving one import to happen only when a specific function runs. There is no security-relevant change visible in the diff.

This commit simply moves a small helper function that checks whether a string contains only normal printable characters from one file to another shared location. No behavior changes, no bug fixes, and no security implications are visible in the code change itself.

This commit only adds new automated tests for a Solana feature that signs and verifies off-chain messages. It does not change the actual wallet firmware code that users rely on, so it cannot by itself introduce a security vulnerability or fix one. The tests exercise parsing, signing, and verification logic and include checks for invalid inputs.

This commit adds a new Trezor feature: signing and verifying Solana off-chain messages. It is a feature implementation, not a fix for a known vulnerability. The code introduces new message types, parsing logic, user confirmation screens, and client helpers. There is no direct evidence in the commit of a security bug, but any new signing path increases the attack surface and must be reviewed carefully for parsing mistakes or user-interface spoofing.