Trezor firmware

This commit is a straightforward internal code refactor in the Trezor hardware wallet's Rust transport-handshake protocol (THP) library. It replaces a simple pairing-state field with a richer 'phase' enum that tracks whether the channel is still in the pairing/credential setup stage or has moved to encrypted application messaging. The change adds helper methods so the application can explicitly mark pairing as finished. There is no direct security fix here; it is a structural improvement that makes state tracking clearer and less error-prone for callers.

This commit refactors the cryptographic glue code that connects Trezor's embedded firmware to a Rust-based Noise protocol implementation used for secure device communication. The most notable security-relevant change is the addition of a constant-time comparison function for checking AES-GCM authentication tags, which helps prevent timing-based attacks that could leak information about the tag. The commit also splits AES-GCM into separate encrypt and decrypt types, adds a non-pinned SHA-256 wrapper, and introduces wrappers for Curve25519 and AES-GCM to satisfy the Noise protocol backend interface. There is no explicit vendor statement that this fixes a security vulnerability, and no independent researcher is credited.

This commit is a code cleanup in the Trezor firmware's Rust cryptography code. It replaces hand-written memory-clearing code with a standard library feature called ZeroizeOnDrop. The goal is the same: erase sensitive cryptographic data from memory when objects are destroyed. There is no evidence this commit fixes an active security bug; it is a defensive hardening and refactoring change.

This commit replaces the Python implementation of Trezor's THP (Trezor Host Protocol) with a Rust-based one. It is a large refactoring that moves channel state management, encryption, packet handling, and handshake logic from Python into a Rust module exposed as `trezorthp`. The change also adjusts how credentials are validated, how sessions are cached, and how the event loop handles reads, writes, and retransmissions. There is no explicit security bug in the diff, but the scope of the rewrite and the removal of several safety checks (for example around buffer allocation and unexpected-message handling) create a non-trivial risk of introducing memory-management, concurrency, or protocol-edge-case bugs. The vendor does not describe this as a security fix.

This commit fixes a spelling mistake in the legal license text at the top of six source files. The typo 'HMAC_SHALL' is corrected to 'SHALL'. It does not change any program logic, security behavior, or compiled code.

This commit fixes several minor issues in a cryptographic module used for secure device communication. The changes include preventing undefined behavior when copying from NULL pointers, zeroing out sensitive key material after use, and properly returning errors when encryption fails. These are defensive hardening fixes rather than a clear, exploitable vulnerability.

This commit is a simple rename of the cryptographic module from 'noise' to 'noise_kk1' across file names, function names, constants, and build scripts. No security behavior changes are visible in the diff. It is a code-maintenance refactor, not a security fix.

This commit adds a brand-new cryptographic module implementing the Noise_XXpsk3_25519_AESGCM_SHA256 protocol for secure encrypted communication. It is a feature addition with no changelog entry and no accompanying security advisory. The code itself is a clean implementation of a well-known cryptographic handshake, but because it is new code handling private keys, pre-shared keys, and AES-GCM encryption, it is security-relevant by nature. There is no direct evidence in the commit or supplied references that this fixes a known vulnerability or introduces a bug.

This commit only adds new automated tests for an existing cryptographic handshake protocol called noise_xxpsk3. It does not change the actual security code, fix a bug, or introduce a vulnerability. The tests verify that the protocol works correctly, that tampered messages are rejected, and that keys are wiped after use.

This commit fixes a build problem in Trezor's firmware. The code used a very common filename, version.h, which could accidentally pull in the wrong file from another software package during compilation. The fix creates a symlink with a more specific name, firmware_version.h, and uses that instead. There is no direct evidence this is a security vulnerability; it appears to be a build reliability fix.