Trezor firmware

This commit changes how Trezor hardware wallet firmware handles a special factory-testing mode called 'prodtest'. In prodtest builds, it now uses an empty placeholder certificate for MCU (microcontroller) attestation instead of a real device certificate. This appears to be a development/testing convenience change rather than a fix for a live security vulnerability, because prodtest is not the normal user-facing firmware. However, it touches attestation code, which is security-sensitive, and the commit message gives no security context.

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 adds a new automated test that checks whether the serial numbers embedded in three different security certificates inside a Trezor device all match. It does not change any production firmware code, fix a bug, or alter device behavior. It only adds a test and a corresponding test fixture entry.

This commit only adds '.PHONY' declarations to many Makefiles. These declarations tell the build system that certain target names are not real files, preventing build mistakes if a file with the same name happens to exist. There is no change to the actual firmware, cryptography, or any code that runs on the device.

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 adds a test-only digital certificate for the T3W1 hardware emulator. It is explicitly labeled as a testing certificate for emulators, lives in a 'unix' emulator directory, and is not used in real Trezor devices. There is no direct evidence it introduces a security vulnerability, but shipping test credentials in source code always deserves a quick check that they cannot accidentally be enabled in production firmware.

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 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 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 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.