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

test(core): synthesize dev-key signed firmware images for the bootloader tests [no changelog]

Public commit record

What the developer wrote

Authored by tychovrahe

95/100 · Strong
test(core): synthesize dev-key signed firmware images for the bootloader tests [no changelog]

make_firmware() builds an image from a checked-in dev vendor header, a
firmware header with the requested version and model, and filler code,
rehashed and signed the way headertool does it. On secmon models a signed
TSEC image is embedded at the aligned offset. The runner fills the model
specifics in from the emulator's -p output.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit adds test-only code that creates fake Trezor firmware images signed with the project's public development keys. The images are used only in automated bootloader tests and never contain real firmware code. It does not change any production bootloader, firmware, or signing process, and it does not introduce a vulnerability in shipped devices.

Recommended action

No security action required. As a routine hygiene measure, confirm that development keys and synthesized images are not referenced or bundled in release builds, and that CI does not publish test fixtures as artifacts.

Security signals we found

01

Use of development signing keys in test fixtures

02

Synthetic firmware images accepted only by bootloader emulators built with BOOTLOADER_DEVEL=1

03

No runtime execution of synthesized code; emulator only verifies images

04

No change to production bootloader, firmware, or release signing infrastructure

Risk score

Why this scored 19/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/15
Confidence 9/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.