KeepKey Firmware v7.14.2

Verification

Source commit: 4ae82732af687fb42982ebdc09eeeb40d181aeff (tag v7.14.2, on master)

To verify this release

git clone https://github.com/keepkey/keepkey-firmware
cd keepkey-firmware
git checkout v7.14.2
git submodule update --init --recursive
./scripts/build/docker/device/release.sh
tail -c +257 bin/firmware.keepkey.bin | shasum -a 256

Expected hash: 45fe90c1dd72df59815475b37404635c5b890b298d74324632383965f533e9fa

See https://keepkey.com/blog/verifying_keepkey_firmware for full verification workflow.

Note: The build embeds git describe output in the firmware binary, so verification must check out the tag (which points to 4ae8273).

The attached binary is signed by firmware key slots 1, 2, 3 (3-of-5).

What's new

7.14.2 is a security release: what the device asks you to approve now matches exactly what it signs. No new features.

• Signed messages, memos, calldata, amounts, fees, authorities and network assets are either shown accurately or refused.
• EVM token and legacy-contract lookups keep the full 32-bit chain ID, so a high chain ID can no longer borrow chain-1 token names.
• EIP-1559 fee display and priority fee shown correctly; multi-byte chain IDs handled.
• THORChain's native-asset sentinel resolves to the signing chain's own asset.
• Security-sensitive blind-signing paths require Advanced Mode.
• Cancel, clear-session, recovery and wipe stop active work and clear retained secrets.
• Oversized, empty, omitted or invalid signed values fail before approval.