BB
← All projectsBitBox

BitBox02 firmware

Firmware and bootloader for BitBox02 signing devices.

BitcoinHardware walletsNormal
Repository coverage

938 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

314security candidates186second-pass queue827AI analyses
88commits · 30 days
150commits · 60 days
340commits · 180 days
723commits · 365 days
Backfill bands
Aug 5 → Feb 6335 seen28 candidatesComplete
Feb 6 → Jun 6265 seen19 candidatesComplete
Jun 6 → Jul 619 seen5 candidatesComplete
Jul 6 → Aug 526 seen3 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

59/100 average clarity
86Strong · 80–100
381Adequate · 60–79
381Thin · 40–59
90Opaque · 0–39
27security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Marko Bencun504157459656
benma's agent15566140267
Niklas Dusenlund17151144057
Cedric Wiese24919051
NickeZ Agent1669077
cedwies12512063
Sebastian Sutter655060
Tomas Vrba12410068
Yasser Aziza333070
Jad14210060
benma312069
Niklas211054
Analysis record

Published AI watches

Last scanned 35 minutes ago

Informational 12 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/remove-aes-hmac-c-exports'

This commit removes unused C-language export functions for AES encryption/HMAC from the BitBox02 firmware's Rust code. It is a cleanup change: the functions are deleted, the crate is no longer included in firmware builds, and simulators st…

Reduction of C FFI attack surface by removing no_mangle AES/HMAC exportsDependency cleanup: bitbox-aes no longer linked into firmware or simulatorsNo patch of an identified vulnerability in cryptographic logic
0b6365c6by Marko Bencun+2−5913 files
No security note in commit
Low 43 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/btc-root-xpub-m49'

This firmware update makes two changes to how the BitBox02 hardware wallet handles Bitcoin-related requests. First, it blocks apps from exporting the wallet's master public key (the 'root xpub') at the top-level path 'm/'. Second, it allow…

Root xpub export blocked at empty keypath (m/)Changelog describes root-xpub restriction as a security-relevant changeExternal service message signing expanded to m/49 unhardened purpose
5294645cby Marko Bencun+79−195 files
Vendor flagged security relevance
Informational 17 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

cipher: remove unused AES-HMAC C exports

This commit removes two unused C-language bridge functions that wrapped an AES-HMAC encryption/decryption module. The functions themselves were not called from C code; the firmware now calls the same encryption logic directly from Rust. Re…

Removal of C FFI wrappers that could panic on malformed inputsCommit message acknowledges potential panic conditions (invalid IV length, undersized output buffer)No functional change to the underlying AES-HMAC implementation
090a263fby benma's agent+2−5913 files
Vendor flagged security relevance
Low 34 AI analysisMessage 85 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

u2f: bound DER signature component reads

This commit fixes a small but real bug in how U2F signature components are converted to DER format. The old code could strip too many leading zeros and then read past the end of a 32-byte signature piece, potentially producing an invalid o…

Out-of-bounds read at component boundary during DER encodingPotential malformed DER output for all-zero signature componentDefensive hardening in U2F signature handling
dd17bed7by benma's agent+21−43 files
Vendor flagged security relevance
Low 30 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: allow message signing under m/49

This commit expands the BitBox02 hardware wallet's Bitcoin message-signing feature to also accept key paths starting with the unhardened purpose 'm/49'. Previously only hardened m/45' and m/48' were treated as valid 'external service' keyp…

Relaxation of keypath allowlist for message signingUnhardened purpose m/49 added to external-service signing namespaceUser confirmation prompt still required ('External service key')
1f377f72by benma's agent+63−194 files
No security note in commit
High 72 AI analysisMessage 73 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: reject master xpub exports

This commit closes a security gap in the BitBox02 hardware wallet's Bitcoin API. Previously, a host app could ask the device to export the 'master xpub' (the public key at the very top of the wallet, keypath m/). Combined with any leaked p…

Master xpub export preventedPrivate-key derivation risk described in commit messageUnhardened path key compromise scenario
c4524b15by benma's agent+16−02 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge branch 'nickez-agent/configure-stage1-embedding'

This commit is a build-system refactor for the BitBox02 hardware wallet firmware. It replaces a set of separate 'bootloader upgrade' firmware images with a configurable option to embed the same bootloader update data into the normal firmwa…

70a32f5bby Niklas Dusenlund+152−33111 files
No security note in commit
High 70 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/merge-firmware-v9.29.0'

This firmware update hardens how the BitBox02 handles SwapKit-style cryptocurrency swaps and Bitcoin multisig addresses. It adds a new 'refund memo' to payment requests so the device can verify that any refund address belongs to the same w…

CHANGELOG labels prior changes as 'Bitcoin security fixes (multisig keypath and previous-transaction hash length validation)'CHANGELOG labels v9.29.0 as 'Require wallet-owned refund addresses for SwapKit'New RefundMemo protobuf message with address and optional derivation info
9b16af63by Marko Bencun+867−12411 files
Vendor flagged security relevance
Moderate 60 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/merge-bootloader-v1.2.3'

This commit hardens the BitBox02 bootloader's stored version-rollback protection data. It adds a SHA-256 checksum over the firmware and signing-key version 'floors' and a one-time migration marker, so the device can detect tampering or cor…

Adds integrity checksum (SHA-256) for anti-rollback version floors in bootloader flash dataIntroduces one-time migration marker to prevent repeated downgrade/migration windowsProduction bootloader now aborts on invalid bootdata instead of silently reinitializing it
a4ddb764by Marko Bencun+2124−3123 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/high-fee-wording-v9.27.2'

This commit only updates test data and test expectations to reflect that a wording change for high Bitcoin transaction fees was released in firmware version 9.27.2 instead of 9.28.0. It does not change any device firmware code, security lo…

00f9eb22by Marko Bencun+65−1123 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: fix high-fee wording cutoff in vectors

This commit only updates test data and test expectations for the BitBox02 firmware. It changes which firmware versions are expected to show an old versus new high-fee warning message, because the real firmware already started showing the n…

dc5702d0by benma's agent+65−1123 files
No security note in commit
High 77 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/stage0-reject-zero-signatures'

This update hardens the BitBox02 hardware wallet's bootloader so it refuses to accept a firmware update signed with an all-zero signature. Previously, the cryptographic verification routine could treat a zero-filled signature as valid unde…

Rejects all-zero ECDSA signatures that may verify as validAdds volatile signature read to mitigate LTO-based read eliminationORs all signature bytes without early exit to ensure full-byte inspection
aec4595dby Marko Bencun+81−22 files
No security note in commit
Low 35 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/stage1-pairing-lifecycle'

This update fixes a Bluetooth pairing bug in the BitBox02 Nova hardware wallet. When the device switched from Bluetooth back to USB mode, it could keep an old pairing request active. The fix clears that stale pairing state so the device do…

Clearing of stale Bluetooth pairing state on mode switchPairing code/request flag left set across BLE->USB transition before fixBluetooth pairing lifecycle change in bootloader startup path
1047430dby Marko Bencun+7−65 files
Vendor flagged security relevance
Low 47 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/silent-payment-constant-time-ecdh'

This commit changes how the BitBox02 hardware wallet computes a secret value used in Bitcoin silent payments. Previously, the device used a function that could leak timing information about the secret key through how long the calculation t…

Constant-time cryptographic operation addedVariable-time secret-key multiplication removedSide-channel hardening for silent payments
c1590222by Marko Bencun+21−122 files
No security note in commit
Moderate 59 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: use constant-time ECDH for silent payments

This commit hardens the BitBox02 hardware wallet's silent-payments feature against a side-channel attack. Previously, the device multiplied a secret key with a public key using a routine whose execution time could leak information about th…

Constant-time cryptographic operation introduced to replace variable-time secret-key multiplicationVariable-time scalar multiplication retained only on public operandsSilent payments private input key material (a_sum) no longer used in variable-time path
7e741cfdby benma's agent+21−122 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge branch 'nickez-agent/pin-protobuf-generators'

This commit is a build-system and developer-environment change. It pins the protobuf compiler and related Python tools to specific versions via a project-managed Python virtual environment, instead of relying on whatever version a develope…

Pinning build tools to exact versions reduces non-determinism in generated codeMoves protobuf compiler from system/Docker-installed binary to a version-locked Python wheelNo changes to firmware, cryptography, authentication, or device protocol logic
d072b0f9by Niklas Dusenlund+107−6411 files
No security note in commit
Informational 15 AI analysisMessage 92 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

build: prefer local protoc for Rust bindings

This commit changes the build script that generates Rust code from protobuf definitions. It makes the build prefer a specific local copy of the protobuf compiler (protoc) installed in the repository's virtual environment, rather than relyi…

de8be632by NickeZ Agent+4−01 file
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

build: use IPv4 for container downloads

This change forces the build system to use IPv4 instead of IPv6 when downloading tools and software packages during Docker image creation. It is a build reliability fix for GitHub Actions CI runners that lack IPv6 connectivity, not a secur…

bc434dcfby NickeZ Agent+6−41 file
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

build: check regenerated protobuf bindings

This change improves a build/CI script that checks whether automatically generated protobuf binding files are up to date. It now also checks Python bindings and deletes old generated files before regenerating them, so stale files cannot hi…

No security-relevant code changeBuild/CI hardening onlyNo vulnerability fix or exploit mitigation present in diff
ff3f7474by NickeZ Agent+13−22 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge branch 'translate-passphrase-on-host'

This commit is a localization (translation) update for the BitBox02 hardware wallet. It replaces hard-coded English text strings in the passphrase unlock feature with calls to the device's internationalization system, so the same messages …

4dfa26b4by Marko Bencun+33−103 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidateMerge remote-tracking branch 'agent/benma-agent/remove-aes-hmac-c-exports'by Marko Bencun · 0b6365c6 · Nov 20, 2026 · 13 filesMessage 50 · ThinInformational 12Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/remove-aes-hmac-c-exports'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 12/100

This commit removes unused C-language export functions for AES encryption/HMAC from the BitBox02 firmware's Rust code. It is a cleanup change: the functions are deleted, the crate is no longer included in firmware builds, and simulators stop depending on it. There is no indication this fixes an active security bug; it reduces attack surface by narrowing what code is exposed to C callers.

Security candidatecipher: remove unused AES-HMAC C exportsby benma's agent · 090a263f · Nov 19, 2026 · 13 filesMessage 78 · AdequateInformational 17Details
Commit message · benma's agent

cipher: remove unused AES-HMAC C exports

The keystore calls the AES-HMAC implementation directly from Rust. No
C caller needs the wrappers, which can panic if given an invalid IV
length or an undersized output buffer.

Remove both C exports and their binding and link configuration. Drop
the redundant test import and direct AES dependencies in the device
tests and graphical simulators. The keystore continues to use the same
Rust encryption and decryption functions.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
cryptography-sensitive path
AI analysis · Informational 17/100

This commit removes two unused C-language bridge functions that wrapped an AES-HMAC encryption/decryption module. The functions themselves were not called from C code; the firmware now calls the same encryption logic directly from Rust. Removing them eliminates the risk that someone might later misuse these wrappers with a wrong input size, but the change does not fix any currently exploitable vulnerability.

Security candidateu2f: bound DER signature component readsby benma's agent · dd17bed7 · Nov 19, 2026 · 3 filesMessage 85 · StrongLow 34Details
Commit message · benma's agent

u2f: bound DER signature component reads

Trimming every leading zero from a P-256 component can move the DER
encoder past the component boundary before it checks the sign bit.

Keep the final octet of each component when trimming so that zero has
its required one-octet DER INTEGER representation.

This is defensive hardening. The production U2F signer generates
nonzero R and S. Valid signatures, including ones with leading zeros,
produce exactly the same DER bytes as before.

85/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validation
AI analysis · Low 34/100

This commit fixes a small but real bug in how U2F signature components are converted to DER format. The old code could strip too many leading zeros and then read past the end of a 32-byte signature piece, potentially producing an invalid or malformed DER-encoded signature. The fix ensures at least one byte of each component is always kept. The vendor describes this as defensive hardening, because the device's own signer is not expected to produce the all-zero inputs that trigger the bug.

Security candidatebtc: allow message signing under m/49by benma's agent · 1f377f72 · Nov 19, 2026 · 4 filesMessage 78 · AdequateLow 30Details
Commit message · benma's agent

btc: allow message signing under m/49

Casa (casa.io) needs Bitcoin message signatures to verify control of
keys in the unhardened m/49 branch. The firmware currently rejects
these keypaths before prompting.

Accept m/49 and its descendants up to the existing limit of ten path
components. Use the same external service key confirmation as for m/45'
and m/48'.

Bump the firmware version to v9.30.0 for the two Bitcoin keypath changes.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundarydefensive validationsigning or wallet path
AI analysis · Low 30/100

This commit expands the BitBox02 hardware wallet's Bitcoin message-signing feature to also accept key paths starting with the unhardened purpose 'm/49'. Previously only hardened m/45' and m/48' were treated as valid 'external service' keypaths. The change is presented as a feature for Casa (casa.io) to verify control of keys. It is not a vulnerability fix; it is a deliberate relaxation of an access check, accompanied by tests and a version bump.

Security candidatebtc: reject master xpub exportsby benma's agent · c4524b15 · Nov 19, 2026 · 2 filesMessage 73 · AdequateHigh 72Details
Commit message · benma's agent

btc: reject master xpub exports

The master xpub combined with a leaked private key on an entirely
unhardened path exposes the master private key. The single-xpub API
would release the master xpub after an unusual-keypath confirmation.

Reject the empty keypath before prompting. Hosts that need to identify
the wallet can use the dedicated root fingerprint request.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
secret or key materialdefensive validation
AI analysis · High 72/100

This commit closes a security gap in the BitBox02 hardware wallet's Bitcoin API. Previously, a host app could ask the device to export the 'master xpub' (the public key at the very top of the wallet, keypath m/). Combined with any leaked private key from an unhardened derivation path, that master xpub could let an attacker compute the wallet's master private key and steal all funds. The fix rejects empty keypath requests before showing any confirmation screen. The commit message itself describes the security relevance.

Security candidateMerge branch 'nickez-agent/configure-stage1-embedding'by Niklas Dusenlund · 70a32f5b · Nov 19, 2026 · 11 filesMessage 50 · ThinInformational 15Details
Commit message · Niklas Dusenlund

Merge branch 'nickez-agent/configure-stage1-embedding'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit is a build-system refactor for the BitBox02 hardware wallet firmware. It replaces a set of separate 'bootloader upgrade' firmware images with a configurable option to embed the same bootloader update data into the normal firmware image. There is no indication in the commit of a security vulnerability being fixed; it appears to be a change to how firmware variants are produced.

Security candidateMerge remote-tracking branch 'agent/benma-agent/merge-firmware-v9.29.0'by Marko Bencun · 9b16af63 · Nov 19, 2026 · 11 filesMessage 50 · ThinHigh 70Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/merge-firmware-v9.29.0'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · High 70/100

This firmware update hardens how the BitBox02 handles SwapKit-style cryptocurrency swaps and Bitcoin multisig addresses. It adds a new 'refund memo' to payment requests so the device can verify that any refund address belongs to the same wallet account being spent from, preventing a malicious or compromised swap provider from redirecting refunds to an attacker's address. It also tightens Bitcoin multisig address keypath checks so only normal receive/change branches (0 or 1) are allowed when displaying a receiving address, while still permitting broader paths for spending/recovery. The changelog explicitly calls these 'Bitcoin security fixes' and 'Require wallet-owned refund addresses for SwapKit'.

Security candidateMerge remote-tracking branch 'agent/benma-agent/merge-bootloader-v1.2.3'by Marko Bencun · a4ddb764 · Nov 19, 2026 · 23 filesMessage 50 · ThinModerate 60Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/merge-bootloader-v1.2.3'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
update trustcryptography-sensitive pathboot or update pathmerge-commit duplicate discount
AI analysis · Moderate 60/100

This commit hardens the BitBox02 bootloader's stored version-rollback protection data. It adds a SHA-256 checksum over the firmware and signing-key version 'floors' and a one-time migration marker, so the device can detect tampering or corruption of those floors. It also improves flash read/write error handling (including ECC memory errors) and makes the bootloader refuse to use invalid boot data on production devices. Development devices can reset corrupt boot data for testing. The change is defensive: it closes a path where an attacker or glitch could potentially downgrade firmware or signing-key versions by corrupting stored data.

Security candidateMerge remote-tracking branch 'agent/benma-agent/stage0-reject-zero-signatures'by Marko Bencun · aec4595d · Nov 18, 2026 · 2 filesMessage 50 · ThinHigh 77Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/stage0-reject-zero-signatures'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundaryboot or update pathmerge-commit duplicate discount
AI analysis · High 77/100

This update hardens the BitBox02 hardware wallet's bootloader so it refuses to accept a firmware update signed with an all-zero signature. Previously, the cryptographic verification routine could treat a zero-filled signature as valid under some conditions, which might let a malicious or malformed firmware image pass the signature check. The fix explicitly scans every byte of each signature to ensure it is not all zeros, and it re-reads the signature bytes fresh during each verification pass to guard against subtle compiler or hardware-level tampering.

Security candidateMerge remote-tracking branch 'agent/benma-agent/stage1-pairing-lifecycle'by Marko Bencun · 1047430d · Nov 18, 2026 · 5 filesMessage 50 · ThinLow 35Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/stage1-pairing-lifecycle'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Low 35/100

This update fixes a Bluetooth pairing bug in the BitBox02 Nova hardware wallet. When the device switched from Bluetooth back to USB mode, it could keep an old pairing request active. The fix clears that stale pairing state so the device does not act on an outdated or unintended pairing code.

Security candidateMerge remote-tracking branch 'agent/benma-agent/silent-payment-constant-time-ecdh'by Marko Bencun · c1590222 · Nov 18, 2026 · 2 filesMessage 50 · ThinLow 47Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/silent-payment-constant-time-ecdh'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
constant-time or timing behaviorcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Low 47/100

This commit changes how the BitBox02 hardware wallet computes a secret value used in Bitcoin silent payments. Previously, the device used a function that could leak timing information about the secret key through how long the calculation took. The new code uses a constant-time elliptic-curve Diffie-Hellman operation and passes the intermediate public point into the proof creation so the secret is no longer multiplied in a variable-time way. This is a defensive side-channel fix, not an active exploit.

Security candidatebtc: use constant-time ECDH for silent paymentsby benma's agent · 7e741cfd · Nov 18, 2026 · 2 filesMessage 68 · AdequateModerate 59Details
Commit message · benma's agent

btc: use constant-time ECDH for silent payments

Use libsecp256k1's constant-time ECDH to multiply the scan public key
by the sum of the input private keys. Reuse this DLEQ point to derive
the same BIP352 shared point by multiplying it by the input hash. The
host receives the DLEQ point with the proof and can compute the hash,
so both operands of the remaining variable-time tweak are public to it.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialconstant-time or timing behaviorcryptography-sensitive path
AI analysis · Moderate 59/100

This commit hardens the BitBox02 hardware wallet's silent-payments feature against a side-channel attack. Previously, the device multiplied a secret key with a public key using a routine whose execution time could leak information about the secret. The change uses libsecp256k1's constant-time ECDH for the secret multiplication, and only performs a variable-time multiplication on a value that is already public to the connected computer. This reduces the risk that a local attacker or malware could recover private key material by timing how long the device takes.

Security candidatebuild: use IPv4 for container downloadsby NickeZ Agent · bc434dcf · Nov 12, 2026 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · NickeZ Agent

build: use IPv4 for container downloads

GitHub Actions' hosted Ubuntu runners do not support IPv6 connectivity.
When the LLVM signing-key download resolves to IPv6, it fails with
"Network is unreachable" and prevents the development image from building.

Force IPv4 for APT and the Dockerfile's wget and curl downloads so they
use the network available on the CI runners.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing boundary
AI analysis · Informational 15/100

This change forces the build system to use IPv4 instead of IPv6 when downloading tools and software packages during Docker image creation. It is a build reliability fix for GitHub Actions CI runners that lack IPv6 connectivity, not a security fix.

Security candidateMerge branch 'translate-passphrase-on-host'by Marko Bencun · 4dfa26b4 · Nov 12, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · Marko Bencun

Merge branch 'translate-passphrase-on-host'

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access controlboot or update pathmerge-commit duplicate discount
AI analysis · Informational 15/100

This commit is a localization (translation) update for the BitBox02 hardware wallet. It replaces hard-coded English text strings in the passphrase unlock feature with calls to the device's internationalization system, so the same messages can be shown in German or other supported languages. There is no security vulnerability here; it is a routine code-quality and user-interface improvement.

Security candidateMerge remote-tracking branch 'agent/benma-agent/rust-audit-upgrades'by Marko Bencun · daa2ff28 · Nov 11, 2026 · 300 filesMessage 50 · ThinLow 25Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/rust-audit-upgrades'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 25/100

This is a large dependency upgrade commit for the BitBox02 firmware, primarily updating vendored Rust cryptography and utility crates (such as aead, anyhow, chacha20poly1305, sha2, etc.) and adding build flags to use smaller 32-bit and compact software-only backends. The commit itself is a routine maintenance/audit upgrade merge; it does not introduce an obvious vulnerability in the diff shown, but any large dependency bump carries a risk of subtle breaking changes or supply-chain issues. There is no vendor statement or external advisory supplied that identifies this commit as a security fix or as addressing a known vulnerability.

Security candidaterust: upgrade crypto dependencies togetherby benma's agent · 25bc564c · Nov 10, 2026 · 300 filesMessage 68 · AdequateLow 38Details
Commit message · benma's agent

rust: upgrade crypto dependencies together

RustSec advisories require newer crypto dependencies. Upgrade P-256 and all consumers of
the shared RustCrypto traits together so the migration does not introduce parallel
crypto versions.

Use the upstream bip32-ed25519 v0.2.2 tag and share DER 0.8 with bitbox-securechip.
Adapt the remaining digest, HMAC, AEAD and P-256 APIs while preserving key derivation,
signatures and Noise wire behavior. Retain key and keystream zeroization and inline
Noise storage.

sha2 0.11 replaces the force-soft-compact Cargo feature with quoted compiler cfg values.
Select the compact software backend in Cargo, CMake and CI to preserve the firmware size
optimization. CMake must pass the inner quotes through to rustc, so enable VERBATIM on
the Rust build commands. Split CARGOFLAGS into separate arguments and expand optional
argument lists so quoting does not combine multiple options or pass empty arguments.

Refresh the lockfile and vendored sources. Remove the direct Keccak dependency now that
sha3 uses compact loops by default.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialsigning boundarycryptography-sensitive pathseed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Low 38/100

This is a large maintenance update for the BitBox02 hardware wallet's Rust cryptography libraries. The developers upgraded many crypto-related dependencies (such as those handling SHA-2 hashing, AEAD encryption, BLAKE2, and Ed25519 key derivation) to newer versions required by RustSec security advisories. They also adjusted build settings to keep the firmware small and preserve existing security behavior, such as clearing sensitive key material from memory. The commit itself is a routine, security-motivated dependency refresh rather than a fix for an active, exploitable bug in the device.

Security candidaterust: prepare crypto callers for upgradesby benma's agent · df4284d6 · Nov 10, 2026 · 7 filesMessage 73 · AdequateInformational 15Details
Commit message · benma's agent

rust: prepare crypto callers for upgrades

The crypto dependency upgrade changes digest and hash APIs. Use caller forms supported
by both dependency generations so these behavior-preserving adaptations can be reviewed
separately.

Express the fixed Cardano hash sizes in the types and consume the single-use backup MAC.
Keep random and salt outputs in their existing zeroizing allocations. Add the expected
P-256 public key alongside the existing signature vector.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundaryseed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a routine code cleanup in the BitBox02 firmware's Rust code. It changes how cryptographic hashing functions are called so the project can upgrade a dependency later without breaking anything. There is no indication of a security bug being fixed or introduced.

Security candidaterust: replace Noise crypto adaptersby benma's agent · 89f51cf9 · Nov 10, 2026 · 16 filesMessage 68 · AdequateLow 32Details
Commit message · benma's agent

rust: replace Noise crypto adapters

The noise-rust-crypto dependency ties the Noise adapters to an older
RustCrypto dependency set, blocking the planned dependency upgrades.

Own the SHA-256, ChaCha20-Poly1305 and sensitive-buffer adapters in
bitbox-noise so their dependencies can be updated with the workspace.
Keep the existing sha2 and chacha20poly1305 versions, Noise wire behavior,
and inline zeroizing storage.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Low 32/100

This commit replaces an external cryptography adapter library with the project's own in-house version for the secure communication layer (Noise protocol) used in the BitBox02 hardware wallet. The stated reason is to unblock future dependency upgrades, not to fix a known bug or vulnerability. The new code closely mirrors the old implementation and adds test vectors to verify correct behavior, but any change to cryptographic code carries a risk of subtle mistakes that could weaken secure connections.

Security candidatei18n: add missing passphrase on host translationsby Sebastian · 3ba5f42d · Nov 9, 2026 · 3 filesMessage 68 · AdequateInformational 18Details
Commit message · Sebastian

i18n: add missing passphrase on host translations

Passphrase on host related translations were missing.

Existing translation for "Please try again" was bypassed in unlock.rs,
fixed as well.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
access controlboot or update path
AI analysis · Informational 18/100

This commit is a localization (translation) fix. It adds missing translated text strings for the 'passphrase on host' feature and makes the unlock code use those translated strings instead of hard-coded English text. There is no evidence of a security vulnerability being fixed; it is a user-interface completeness and internationalization improvement.

Security candidateMerge remote-tracking branch 'agent/benma-agent/blupgrade-stage0-v3-sighash'by Marko Bencun · 9e437162 · Nov 3, 2026 · 14 filesMessage 50 · ThinLow 43Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/blupgrade-stage0-v3-sighash'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Low 43/100

This commit updates the BitBox02 hardware wallet's bootloader upgrade files from version 1.2.2 to 1.2.3 and refreshes the stage0 bootloader binaries. The change is a routine firmware/b bootloader refresh, but the commit message and diff provide no explanation of why the new versions were built or what they fix. Because these binaries are security-critical (they control how the device boots and verifies firmware), any change to them is security-relevant by nature, but we cannot determine from the supplied materials whether it fixes a vulnerability, adds a feature, or is purely maintenance.

Security candidateblupgrade: update stage1 binaries to v1.2.3by benma's agent · 597e7dd8 · Nov 3, 2026 · 10 filesMessage 81 · StrongLow 43Details
Commit message · benma's agent

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.

81/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet pathboot or update path
AI analysis · Low 43/100

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.

Security candidateblupgrade: refresh stage0 v3 for new sighashby benma's agent · 57b4712c · Nov 2, 2026 · 5 filesMessage 91 · StrongLow 29Details
Commit message · benma's agent

blupgrade: refresh stage0 v3 for new sighash

The stage0 binaries embedded in blupgrade still use the legacy stage1
signature hash and cannot accept images signed with the 0x01-prefixed
scheme introduced in #2184.

Refresh the four production stage0 v3 images from bb1a866bba and update
their checksums. Development stage0 skips signature verification and
is unchanged.

Production use also requires stage1 binaries signed with the new scheme.
The bundled v1.2.2 production images still use legacy signatures, so
production blupgrade currently stops at "stage1 update" before flashing.

91/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validationboot or update path
AI analysis · Low 29/100

This commit updates four embedded bootloader files (called 'stage0') inside the BitBox02 firmware's bootloader upgrade tool. The old stage0 files could only verify bootloader updates signed with an older signature format. The new stage0 files understand the newer signature format introduced in a previous change. This is a maintenance/fix commit to keep the bootloader upgrade path working with current signing practices; it does not by itself introduce or fix a user-exploitable vulnerability. Development devices, which skip signature checks, are left unchanged.

Security candidateMerge remote-tracking branch 'agent/benma-agent/bootloader-sighash'by Marko Bencun · bb1a866b · Nov 2, 2026 · 11 filesMessage 50 · ThinLow 47Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/bootloader-sighash'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
update trustsigning or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Low 47/100

This commit updates the BitBox02 bootloader and signing tools to use a new, versioned signature hash format. A one-byte version prefix (0x01) is added to the data that gets signed for both firmware and stage1 bootloader updates. This is a defensive hardening change: by versioning the signed message format, the device can distinguish old signatures from new ones and avoid cross-version signature confusion. The patch also speeds up the check for an empty firmware slot by reading flash erase state directly instead of computing a hash. There is no direct evidence in the commit of an active vulnerability being fixed, but the change prevents a class of future downgrade/replay-style attacks where a signature for one firmware version could be misused for another.

Security candidateMerge remote-tracking branch 'agent/benma-agent/usb-poll-interval'by Marko Bencun · f76c38cd · Nov 2, 2026 · 13 filesMessage 50 · ThinInformational 17Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/usb-poll-interval'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update pathmerge-commit duplicate discount
AI analysis · Informational 17/100

This commit updates the BitBox02 firmware to poll its USB communication channel more frequently (every 1 millisecond instead of every 4 milliseconds) and bundles newer signed bootloader files for development builds. The stated goal is to speed up firmware upgrades over USB. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a performance/usability improvement.

Security candidateblupgrade: refresh stage0 v3 binariesby benma's agent · 32d5523c · Nov 2, 2026 · 9 filesMessage 68 · AdequateModerate 60Details
Commit message · benma's agent

blupgrade: refresh stage0 v3 binaries

The embedded stage0 v3 binaries predate the NVM cache fix in
5b902dae6. Stage0 uses the same flash-programming driver, so
blupgrade must install rebuilt images to include it.

Refresh all eight production and development stage0 v3 images
from 8a65822e97 and update their checksums. The refreshed stage0
disables both NVM caches while programming flash and restores
them once programming completes.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · Moderate 60/100

This commit replaces eight pre-built bootloader helper files (called 'stage0 v3') inside the BitBox02 firmware repository and updates their checksum list. The commit message says the old stage0 files were built before a flash-memory programming fix (commit 5b902dae6) and therefore lack that fix. The new stage0 files disable a flash-memory speed-up feature (NVM cache) while writing to flash and turn it back on afterward. Because the actual binary contents are not shown in the diff, we cannot independently verify the change; we can only rely on the commit message's explanation.