Keystone 3 firmware

This appears to be a routine CI (continuous integration) configuration update with no visible security relevance. Only one file was changed with a single-line addition and deletion. No diff content is available to inspect, and no security references were provided.

This firmware update for the Keystone 3 hardware wallet is billed as a security improvement. The most important change is a complete rewrite of the bootloader/firmware update path: it now uses SHA-256 and a signed/length-prefixed 'bootupdate' envelope instead of the older MD5-based verification, and removes an old USB mass-storage auto-reboot behavior that could let a plugged-in host trigger a reboot just by copying a file. The patch also hardens the USB stack against malformed endpoint numbers and oversized control transfers, enables on-chip flash encryption for the external QSPI flash, and improves I2C and random-number error handling. However, the diff is very large and mixes many unrelated features (new wallet icons, X Layer chain support, UI tweaks), so it is hard to be certain every corner case is fixed.

This commit removes two lines from the bootloader update code. Previously, after a successful bootloader update, the firmware erased and overwrote a sector near the end of the application flash area, then cleared a memory buffer. Now it only clears the buffer in RAM and skips the flash erase/write. This could leave stale update data or metadata in flash, potentially allowing a previously-failed or old update marker to persist and affect future boot behavior. The change is small and its security implications depend heavily on why the erase was originally performed.

This commit only adds text to two changelog files describing a new firmware release. It does not change any executable code, configuration, or security logic. There is nothing to exploit or patch in the commit itself.

This firmware update fixes a memory leak and cleans up boot-update logic in a hardware crypto wallet. The most concrete security-relevant change is adding a missing SRAM_FREE(buffer) call in BinarySearchBootHead, which prevents a small memory allocation from never being released. Other changes replace hardcoded 4096-byte values with a SECTOR_SIZE constant and remove a production-only conditional around NeedUpdateBoot. The commit message mentions 'fix memory allocation' but does not frame the change as a security fix.

This commit is described as a routine CI (continuous integration) update with only one line changed in a release-related file. No actual code changes are shown, and no security relevance is stated or visible.

This commit is a large firmware update for the Keystone 3 hardware wallet, primarily adding a bootloader update mechanism and hardening the USB stack. It introduces a way to overwrite the device's bootloader from a specially formatted region of flash memory, enables hardware-level flash encryption for production builds, and adds many bounds checks and validation routines to the USB device driver to prevent malformed host requests from crashing or confusing the device. The commit also removes the MD5 checksum code entirely and improves I2C and secure-element error handling.

This commit fixes a user-interface bug related to displaying the new USD₮0 (Tether) token symbol. It updates a generated font file so the ₮ glyph renders correctly, and corrects a function signature in the wallet connection screen so coin icons are passed as image descriptors instead of strings. There is no direct evidence of a security vulnerability being patched.

This commit adds support for a new blockchain network called X Layer and its associated token contracts to the wallet's user interface. It is a routine feature addition with no visible security-relevant changes.

This commit is a routine rebranding update: it changes the displayed name and icon of a wallet partner from 'Zashi' to 'Zodl' across the user interface. It also includes a tiny, unrelated code-style fix in a boot-parameter function so the simulator build path is properly wrapped in #ifdef/#else/#endif. There is no security-relevant change.

This commit only adds a blank line to a changelog file. It contains no code changes, no security fixes, and no functional modifications. There is nothing here that could affect device security or user funds.

This commit only edits two changelog files. It changes the release date of version 2.3.10 and adds a note about a bug fix for signing shielded Zcash (ZEC) transactions. No actual source code is changed in this commit, so it cannot by itself introduce, fix, or exploit a security vulnerability.

This is a one-line build-configuration fix for the Keystone hardware wallet's Zcash signing code. Previously, transparent Zcash transaction signing was only enabled when the 'multi_coins' feature was active. The change also enables it when the 'cypherpunk' feature is active. Without this fix, Zcash transparent signing simply fails to compile or run in cypherpunk-only builds. There is no direct evidence in the commit of a security vulnerability; it appears to be a missing-feature bug.

This is a one-line build-configuration fix for the Keystone hardware wallet's Zcash transparent transaction signing. Previously, the code that signs the transparent (non-shielded) part of a Zcash PCZT transaction was only compiled when the 'multi_coins' feature was enabled. The change also enables that signing code when the 'cypherpunk' feature is enabled. Without this fix, a device built with only the 'cypherpunk' feature could produce an incomplete or invalid Zcash transaction signature, likely causing the transaction to be rejected by the network rather than stealing funds.

This commit only adds a new changelog entry for firmware version 2.3.10 and bumps the build number in a version header. It does not change any executable code, cryptographic logic, or security behavior. There is no security issue visible in this commit.

This commit adds support for a new wallet partner called Gero Wallet in the Keystone 3 firmware. It is a routine feature addition: a new icon, a new entry in wallet lists, a tutorial link, and recognition of the wallet's origin name when handling key-derivation requests. There is no indication of a security fix or vulnerability.

This commit only changes a single version number in a header file, bumping the build number from 6 to 8. There is no functional code change, no bug fix, and no security-related modification visible in the diff.

This commit only adds a new changelog entry for firmware version 2.3.8 and bumps the build number in a version header file. There are no code changes, no bug fixes, and no security-related content.

This commit removes the Nabox wallet from an internal list of Ethereum-compatible (EVM) wallets in the Keystone 3 firmware's user interface. The title calls it a 'UI bug' fix. The change is one line: Nabox is no longer treated as an EVM wallet, which likely changes which blockchain options or connection flows are shown to users when they select Nabox. There is no direct evidence in the commit of a security vulnerability, exploit, or data leak.

This commit fixes a user-interface bug in the Keystone 3 firmware. It adds a missing entry for the 'Bull' wallet in the wallet tutorial list and corrects a typo in the icon array from 'walletXBull' to 'walletBull'. There is no security-relevant change visible in the diff.

This commit adds support for a new software wallet called 'BULL' to the Keystone 3 hardware wallet firmware. It is a feature addition: new icon, new menu entries, new localized strings, and wiring the wallet into existing Bitcoin QR-code export flows. There is no indication of a security bug or vulnerability in the changes.

This commit changes which cryptocurrency filters are shown for the Nabox wallet in the wallet connection screen. It expands the filter categories from just 'Other' to include Bitcoin, Ethereum, Solana, and Other. This is a UI/UX fix with no apparent security relevance.

This is a one-line build fix in a hardware wallet firmware file. It adds two extra arguments (NULL and 0) to a function call so it matches the current definition of get_keystone_connect_wallet_ur. There is no visible security change in behavior.

This commit fixes Japanese-language display issues in the Keystone 3 hardware wallet firmware. It adds two missing Japanese characters (住 and 未) to a font file and updates several Japanese translation strings to be shorter or more natural. There is no security-relevant change.

This commit only adds new automated unit tests for an existing function called generate_crypto_multi_accounts. It does not change any production code, so it cannot introduce a security vulnerability or fix one. The tests check that the function accepts certain cryptocurrency key paths, rejects an unsupported path, and handles empty input.