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.
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
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.
Security candidateoled: hold display in reset during startupby Niklas Dusenlund · cdb27835 · Sep 8, 2026 · 1 fileMessage 68 · AdequateLow 35Details
Commit message · Niklas Dusenlund
oled: hold display in reset during startup
Production stage0 verifies stage1 before initializing the OLED. Leaving the reset pin high can allow previous display content to remain visible at reduced brightness while the boost converter is disabled.
Set the reset output latch low before enabling the pin as an output. Keep the OLED in reset until oled_init() releases it and uploads a cleared framebuffer.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
access control
AI analysis · Low 35/100
This commit fixes a display behavior issue during startup of the BitBox02 hardware wallet. Previously, when the device turned on, the screen's reset pin was left in a state that could allow leftover images or text from an earlier session to briefly appear at low brightness before the device finished booting. The change ensures the screen is kept fully blank (held in reset) until the firmware is ready to draw a clean screen. This is a defensive fix to prevent a user from seeing stale or misleading information during boot.
This commit trims the BitBox02 factory-setup firmware image by switching stored root attestation public keys from 65-byte uncompressed to 33-byte compressed secp256k1 keys, and by using a smaller static secp256k1 verification context instead of a full signing context. It also adds a self-test and a helper that computes the key identifier from the uncompressed form so existing host tooling keeps working. The changes are framed as a size-reduction/cleanup patch; there is no direct evidence in the commit of a security vulnerability being fixed.
This commit adds extra safety checks in the BitBox02 Python library for ECDSA signatures used in Bitcoin and Ethereum signing. It now validates that signatures have the correct length, use valid numbers, and use the safer low-S form. It also validates the recovery ID for recoverable signatures. These are defensive hardening changes rather than a fix for a known active exploit, but they close a gap where a malicious or buggy device could return malformed or malleable signatures that the host software would previously accept.
Store the 110 root attestation public keys as const compressed SEC1 points instead of writable uncompressed points. Keep every key and its index unchanged, and document conversion using Python's ecdsa module.
Derive root identifiers from the uncompressed encoding so the host's identifiers and the single-signature verification added in #2081 are preserved.
The factory-setup image shrinks from 155,088 to 152,472 bytes, saving 2,616 bytes. RAM usage drops from 203,304 to 196,152 bytes, saving 7,152 bytes by keeping the table out of writable memory.
Together with the earlier changes in this PR, the image shrinks from 195,296 to 152,472 bytes (-42,824, 21.9%), and RAM usage drops from 203,304 to 196,152 bytes (-7,152, 3.5%). These figures exclude the peripheral and font changes split into #2092.
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
This commit is a hardening and size-optimization change for the BitBox02 factory-setup firmware. It stores the 110 built-in root attestation public keys in compressed (33-byte) form instead of uncompressed (65-byte) form, and marks the table as read-only (`const`). This shrinks the firmware image by about 2.6 KB and reduces RAM use by about 7 KB. A new helper is added so the device can still compute the same public-key identifiers used by host software, and the existing signature verification behavior is preserved. There is no direct vulnerability being fixed; the main security benefit is making the key table tamper-resistant in RAM because it now lives in read-only memory.
Use RustCrypto Hmac<Sha256> for the shared HMAC-SHA256 helper so factory setup reuses the SHA-256 backend already linked for plain hashing.
This reduces the factory-setup image from 159,568 to 155,088 bytes, saving 4,480 bytes. RAM usage remains 203,304 bytes.
Normal firmware still needs bitcoin_hashes for other callers. Multi grows from 686,080 to 686,356 bytes (+276), and Bitcoin-only grows from 525,392 to 525,656 bytes (+264).
Add known-answer coverage for empty keys and keys longer than the SHA-256 block size.
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 18/100
This commit swaps one internal cryptography library for another when computing HMAC-SHA256 in the factory-setup code. The goal is to reduce firmware size by reusing an existing SHA-256 implementation, not to fix a security bug. New test vectors were added to confirm the new implementation still produces the correct answers.
ECDSA verification can use libsecp256k1’s built-in static context.
A dynamically created context links signing support and its precomputation table, even when Rust requests a verification-only context.
The previous context initialization reached secp256k1_context_preallocated_create(), which runs secp256k1_selftest() automatically. The static context skips initialization, so run the self-test explicitly once during factory setup startup, as recommended by libsecp256k1.
This reduces the factory-setup image by 35,728 bytes.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
This commit changes how the BitBox02 factory-setup program checks digital signatures. It switches from a dynamically created crypto context to a built-in, read-only verification context, which makes the factory-setup firmware about 35 KB smaller. The commit also adds an explicit self-test because the new static context skips the automatic self-test that the old path performed. The change is a size optimization, not a fix for an active security flaw, but it touches cryptographic verification code used during device manufacturing.
Select the attestation root key by its identifier before verifying the certificate signature. This decreases the time to set the certificate to less than 0.1 seconds. Previously it took up to roughly 2.4 seconds for a root key near the bottom of the list.
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 boundaryupdate trust
AI analysis · Informational 18/100
This commit is a performance optimization in the BitBox02 factory setup process. It changes how the device picks which trusted root public key to use when verifying an attestation certificate. Previously, the device tried verifying the signature against every known root key until one worked, which could take up to about 2.4 seconds. Now it first looks up the correct root key using a short identifier (a hash of the public key) and then verifies the signature only once, taking less than 0.1 seconds. The security properties remain the same: the signature is still checked, just faster.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathboot or update pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit is a large feature merge that adds initial support for a new hardware variant, the BitBox03 (STM32U5-based development kit). It introduces new bootloader and firmware binaries, board support crates, vendored Rust dependencies (once_cell, portable-atomic, rtt-target), build scripts, and CI targets. There is no indication in the commit message or diff that this is a security fix or that it addresses any vulnerability. It appears to be routine product/platform enablement work.
Security candidateMerge branch 'assert-v9.27.1'by Marko Bencun · 37c1fde0 · Aug 31, 2026 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · Marko Bencun
Merge branch 'assert-v9.27.1'
45/100 · ThinMessage clarity
✓ 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 adds signed release assertions for the BitBox02 firmware version 9.27.1. It contains only text files and detached signatures that record the expected SHA-256 hash of the official firmware binaries. There is no code change, no bug fix, and no security patch.
Security candidatereleases: add v9.27.1by Marko Bencun · 45bca4de · Aug 31, 2026 · 4 filesMessage 38 · OpaqueInformational 15Details
Commit message · Marko Bencun
releases: add v9.27.1
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
boot or update path
AI analysis · Informational 15/100
This commit simply adds official signed release artifacts for BitBox02 firmware version 9.27.1. It contains two text files with build attestations and two detached signatures. There is no code change, no bug fix, and no security-relevant content in the diff itself.
✓ 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 · Informational 20/100
This commit adds a new read-only piece of information to the BitBox02 device info API: the installed bootloader's marketing version string. It does not change how the device boots, signs, or verifies anything. It is purely an informational feature for apps and users to see which bootloader is installed, and it is not treated by the authors as a security fix.
Security candidateMerge remote-tracking branch 'agent/benma-agent/improve-firmware-loader-ux'by Marko Bencun · 7860a077 · Aug 28, 2026 · 7 filesMessage 50 · ThinLow 34Details
✓ 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 34/100
This commit improves the Python firmware-flashing tool for BitBox hardware wallets. It adds clearer warnings, requires user confirmation before flashing, detects firmware type automatically instead of relying on filename or a debug flag, and exposes more detailed bootloader error messages. The changes are primarily usability and safety improvements for a developer/testing tool, not a fix for an exploitable device vulnerability.
Detect development bootloaders and automatically classify signed and unsigned firmware inputs.
Confirm the detected combination by default, with -y/--yes for non-interactive use.
Keep --debug as a deprecated no-op for backwards compatibility.
Warn about combinations expected to fail without blocking deliberate bootloader error tests.
Treat signature-data errors as nonfatal on development devices and fatal on production devices.
Improve bootloader errors and timeout handling, and document and test the flashing matrix.
83/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundaryupdate trustboot or update path
AI analysis · Informational 23/100
This commit improves a Python helper used by developers to flash firmware onto BitBox hardware wallets. It makes the tool smarter about whether the connected device is a production or development unit, detects signed vs unsigned firmware files automatically, and adds clearer warnings and confirmation prompts. The changes are mostly usability and safety improvements for a developer-facing script, not a fix for a remote attack on user devices.
Security candidateMerge remote-tracking branch 'agent/benma-agent/create-firmware-release'by Marko Bencun · 332cd4d2 · Aug 26, 2026 · 9 filesMessage 50 · ThinInformational 12Details
✓ 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 12/100
This commit is a merge that adds and updates release-helper scripts for the BitBox02 hardware wallet. It introduces a new script to draft GitHub firmware releases, refactors existing scripts to share a common parser for signed firmware files, and adds type annotations and tests. There is no direct evidence in the diff of a security vulnerability or malicious change; it appears to be routine release-tooling maintenance.
Security candidateExpose bootloader version in device infoby Niklas Dusenlund · 03cae40c · Aug 25, 2026 · 29 filesMessage 68 · AdequateInformational 19Details
Commit message · Niklas Dusenlund
Expose bootloader version in device info
Read and validate the installed stage1 header, then expose its marketing version through the HAL and device info protobuf response.
Keep the field absent for legacy bootloaders and return None from the Python client when unavailable.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
update trustdefensive validationcryptography-sensitive pathboot or update path
AI analysis · Informational 19/100
This commit adds a new read-only field to the BitBox02's device information response so the host app can learn which bootloader version is installed. It does not change how data is signed, encrypted, or authorized. The main security-relevant aspect is that the firmware now reads a small version string from the bootloader area and validates the bootloader header's magic value and length before exposing it. This is a defensive information-disclosure change rather than a vulnerability fix.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication pathmerge-commit duplicate discount
AI analysis · Informational 22/100
This commit adds vendored copies of two Rust embedded-crates (cortex-m-rt and its companion macro crate) plus a large auto-generated STM32U5 peripheral access crate to the BitBox02 firmware repository. Vendoring means the project is no longer fetching these libraries from the public crates registry at build time; instead it uses its own frozen copy. The change itself is a build-system/dependency-management refactor. There is no direct evidence in the commit message or diff that this fixes a known security vulnerability, but vendoring can affect how future upstream security patches are applied and the STM32 register definitions are security-relevant because they control hardware protections (TrustZone, debug, flash, etc.).
Security candidateMerge commit 'refs/pull/2061/head' of https://github.com/BitBoxSwiss/bitbox02-firmwareby Marko Bencun · aa92b419 · Aug 24, 2026 · 2 filesMessage 58 · ThinInformational 15Details
Commit message · Marko Bencun
Merge commit 'refs/pull/2061/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
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Informational 15/100
This commit only adds two digital signature files for an already-released firmware version (v9.26.5). These signatures are used by users to independently verify that the published firmware binary matches what a specific signer reviewed. No code, no firmware binary, and no behavior of the device or software is changed. There is no security vulnerability here.
- The graphical simulator starts with the keystore locked; launch with --unlock (requires --preseed) to start it unlocked. Unlocking also retains the BIP39 seed, so user gets no password prompt.
- Entered PINs/passphrases are wrapped in zeroize::Zeroizing, copied straight out of LVGL's buffer. This avoids the intermediate CString of TextareaExt::get_text(), which was dropped without zeroizing.
- Remove the flicker when nav buttons toggle enabled/disabled.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialaccess controlmemory safety
AI analysis · Low 44/100
This commit fixes a security hygiene issue in the BitBox02 firmware's on-screen text-entry code. Previously, when a user typed a PIN or passphrase, the code briefly created an intermediate plain-text copy of the secret that was not securely erased from memory after use. The patch reads the secret directly into a zeroizing container so it is wiped when no longer needed. The same commit also removes a visual flicker on disabled navigation buttons and changes a simulator command-line flag from '--lock' to '--unlock'.