AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 31 Bitcoin

feat(core): allow unprovisioned tropic run in non-production fw

Public commit record

What the developer wrote

Authored by cepetr

62/100 · Adequate
feat(core): allow unprovisioned tropic run in non-production fw

[no changelog]
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
The short version

What changed, and why it matters

This commit adds a development-only code path for Trezor hardware wallets that use the Tropic secure chip. In non-production firmware builds, if the device lacks the normal Trezor private key, it falls back to a publicly visible factory private key and a factory pairing key slot. This lets developers test devices that have not yet been provisioned with unique secrets. The change is wrapped in `#if !PRODUCTION` guards, so it should not compile into retail firmware, but it does embed a hardcoded private key in the source tree.

Recommended action

Verify that `PRODUCTION` is always defined for official release builds and that CI blocks accidental shipping of non-production firmware. Treat the hardcoded factory key as a development/test credential, rotate it if it has ever been used in field devices, and ensure it is not present in released binaries. Review whether the delay value and certificate-store fallback have any side effects on boot time or secure-element state.

Security signals we found

01

Hardcoded cryptographic private key in source code

02

Factory-default key fallback for unprovisioned devices

03

Conditional compilation (`#if !PRODUCTION`) intended to exclude the fallback from production builds

04

Addition of `hal_delay(100)` to work around Tropic01 `LT_L1_CHIP_BUSY` responses

05

New certificate-store parsing helper to retrieve Tropic public key when normal provisioning data is absent

Risk score

Why this scored 31/100

Our methodology →
Potential impact 8/30
Exploitability 4/25
Stealth signal 3/15
Affected reach 5/15
Confidence 7/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.