Trezor firmware

This is a routine dependency version bump in a Python lock file. It updates the jaraco-context package from version 6.0.1 to 6.1.0, which is a minor release of a small helper library. There is no indication in the commit of any security issue being fixed, and no security-relevant code changes are present.

This commit fixes a small but specific bug in how the Trezor hardware wallet handles unrecognized messages during its secure Bluetooth/USB pairing setup (called the 'pairing phase'). Previously, receiving an unexpected message type could trigger a low-level KeyError instead of the intended, safer 'UnexpectedMessage' error. The fix makes the device respond with the proper error so the pairing process fails cleanly rather than potentially leaking internal state or crashing awkwardly.

This commit is a code cleanup that changes how Bluetooth Low Energy (BLE) support is enabled in the Trezor Python library. Previously, the BLE flag was passed through many function calls. Now it is read from an environment variable or command-line flag once and stored in a single place. There is no indication this fixes a security vulnerability; it is a refactoring to make the code easier to maintain.

This is a minor code cleanup that improves Python type annotations in the Trezor library's transport layer. It does not change how the software behaves or fix any security issue.

This is a small hardening fix in the Python Trezor library. Previously, if the device failed to respond to an 'EndSession' command, the software might keep thinking the secure session was still usable. Now the session is marked invalid regardless of whether the EndSession call succeeds or fails. This reduces the chance of accidentally reusing or leaking a stale session, but the change is minor and defensive rather than a clear fix for an active attack.

This is a large internal refactoring of the Python trezorlib client API. It reworks how sessions are created, managed, and closed, moves session classes out of the transport layer, adds a credential/keyring helper for the new THP pairing flow, and updates many CLI commands and tests to use the new API. There is no obvious malicious backdoor or simple vulnerability introduced, but the sheer size of the change means small bugs in session lifecycle, passphrase handling, or pairing credential storage could have security consequences. It is best treated as a high-risk refactor that needs careful review rather than an identified exploit.

This is a small code cleanup in Trezor's Python library. It changes how a new Bluetooth-style pairing flow is started so that it no longer asks the device for a 'credential' during setup. The commit message says the credential could not be returned to the caller anyway, so it was being discarded. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a refactor to avoid a useless step.

This is a tiny fix in the Trezor Python library that stops an incorrect error message. When a Trezor device is in bootloader mode, it legitimately does not return a session ID, but the library was wrongly logging a scary 'session management is now broken' error. The patch simply skips that warning when the device reports it is in bootloader mode. There is no sign this is a security vulnerability or that it changes any actual security behavior.

This commit fixes a logic bug in the Trezor Python library's pairing flow. Previously, the library would skip pairing whenever the device allowed it, even when the caller also asked for a security credential. Skipping pairing moves the protocol straight to a finished state where credential requests cannot succeed. The change makes the library only skip pairing when no credential is requested, preventing a likely functional failure or error condition during setup.

This commit refactors how Trezor's command-line tool stores and looks up pairing credentials. It changes the way secrets are labeled in the system keyring, adds new lookup methods, and adds a 'forget' command to remove remembered device keys. The changes appear to be a defensive improvement to credential management rather than a fix for an active vulnerability.

This is a small internal code cleanup in Trezor's test tooling. It replaces several direct checks for the string 'EMULATOR' with a single shared property, `is_emulator`. There is no change to the firmware's security behavior, no fix for a vulnerability, and no user-facing effect.

This commit refactors how the Trezor Python command-line tool (trezorctl) manages device sessions and unlocking. It aims to avoid creating duplicate sessions when unlocking the device and to handle passphrases more cleanly. The changes are framed by the developer as an improvement/fix to session handling, not as a response to a known security vulnerability. There is no public evidence that this fixes an exploitable bug.

This commit is a pure code reorganization: it moves the Trezor host-side protocol implementation files from one Python package directory (transport/thp) to another (thp) and adds a new protocol_v1.py module. The actual logic, constants, and behavior appear unchanged. There is no indication this fixes or introduces a security vulnerability.

This commit fixes a user-interface labeling bug in Trezor's Tron (TRC-20) token support. Previously, when a user was about to send a normal token transfer, the device screen incorrectly showed 'Approve' wording and labels, which could mislead the user into thinking they were approving a spender rather than sending funds. The fix adds a new 'transfer' confirmation screen and uses it for token transfers, while keeping the old 'approve' screen for future use. The actual transaction logic and signatures were not changed—only what the user sees on screen.

This commit changes a CI workflow that uploads test screenshots and screen recordings to an S3 bucket. It replaces the `aws s3 sync` command with `aws s3 cp --no-overwrite --recursive`. This is a workflow reliability tweak to prevent files from being overwritten during parallel uploads, not a security fix. There is no indication this change addresses a vulnerability or affects end-user devices.

This commit is a routine code cleanup: it creates a Tron-specific copy of some smart-contract constants that were previously borrowed from the Ethereum app, and updates the Tron signing code to use its own copy. There is no functional change to how transactions are validated or signed, and no security bug is fixed or introduced.

This commit only fixes whitespace in documentation comments and makes a minor type annotation change (using a more general AnyBytes type alias instead of bytes). There is no change to actual program logic, no bug fix, and no security relevance.

This commit adds support for a new Ethereum transaction type called EIP-7702 (smart accounts / account abstraction) to Trezor firmware. It is a feature addition, not a security fix. The change includes new user-facing confirmation text, test fixtures, and logic to allow signing these transactions only when safety checks are disabled and the destination address is a known allowed contract.

This commit only updates a test data file (fixtures.json) that stores expected screen hashes for automated UI tests. It renames some test cases and adds expected hashes for new Ethereum transaction test scenarios, including EIP-7702 and staking bad-input cases. There are no changes to the actual Trezor firmware code, wallet logic, or security behavior. It is a routine test-maintenance change.

This commit changes the Trezor firmware CI pipeline so that build artifacts (not just small fingerprint files) are collected and uploaded after reproducible builds. It is a workflow/infrastructure change with no visible effect on the firmware code, device behavior, or security of the product itself.

This commit refactors the way digital signatures are encoded and decoded in the Trezor firmware's Python code. It replaces a generic low-level DER sequence encoder/decoder with two dedicated functions for signatures. The change is described by the developer as a cleanup ('chore') with no changelog entry. There is no direct evidence in the commit that this fixes a security vulnerability, but centralizing signature handling can reduce the risk of future mistakes.

This commit simply removes an unused developer convenience command from the build Makefile. It does not change any firmware code, crypto logic, or device behavior, and has no security relevance.

This is a routine automated update by Dependabot that bumps the Python library cbor2 from version 5.6.5 to 5.8.0 in the project's lock file. The change only records new package download URLs and cryptographic hashes; no Trezor source code was modified. There is no indication in the commit that this fixes a security issue, and no verified security advisory was supplied. It is best treated as normal dependency maintenance.

This is a routine automated dependency update by Dependabot that bumps the Python library pyasn1 from version 0.6.1 to 0.6.2 in the project's lock file. There is no indication in the commit itself that this fixes a security issue, and no verified security references were provided. On its own, a patch-version bump of a pure-Python ASN.1 parsing library is normally treated as a maintenance change.

This is a routine automated dependency update by Dependabot. It bumps the Python build tool 'virtualenv' from version 20.34.0 to 20.36.1 in the project's lock file. The change only affects development tooling used to create isolated Python environments, not the Trezor firmware that runs on devices or handles cryptocurrency. There is no indication of a security fix or vulnerability in the commit itself.