Trezor firmware

This commit updates Trezor's internal test-only files that simulate a TROPIC01 secure chip. It replaces old self-signed test certificates with a new four-level test certificate chain and embeds keys directly into config files instead of referencing separate PEM files. The change is labeled as a testing chore, touches only test/development artifacts, and does not alter production firmware code. The most notable security-relevant detail is that a hardcoded X25519 private key is included in test data, but it is explicitly a test key already present in the public source tree and used only for the emulator/unix test build.

This commit changes a Trezor firmware function so that, outside of a special factory testing mode (PRODTEST), it refuses to write an MCU attestation certificate. Previously the function accepted and stored such a certificate. The change prevents firmware from installing or overwriting this certificate, likely to reduce attack surface, but the commit message gives no details about any specific security issue.

This commit changes a factory-production testing tool (prodtest) so that the commands for writing and reading the device's MCU attestation certificate also work in the software emulator, instead of returning 'not implemented'. In the emulator, the written certificate is only stored in memory and disappears after reboot. The change removes compile-time guards that previously disabled these commands for emulator builds. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a feature-enablement change for testing/development workflows.

This commit simply moves a helper function called compact_size from one internal file to another and updates the import statements in files that use it. There is no change to what the function does, no bug fix, and no security impact.

This commit only adds a new automated test that checks whether Trezor hardware devices can prove their identity using an MCU-based digital signature. It does not change any firmware code that runs on the device, nor does it fix or introduce any security vulnerability. It is a testing-only change.

This commit fixes how the Trezor Python library builds an authentication challenge. Previously, the code encoded the length of a header and the length of the challenge as a single byte, which only works for values up to 255. The fix uses a variable-length 'compact size' encoding instead, which can handle larger values. If a challenge or header were ever 256 bytes or longer, the old code would produce an incorrect byte string, which could cause authentication to fail or behave unexpectedly. There is no direct evidence in the commit that this was exploitable as a security vulnerability, but it is a correctness fix in a security-sensitive authentication path.

This is a minor code cleanup in the test suite. It replaces a manually constructed challenge message with a helper function that does the same thing. There is no change to the actual Trezor firmware or to how device authentication works in production.

This commit is a simple code cleanup: it moves a small block of code that builds an authentication challenge message into its own reusable function. There is no change to behavior, no bug fix, and no security-related change.

This commit is a code cleanup and test reorganization. It moves sanity-check assertions (which verify that hardcoded cryptocurrency addresses and function signatures are correct) out of the main firmware code and into dedicated unit tests. The actual checks still run during development testing, but they no longer get baked into debug firmware builds. There is no security vulnerability being fixed here.

This is a code cleanup (refactor) in Trezor's Ethereum transaction signing. It merges two internal steps into one so that transaction data is streamed, hashed, and shown to the user in a single pass instead of two. The commit message says there is no functional change, and the visible code preserves the same hashing and confirmation behavior. UI test snapshots changed, which is expected because the on-screen flow order changed, but no security bug is evident from the diff alone.

This commit updates Trezor's Bluetooth firmware build system so it can compile against two different Nordic SDK versions (an older 2.9 and a newer 3.3). It adds version checks, pins the correct compiler toolchain, and renames a few Bluetooth and SPI constants so the same source code works with both SDKs. There is no obvious security bug being fixed; it is primarily a compatibility and build-reliability change.

This commit adds metadata for a new Ethereum yield vault called 'Trezor Steakhouse ETH Prime Vault' so that Trezor devices can display a friendly name and token details when users interact with it. It is a product feature addition, not a security fix or vulnerability.

This is an internal code cleanup in Trezor's Ethereum transaction signing. It changes how staking and yield-farming transactions hand off their user-confirmation step so the confirmation happens inside the same routine instead of being returned as a separate progress indicator. The commit message says the goal is to avoid needing a progress indicator because all transaction data is already loaded and hashed. There is no direct evidence in the commit of a security bug being fixed, but the change touches the code that decides what users see before they approve high-value operations like staking and vault deposits/withdrawals. The large set of updated UI test hashes shows the on-screen flow changed, which is expected for a refactor of this kind.

This commit tightens validation in the hardware wallet's AES-GCM encryption code by rejecting initialization vectors (IVs) of length zero. Previously, a zero-length IV was silently accepted, which violates the NIST standard and can lead to weak or broken encryption. The change also makes the higher-level encrypt/decrypt functions properly report this error instead of ignoring it.

This commit only adds a new test to the Trezor firmware crypto test suite. It checks that multiplying certain special 'low-order' points on the Curve25519 curve by various secret scalars always produces an all-zero result. There is no change to the actual cryptographic code being tested, only a new regression test. By itself, this commit does not fix or introduce a security vulnerability.

This commit only updates the project's cryptographic test suite to match a newer version of the Wycheproof test-vector submodule. It changes test data file names and field names (for example, 'keyDer' to 'publicKeyDer') and adds a safety check for empty padding data in a test helper. None of these changes affect the actual Trezor firmware code that users rely on for security.

This commit only adds and improves test code. It extends an existing test suite to check more cryptographic algorithms (AES-GCM, AES-CCM, HMAC, PBKDF2) using well-known public test vectors from Project Wycheproof. It also fixes a few small helper functions in the test file so they correctly report failures. There is no change to the actual Trezor firmware or its cryptographic library, so this commit does not introduce or fix a security vulnerability in the product itself.

This commit fixes a length-check bug in Trezor's Stellar cryptocurrency support. The device was measuring string length in characters (Unicode code points) instead of bytes. Because some characters use multiple bytes, a string could pass the old check yet be too long for the Stellar protocol, potentially causing malformed transaction data or unexpected device behavior when signing.

This commit only adds new protocol buffer message definitions for an upcoming Ethereum feature (EIP-7702 authorization signing). It does not contain any actual signing logic, device firmware behavior, or user-interface code. It is a schema-only change and therefore does not introduce a security vulnerability by itself.

This is a code-style cleanup commit in the Trezor firmware's Rust code. It replaces plain `as` type casts with explicit conversion methods like `u32::from(...)`, `i16::from(...)`, and `f32::from(...)` to satisfy the Rust Clippy lint `cast_lossless`. These changes do not alter program behavior; they only make the code clearer and avoid compiler warnings. There is no security fix or functional change here.

This is a clean internal code cleanup in the Ethereum app of the Trezor firmware. It moves the Keccak hashing helper to a shared location and updates callers to use it. There is no user-facing behavior change and no security fix.

This is a small internal code cleanup in Trezor's Ethereum transaction signing. It replaces two separate return values with a single tuple, because they are always either both present or both absent. There is no user-visible behavior change and no indication of a security fix.

This commit fixes a minor user-interface inconsistency in how the Trezor device displays auto-lock delays longer than a day. Previously, the confirmation dialog showed "48 hours" while the settings menu showed "2 days" for the same delay. The fix merges two similar formatting functions into one shared implementation so all screens use the same wording. It is a cosmetic bug fix, not a security vulnerability.

This commit only adds two new import names (DateFormatter and RawFormatter) to an existing Python file in the Ethereum clear-signing module. It is a test-related change with no functional code modifications, no bug fixes, and no security-sensitive behavior changes.

This commit adds a new way for Ethereum transaction definitions to include fixed text labels (called 'constant values') that are shown to the user during signing. It does not change how transaction data is parsed or signed, but it expands what untrusted display-format definitions can put on the device screen. The change is a feature addition, not a fix for a known bug, and there is no vendor statement that it is security-relevant.