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

blupgrade: update stage1 binaries to v1.2.3

Public commit record

What the developer wrote

Authored by benma's agent

81/100 · Strong
blupgrade: update stage1 binaries to v1.2.3

Production blupgrade still embeds legacy-signed v1.2.2 stage1
images. After #2184, its signature check rejects those images
before the installer can replace stage0.

Embed the signed v1.2.3 images for all four production variants,
using the 0x01-prefixed signature scheme and monotonic version 2.
Update the CMake paths and checksums so blupgrade carries stage1
payloads accepted by the refreshed stage0.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
The short version

What changed, and why it matters

This commit swaps in newly signed bootloader stage1 files (v1.2.3) for the BitBox02 hardware wallet's bootloader upgrade tool. The old v1.2.2 production stage1 images would be rejected by a recently updated stage0 (#2184), so the firmware now ships the newer signed images so the bootloader update process can still work. The actual binary contents are not shown in the diff, so we can only verify the file names and checksums changed, not what code is inside the new binaries.

Recommended action

Treat this as a supply-chain/bootloader integrity checkpoint. Independently verify the v1.2.3 stage1 binaries against published signed release artifacts and reproducible build outputs, confirm the 0x01 signature scheme and version 2 metadata, and review #2184 to understand why the old images were rejected. Do not rely solely on filename or checksum changes.

Security signals we found

01

Bootloader image update

02

Signature scheme change (0x01-prefixed)

03

Monotonic version bump to 2

04

Opaque binary blob replacement

05

Referenced prior security-related change #2184

Risk score

Why this scored 43/100

Our methodology →
Potential impact 12/30
Exploitability 8/25
Stealth signal 6/15
Affected reach 10/15
Confidence 5/10
Evidence quality 2/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.