Trezor firmware

This commit only changes the wording of a date in two changelog files, switching from 'December 10th 2025' to '10th December 2025' for consistency. It does not touch any program code, build scripts, or security-related documentation.

This commit simply adds two new firmware version entries to a release metadata file. It does not change any code, cryptographic checks, or device behavior. There is no security issue visible in the change itself.

This commit only updates a timestamp-style version number in a definitions file. It is a follow-up housekeeping change with no visible security implications.

This commit fixes a timing side-channel flaw in how Trezor hardware wallets convert a user's recovery phrase (BIP-39 mnemonic words) into secret seed bits. The old code used a fast but variable-time binary search over the word list, which could let a local attacker with precise timing measurements learn information about the recovery words. The patch replaces it with a constant-time linear comparison and also removes an extra integrity check in older (legacy) Trezor firmware to reduce how often the secret seed is processed.

This commit is a routine version bump from 2.10.0 to 2.10.1 in the Trezor firmware repository. It only changes version numbers in a header file and translation metadata, plus updates the signed translation package timestamp and fingerprint. There are no code behavior changes and no security relevance.

This commit only changes version numbers and release metadata. It bumps the firmware version from 2.9.7 to 2.10.0 and updates related changelog entries and translation package signatures. The commit message mentions that a separate security fix forced the version bump, but this commit itself does not contain any code fix.

This commit only updates the changelog and release notes for Trezor legacy firmware version 1.14.0. It deletes six small draft changelog files and adds their contents to the main CHANGELOG.md. No actual code, logic, or security behavior is changed in this commit.

This is a one-line bug fix in a Trezor hardware wallet factory/production testing tool. The function `prodtest_tropic_get_access_credential()` now jumps to cleanup code when it fails to retrieve a public key, instead of continuing to run as if nothing went wrong. Without the fix, the tool could keep processing and potentially leak or mishandle sensitive key material after an error. The affected code is in a production-test (manufacturing) program, not the main wallet firmware users interact with.

This commit only adds extra diagnostic log messages to two internal helper functions used during factory production testing of the Tropic secure chip. It does not change how keys or certificates are handled, and the new logging is compiled out of normal user firmware. There is no direct security vulnerability here; it is a minor debugging improvement.

This change only adds diagnostic log messages to a production-test helper function that writes pairing keys to a Tropic secure chip during factory testing. It does not alter security logic, access controls, or cryptographic operations; it merely makes failures easier to see during manufacturing tests.

This commit only adds an error log message when a cryptographic signing operation fails during a production-test command. It does not change any security logic, access controls, or behavior; it merely reports the specific failure reason instead of silently returning false.

This commit only changes error messages in a Trezor factory production-test tool. Instead of printing numeric error codes, it prints human-readable text descriptions. There is no change to security logic, no bug fix, and no vulnerability.

This commit only adds extra log/trace messages to a production-test command that checks whether a Tropic secure chip is locked. It does not change any logic, return values, access controls, or behavior of the device. There is no security issue visible in the diff.

This commit only adds diagnostic log messages to a hardware testing tool. It changes a function so it can optionally print 'Tropic driver is not initialized' or 'Tropic is busy' during production testing. There is no change to normal wallet firmware behavior and no security fix or vulnerability introduced.

This commit only adds extra diagnostic logging and changes a function signature so the logging can be routed to the production-test command-line interface. It does not change how cryptographic sessions are established or which keys are used. There is no indication this fixes or introduces a security vulnerability.

This commit only adds a one-line changelog note saying that logging of Tropic commands was improved. There is no code change, no bug fix, and no security-relevant content in the diff.

This is a small logging improvement in a Trezor factory production-test command. It splits one combined error check into two separate checks so the user sees a clearer message: either the key-read operation failed, or the key's curve type is not the expected P-256. There is no functional behavior change and no obvious security vulnerability.

This commit only improves the error messages shown during a production-line test command for the Tropic secure element. It replaces vague messages like 'Unable to write certificate' with more specific ones that include the underlying error code. There is no change to security logic, access control, or data handling.

This commit changes how a production-test tool reports problems when checking whether a Tropic secure chip is paired. Previously, the check function itself printed error messages; now it only records diagnostic traces, and the calling commands decide whether to report an error. It also fixes two callers that were passing a dummy/NULL context so they now pass the real command-line interface, meaning their 'pairing required' error messages will actually be shown. This is a code-quality and diagnostics change in a factory/testing tool, not a fix for an exploitable security flaw in end-user firmware.

This is a tiny build-tool fix in a code-generation template. It swaps single quotes for double quotes inside a Python f-string so the template works with older Python versions that don't allow single quotes inside f-string braces. There is no runtime security effect on the Trezor firmware itself.

This commit simply renames a constant from TROPIC_MAC_AND_DESTROY_SLOTS_COUNT to TROPIC_MAC_AND_DESTROY_SLOT_COUNT (singular) across three files. The numeric value stays the same (64), and no program behavior changes. It is a typo-fixing refactor with no security relevance.

This commit is a simple code cleanup: it renames a few internal variables in a production-test file by adding a 'g_' prefix to indicate they are global variables. No behavior of the code changes, and there is no security fix or vulnerability introduced.

This commit adds a new factory/production-test command called tropic-stress-test. It is meant for manufacturing diagnostics and repeatedly exercises the Tropic secure chip's session, MAC-and-destroy, and signing functions to make sure the chip does not enter an alarm state. There is no indication this change fixes a security bug or introduces a vulnerability; it is a testing feature.

This commit is a minor code cleanup in Trezor's production-test tool. It adds the 'const' keyword to two large configuration tables so the compiler knows they should not be modified at runtime. There is no functional change, no bug fix, and no security vulnerability indicated in the diff or commit message.

This commit is a routine code cleanup. It introduces a small helper file that provides a standard, safe way to convert between float numbers and their raw 32-bit representations. It then replaces a few existing hand-written conversions in the battery telemetry code with these helpers. There is no functional change and no security issue.