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.
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
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
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
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
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
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')
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
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…
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
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
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…
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…
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
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
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…
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
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
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…
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…
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
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 …
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
defensive validationboot or update path
AI analysis · Informational 15/100
This commit adds two digital signature files for BitBox02 firmware version 9.27.1. These signatures are a third-party reproducible-build verification (called an 'assertion') created by an independent contributor named yaziza. The commit does not change any firmware code, configuration, or executable behavior. It is purely a release-artifact addition.
The growing set of products, editions and boards requires more Make targets and separate flashing/debugging scripts for each combination. Selecting the device once lets developers use the same image commands across BitBox02, Nova and BitBox03 and reduces duplicated workflows.
Add make config to save product, board, edition, debug setting, probe software and SWD speed in a local, ignored config.mk. The primary build commands are firmware, factorysetup, bootloader-stage0 and bootloader-stage1. The stage targets build the selected development image; explicit production/development aggregates remain available.
Primary builds and matching flash/run commands follow the saved DEBUG setting, which can also be overridden per command. DEBUG=no selects RelWithDebInfo for BitBox02/Nova and release for BitBox03; DEBUG=yes selects debug builds. Without configuration, firmware keeps the existing BitBox02 multi RelWithDebInfo default. Replace profile-specific Make aliases with this shared setting.
Store builds in flat product directories, with CMake profiles in their names, so switching products keeps previous artifacts and backend caches available. Changing probe settings does not trigger recompilation. Update CI and artifact consumers to follow the new commands and paths, retaining debug build coverage and distinct artifact names.
Add matching flash-<image> and run-<image> commands using the saved probe settings, with hardware derived from the board. J-Link probes support SEGGER software or OpenOCD; the ST-Link dev-kit uses OpenOCD. Start debug-server separately, then run-<image> loads and verifies the built ELF, initializes its entry state and continues with GDB attached. BitBox02 stage1 uses finalized contents when flashing or debugging, and BitBox03 factorysetup runs from RAM without a reset after loading.
BitBox03 defaults to OpenOCD. Its testboard currently shares the dev-kit build, both editions build the same stub, and the production board remains disabled.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustboot or update path
AI analysis · Informational 17/100
This commit is a developer-facing build-system refactor. It replaces many hard-coded Make targets with a single saved configuration (product, board, edition, debug mode, probe tool) and adds Python helper scripts to build, flash, and debug firmware across BitBox02, Nova, and the upcoming BitBox03. There is no direct change to wallet cryptography, secure-boot checks, or firmware runtime behavior. The main security-relevant concern is that the new scripts handle flashing and GDB startup commands, so any bugs there could affect how firmware is loaded onto devices during development or factory setup.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
defensive validationboot or update path
AI analysis · Informational 15/100
This commit adds two digital signature files to the repository. They are third-party reproducible-build attestations (assertions) for the already-released BitBox02 firmware version 9.25.0. The commit does not change any firmware source code, build scripts, or device behavior. It is a routine release-verification step and does not introduce or fix any security vulnerability.
Allow host entry when the optional BIP39 passphrase is enabled, keeping device entry as the default. Requesting host entry requires device approval, then the user confirms the submitted value on the device before unlocking, including an empty passphrase. Rejection, cancellation or invalid input restarts device entry.
Run the new unlock flow inside the paired Noise channel to protect host input, retaining legacy unlock for older clients. Poll progress within the existing request/response model and use the existing reconnect reset to discard abandoned workflows.
Limit host passphrases to the device keyboard's character set and length so users can still access the same wallet through device entry. Withdraw the host-entry option before consent or passphrase confirmation starts, and relock after interrupted unlocks. Repeated unlock calls leave an already unlocked wallet unchanged.
Expose Python callbacks for host input and optional entry controls, with polling handled by the library. Support both a host-entry button and requesting host entry automatically. Extend send_message.py to demonstrate host entry, cancellation and withdrawal of the host-entry option.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialaccess controlcryptography-sensitive pathparser or protocol path
AI analysis · Low 41/100
This commit adds a new feature to the BitBox02 hardware wallet that lets users type their optional BIP39 passphrase on the connected computer (host) instead of only on the device. The passphrase is still sent inside the existing encrypted Noise channel, and the device still asks the user to approve and confirm the value before unlocking the wallet. The change is designed to make passphrase entry easier while keeping the device as the final gatekeeper. It is a feature addition, not a fix for a known vulnerability, and the commit message and code include several safeguards against misuse.
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 34/100
This commit adds a new 'session reset' command to the BitBox02 hardware wallet's USB protocol. It lets the host computer cleanly reset the device connection if a previous operation was interrupted, instead of leaving the device stuck mid-task. The change also fixes a minor timeout-handling issue for the existing INFO command so that merely checking the firmware version no longer keeps an abandoned operation alive. The commit is framed as a robustness improvement, not a security fix, and there is no disclosed vulnerability.
AI review queuedpy: make session reset an API setup helperby benma's agent · 50a9e76a · Sep 17, 2026 · 3 filesMessage 78 · AdequateInformational 15Details
Commit message · benma's agent
py: make session reset an API setup helper
Move reset_session out of BitBoxProtocol into the private BitBoxCommonAPI._reset_session helper alongside get_info. Keep the firmware version gate inside the helper so initialization skips the request on firmware older than v9.28.0.
Update the session tests and document host reconnect support under Firmware / Unreleased.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This is a routine Python code refactor. It moves an existing 'reset session' command from one internal class to another and adds a version check so older firmware simply skips it. There is no security bug being fixed here; it is purely organizational cleanup and test updates.
When a host disconnects after receiving an intermediate response, a workflow can remain in next_request().await while the device stays powered. The HWW lock has already been released, so the USB timeout does not cancel it. On reconnect, the Python client's attestation request is consumed as the old workflow's continuation and receives an error encrypted with the old Noise session instead of an attestation response.
Add a top-level REQ_RESET that cancels the pending task, discards queued HWW responses, resets Noise and restores the UI before acknowledging the new session. Drop task-owned UI components before resetting the screen stack, and refuse reset while a U2F workflow owns the shared UI. Allow REQ_INFO through the HWW busy gate without refreshing the operation timeout, so the host can discover the firmware version before deciding whether to reset.
Bump the firmware to v9.28.0 and have the Python client issue REQ_RESET before attestation, unlock and Noise setup only on v9.28.0 or newer. Add regression tests for abandoned continuations, pending responses, U2F arbitration, INFO timeout behavior and client compatibility. The powered-device reconnect flow still needs hardware validation.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustfuzzing or regression evidenceboot or update pathparser or protocol path
AI analysis · Moderate 62/100
This commit fixes a bug in the BitBox02 hardware wallet where unplugging the USB cable at the wrong moment could leave a half-finished operation running. If the device stayed powered and a new host reconnected, the new host's first message could be misinterpreted as a continuation of the old operation, producing a confusing encrypted error instead of a proper response. The fix adds a new 'reset session' command that the companion app sends at the start of every connection on firmware 9.28.0 and newer, which cancels any leftover task, clears queued responses, resets the encrypted Noise channel, and restores the user interface. The change also lets the host ask for the firmware version without extending an abandoned operation's timeout, so it can safely decide whether to reset.
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
AI review queuedMerge commit 'refs/pull/2073/head' of https://github.com/BitBoxSwiss/bitbox02-firmwareby Marko Bencun · 6b04e006 · Sep 16, 2026 · 21 filesMessage 58 · ThinInformational 17Details
Commit message · Marko Bencun
Merge commit 'refs/pull/2073/head' of https://github.com/BitBoxSwiss/bitbox02-firmware
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
This commit adds a new recovery-word entry screen for the upcoming BitBox03 hardware wallet. It is a large feature patch: it introduces a dedicated BIP39 wordlist keyboard, a new recovery-words review screen, and changes how the device handles going back versus cancelling during seed restoration. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a user-experience and hardware-support change. The code does improve clarity around cancel/back handling and adds confirmation prompts before aborting a restore, which is a sensible defensive design, but it is not presented by the vendor as a security fix.
Accept the title, required wordlist, and preset directly instead of the general EnterStringParams with its optional wordlist and unrelated flags. Construct the parameters inside the UI implementations and always use CanCancel::Yes, as recovery-word entry always allows aborting.
Preserve the BitBox02 enter_string fallback and existing back/cancel behavior.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
No production caller enables cancel_is_backbutton. Remove the flag from the UI HAL, BitBox02 Rust/C parameters, renderer state, and parameter-conversion tests.
Keep the existing default behavior: BitBox02 shows a cancel cross for empty input and a back arrow while editing, and BitBox03 uses the cancel icon.
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 47/100
This commit improves the BitBox02 hardware wallet's Ethereum token-approval screen. When a user signs an ERC20 token transfer, the device now also shows the token's smart-contract address if the token symbol is ambiguous (the same ticker, like 'UNI', is used by multiple contracts) or if the token is completely unknown. This helps prevent 'look-alike' token scams where a malicious contract uses a familiar symbol but is actually a worthless or harmful token. The change also blocks payment requests for unknown tokens. It is a defensive hardening patch, not an exploit fix for already-broken code.
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
update trustboot or update pathmerge-commit duplicate discount
AI analysis · Low 26/100
This commit relaxes a version check in the BitBox02 bootloader upgrade code. Previously, the firmware installer required that a stage0 bootloader descriptor's version exactly matched the currently expected image version. Now it accepts descriptors whose version differs, as long as the magic number and product ID still match. The change is framed as improving compatibility across bootloader descriptor layouts, not as fixing a security bug. The accompanying tests verify that both older and newer stage0 versions are accepted.