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

build: support locked development bootloaders

Public commit record

What the developer wrote

Authored by NickeZ Agent

85/100 · Strong
build: support locked development bootloaders

Hardware locking was tied to production mode, so development bootloaders
could not enable debug and boot protection while accepting unsigned
images.

Add saved LOCKED and DEVELOPMENT options for BitBox02 and Nova. LOCKED
controls hardware protection; DEVELOPMENT controls signature enforcement
and development markers. Keep unlocked development as the default,
support locked development, and require LOCKED=yes when DEVELOPMENT=no.
BitBox03 continues to accept only the default modes.

Select stage0/stage1 build and probe images from configuration, replacing
the top-level production/development stage aggregates. Preserve existing
artifact names and add development-locked variants. Refresh CMake target
definitions on each build and extend CI to build locked development
bootloaders for both products and stages.

Use BOOTLOADER_DEVELOPMENT in both stages and expose is_development() in
the Python client, retaining is_devdevice() as a deprecated alias. Keep
on-device flags and bundled bootloader images unchanged.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
The short version

What changed, and why it matters

This commit rewrites how BitBox02/Nova bootloaders are built so that 'hardware locking' and 'development mode' become two independent settings. Previously, locking was only available in production builds. Now developers can build a bootloader that has hardware debug protection enabled while still allowing unsigned (development) firmware. The change also renames internal flags from 'devdevice/production' to 'development/locked', updates build scripts, CI, and the Python flashing tool, and adds tests. It is a build-system and naming refactor rather than a runtime vulnerability fix.

Recommended action

Treat as a build-hardening and maintainability improvement. Review that the new CMake target generation correctly preserves existing production artifact hashes and that CI artifacts for locked-development bootloaders are clearly labeled and not shipped to end users. Verify the validation rule DEVELOPMENT=no requires LOCKED=yes cannot be bypassed via manual config.mk edits or CMake invocation. No urgent security patch is indicated by the diff alone.

Security signals we found

01

Build system now supports locked development bootloaders (hardware protection + unsigned firmware acceptance)

02

BOOTLOADER_LOCKED macro now gates debug-access locking and boot protection independently of production/development

03

Validation enforces DEVELOPMENT=no requires LOCKED=yes, preventing an insecure unlocked-production-like configuration

04

CI matrix expanded to build and artifact locked development bootloaders for both stages and both products

05

Python flashing tool terminology updated from 'devdevice' to 'development'; behavior unchanged

Risk score

Why this scored 34/100

Our methodology →
Potential impact 8/30
Exploitability 5/25
Stealth signal 4/15
Affected reach 6/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.