BB
← All projectsBitBox

BitBox02 firmware

Firmware and bootloader for BitBox02 signing devices.

BitcoinHardware walletsNormal
Repository coverage

647 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.

193security candidates127second-pass queue338AI analyses
25commits · 30 days
47commits · 60 days
312commits · 180 days
647commits · 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
65Strong · 80–100
281Adequate · 60–79
230Thin · 40–59
71Opaque · 0–39
23security 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 Bencun390117194258
benma's agent892855162
Niklas Dusenlund1112955059
cedwies1257063
Tomas Vrba947074
Cedric Wiese1239049
Jad814062
thisconnect211072
benma211074
Niklas111035
Yasser Aziza111070
Patrick Steiger111045
Analysis record

Published AI watches

Last scanned 53 minutes ago

Moderate 59 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/validate-backup-seed-length'

This commit adds a safety check to the BitBox02 hardware wallet's backup loading code. It now rejects backup files that claim to contain a 'seed' longer than 32 bytes. Without this check, a tampered or malformed backup could potentially ca…

Added input validation on deserialized seed_length fieldBounds check prevents oversized seed length (>32 bytes) from being acceptedNew unit test covers malformed backup with seed_length mismatch
f6d2942cby Marko Bencun+34−01 file
No security note in commit
Low 44 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/reject-oversized-policy-keys'

This commit adds a length check before showing a Bitcoin policy key on the BitBox02 device screen. Previously, an extremely long key string could be displayed or processed without a size limit. The fix rejects keys whose on-screen text exc…

Input size limit added before UI confirmationNew unit test for boundary condition (MAX_CONFIRM_BODY_SIZE and MAX_CONFIRM_BODY_SIZE + 1)Potential UI truncation or buffer issue mitigated for policy key display
1e674dfcby Marko Bencun+43−01 file
No security note in commit
Moderate 60 AI analysisMessage 90 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

backup: validate decoded seed length

This update fixes a bug in how the BitBox02 hardware wallet reads backup files from an SD card. A tampered backup file could claim to contain a seed longer than the 32-byte limit, which previously caused the device to panic (crash) when li…

Out-of-bounds/panic condition in backup parsingMissing input validation on decoded protobuf fieldSD-card backup file could be attacker-controlled
80baf1eeby benma's agent+34−01 file
Vendor flagged security relevance
Low 44 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: reject oversized policy keys

This commit fixes a user-interface safety issue in the BitBox02 hardware wallet's Bitcoin multi-signature policy registration. Previously, a very long policy key could be approved by the user even though the device could not display the fu…

Input validation added to enforce UI display limitPrevents registration of keys that cannot be fully displayedBoundary test added at MAX_CONFIRM_BODY_SIZE and MAX_CONFIRM_BODY_SIZE+1
203bb0aaby benma's agent+43−01 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 60 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

bb03 ui: replace long touch with slide to confirm

This commit changes how users confirm sensitive actions on the BitBox03 hardware wallet. It replaces a 'hold/long-press to confirm' button with a 'slide to confirm' gesture, similar to the swipe gestures used on many smartphone lock screen…

cc6ae75dby Jad+40−781 file
No security note in commit
Low 28 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

bb03 UI: slide to confirm

This commit adds a new 'slide to confirm' user-interface control to the BitBox03 hardware wallet. It is a deliberate UX/security feature for high-risk actions (like approving transactions), replacing a simple tap with a drag gesture. The c…

New high-stakes confirmation gesture (slide instead of tap)Input hardening: per-sample advance cap, off-track rejection, non-pointer rejectionSnap-back behavior on incomplete slides to prevent accidental confirmation
30a68c8dby Jad+3076−111 files
No security note in commit
Informational 11 AI analysisMessage 28 · Opaque
BB BitBoxBitBox02 firmware BitcoinHardware wallets

u2f: fix refresh screen

This commit fixes a UI cleanup bug in the BitBox02 hardware wallet's U2F (Universal 2nd Factor) feature. Previously, a 'Refresh webpage' screen could be destroyed without clearing the pointer that tracked it, potentially leaving a dangling…

dangling-pointer mitigationuse-after-free preventionfirmware UI state cleanup
890f4ce3by benma's agent+17−11 file
No security note in commit
Low 27 AI analysisMessage 28 · Opaque
BB BitBoxBitBox02 firmware BitcoinHardware wallets

u2f: fix nudge screen

This commit fixes how a small on-screen reminder (the 'nudge screen') for U2F is created, tracked, and cleaned up. Before the fix, the code could lose track of the reminder screen or mishandle its removal, which might cause display glitche…

Use-after-free / dangling-pointer risk: global _nudge_label pointer could outlive the component it referencesUI state inconsistency: previous callback set _nudge_label = NULL on screen pop, but component cleanup may occur later or not at allMemory management fix: custom cleanup wrapper now synchronizes global pointer with component lifetime
931e75d6by benma's agent+22−71 file
No security note in commit
Low 42 AI analysisMessage 58 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Fix GroundedCell result lifetime

This commit fixes a bug in the U2F confirmation workflow where the firmware could read a result from memory that had already been cleared, potentially giving an incorrect success/failure answer. The fix simply reads the result before wipin…

use-after-clear / stale reference in task stateincorrect result lifetime orderingU2F confirmation workflow
dcd408f9by benma's agent+1−11 file
No security note in commit
Low 39 AI analysisMessage 73 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

rust: initialize C output buffers

This commit fixes a class of low-level memory-safety bugs where Rust code was given buffers containing uninitialized bytes. Rust's rules require every byte of a slice to be initialized, even if the function will overwrite them. Passing uni…

Undefined behavior at C/Rust FFI due to uninitialized buffers being treated as Rust slicesPotential optimizer-dependent behavior from violating Rust slice initialization rulesHardening of cryptographic output paths (SHA-256, HMAC-SHA256, HMAC-SHA512)
511018eaby benma's agent+52−2713 files
Vendor flagged security relevance
Moderate 60 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

factorysetup: validate RTT message length

This commit fixes a bug in the BitBox02 factory setup tool that receives debug messages over SEGGER RTT. Previously, if a message said it contained more bytes than were actually received, the code would copy whatever leftover data happened…

Copy of uninitialized stack data into command buffer (information disclosure / undefined behavior)Missing length validation against actual bytes receivedFactory-only code path (factorysetup), not normal user firmware operation
bb882fc0by benma's agent+5−01 file
Vendor flagged security relevance
Low 42 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

memory: initialize BLE random buffer

This commit fixes a minor but real security hygiene issue in the BitBox02 Plus hardware wallet. Before the patch, a 32-byte buffer meant to hold freshly generated random bytes for Bluetooth Low Energy (BLE) pairing security was not initial…

Uninitialized cryptographic buffer in security-critical reset routineBLE identity key (IRK) and identity address derivation contextDefense-in-depth initialization of random material
135bb8baby benma's agent+1−11 file
No security note in commit
High 74 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

eth: limit EIP-712 recursion depth

This commit adds a hard limit on how deeply nested Ethereum typed-message (EIP-712) structures can be when the BitBox02 hardware wallet signs them. Without the limit, an attacker could craft a message type that refers to itself over and ov…

Adds explicit recursion-depth cap to attacker-controlled input parsingPre-validates schema roots before host callbacks or user confirmationProtects against stack exhaustion / denial-of-service from deeply nested EIP-712 types
4ccadcc0by benma's agent+196−451 file
No security note in commit
Moderate 59 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: limit Miniscript encoding depth

This commit adds a safety limit to how deeply nested a Bitcoin policy (a set of spending rules) can be before the BitBox02 hardware wallet will reject it. Without such a limit, an attacker could craft an unusually deep policy that causes t…

Adds explicit depth bound to prevent recursive stack exhaustionApplies to both WSH and Taproot (TR) policy parsing pathsIncludes boundary and regression-style tests for deep policies
82346eebby benma's agent+109−01 file
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

py: extract bootloader connection

This commit is a minor code cleanup in a Python helper script. It moves existing bootloader connection logic into a small nested helper function to satisfy a style checker (pylint's limit on the number of return statements). No behavior ch…

886113d0by benma's agent+10−61 file
No security note in commit
Informational 15 AI analysisMessage 43 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

prepare v9.26.5

This commit is a routine release bookkeeping change. It updates the version number from v9.27.0 to v9.26.5 and reorganizes the changelog so that two bug fixes are listed under the new v9.26.5 release section instead of 'Unreleased'. The ac…

51ce24e6by benma's agent+5−22 files
No security note in commit
Low 30 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

api: disable BitBoxSync by default

This commit turns off a feature called BitBoxSync by default. Unless a developer explicitly enables it during build, any request to use BitBoxSync will now receive a standard 'disabled' error. The change is framed as temporary while API ch…

Feature-gates an API that was previously reachable by defaultReturns Error::Disabled for requests to the gated APICommit message describes the change as temporary pending API changes
93d36fc8by benma's agent+7−02 files
No security note in commit
Low 42 AI analysisMessage 70 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

rust: bound executor queue

This commit replaces an unbounded task queue inside the BitBox02 firmware's Rust executor with a fixed 16-slot ring buffer. It also adds a hard limit of 16 active tasks and protects queue access with critical sections so interrupt-driven c…

Replaced unbounded queue with fixed-capacity ring buffer to prevent memory exhaustionRemoved allocation from scheduling/wake path, including interrupt contextAdded critical-section synchronization between wakers and main-loop executor
b99e200aby benma's agent+186−285 files
No security note in commit
Moderate 57 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

rust: use static no-op waker

This commit replaces a custom-built notification helper (a 'waker') inside the BitBox02 firmware's Rust code with a built-in, memory-safe no-op version. The old helper used heap memory and reference counting (Arc), which could be freed by …

Eliminates heap-allocated Arc in waker constructionRemoves custom RawWakerVTable with unsafe clone/wake/drop operationsPrevents ISR callbacks from freeing Arc while heap allocator is active
5be42f61by benma's agent+2−523 files
Vendor flagged security relevance
Moderate 59 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

usb: block HWW during U2F workflows

This commit fixes a concurrency bug in the BitBox02 hardware wallet's USB handling. When a U2F (two-factor authentication) workflow is still running on the device's screen, a new hardware wallet request could previously start and reset or …

Concurrency/lifetime bug between HWW and U2F USB endpointsUse-after-free or invalidation risk for live U2F UI objectsSession reset/cancellation path could corrupt shared UI state
0014300bby benma's agent+114−05 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.

Lower-priorityrust: remove unused rust_base58_encode_checkby Marko Bencun · 18dfdbf9 · Nov 13, 2025 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

rust: remove unused rust_base58_encode_check

The last use of rust_base58_encode_check was removed in 704623e1.

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Lower-prioritykeystore: cover early reset in unit testby benma's agent · 94384319 · Nov 12, 2025 · 3 filesMessage 55 · ThinTriage 0Details
Commit message · benma's agent

keystore: cover early reset in unit test

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritykeystore: test unlock counter resetby benma's agent · 53dead8c · Nov 12, 2025 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · benma's agent

keystore: test unlock counter reset

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Security candidatekeystore: add locked lockout testby benma's agent · 39c1f85f · Nov 12, 2025 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · benma's agent

keystore: add locked lockout test

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 15/100

This commit only adds a new automated test to the BitBox02 firmware. It checks that entering the wrong password repeatedly while the device is already locked correctly triggers the lockout mechanism and eventually wipes the seed. There is no change to production code, no new feature, and no fix to an existing bug.

AI review queuedkeystore: tighten hex literalsby benma's agent · a9963d80 · Nov 12, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · benma's agent

keystore: tighten hex literals

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only changes test code in a Rust firmware file. It replaces runtime hex string decoding with a compile-time `hex!()` macro and removes unnecessary `.unwrap()` and `.try_into()` conversions. There is no change to production behavior, no security fix, and no vulnerability introduced.

Lower-prioritykeystore: use slice::first_chunkby Marko Bencun · c7857bd7 · Nov 12, 2025 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

keystore: use slice::first_chunk

Small optimization, avoiding creating an intermediate subslice.

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
AI review queuedwrapper.h: clang-formatby Marko Bencun · dda5af38 · Nov 12, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Marko Bencun

wrapper.h: clang-format

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is purely a code formatting change. It reorders two #include lines in a C header file so they are sorted alphabetically, matching the project's clang-format style. No functionality was changed, no security bug was fixed, and no new attack surface was introduced.

Lower-priorityrust/keystore: use HAL in encrypt_and_store_seedby benma's agent · aceededf · Nov 12, 2025 · 6 filesMessage 65 · AdequateTriage 0Details
Commit message · benma's agent

rust/keystore: use HAL in encrypt_and_store_seed

For `random`, and in the future for memory access.

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Names security-relevant behavior explicitly
Lower-prioritykeystore: port keystore_encrypt_and_store_seed to Rustby benma's agent · a5db95a5 · Nov 12, 2025 · 10 filesMessage 50 · ThinTriage 0Details
Commit message · benma's agent

keystore: port keystore_encrypt_and_store_seed to Rust

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityrust/keystore: add invalid seed size test for encrypt_and_store_seedby Marko Bencun · d1212b60 · Nov 12, 2025 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Marko Bencun

rust/keystore: add invalid seed size test for encrypt_and_store_seed

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityrust/keystore: simplify securechip error propagationby Marko Bencun · fe739549 · Nov 12, 2025 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

rust/keystore: simplify securechip error propagation

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritybitbox02-sys/build.rs: remove unused funcsby Marko Bencun · e0c3549e · Nov 12, 2025 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Marko Bencun

bitbox02-sys/build.rs: remove unused funcs

Re-introduced in a rebase error in bf923f7d64a918e4fa975a03d3a3f424c5075f1fad607ccffc62f9b89b637e32.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Security candidateorientation-screen: Migrate to rustby Niklas Dusenlund · eb9513b3 · Nov 12, 2025 · 27 filesMessage 60 · AdequateInformational 24Details
Commit message · Niklas Dusenlund

orientation-screen: Migrate to rust

create an async friendly hardware supported delayin C and wrap it in
rust using Future.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
boot or update path
AI analysis · Informational 24/100

This commit rewrites the BitBox02's startup orientation screen from C to Rust and introduces a new shared delay/timer subsystem. It is a refactoring change: the device still asks the user to pick screen orientation at boot, then waits 1.3 seconds before switching to the lock screen and enabling USB/Bluetooth. The rewrite changes how internal timers and product-version strings are handled, but it does not add or remove security features. There is no vendor statement that this fixes a security bug.

AI review queuedDX: Breakpoint in panicby Niklas Dusenlund · 3dd0ea25 · Nov 12, 2025 · 4 filesMessage 28 · OpaqueInformational 15Details
Commit message · Niklas Dusenlund

DX: Breakpoint in panic

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: broader security terminologysecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit is a developer-experience (DX) improvement that adds a debug breakpoint instruction inside the firmware's Rust panic handler. When the firmware crashes, it will now halt at a breakpoint if a debugger is attached, making it easier for developers to inspect the crash. It does not change any security-sensitive behavior in normal operation and does not introduce a vulnerability.

Lower-prioritykeystore: port is_locked to Rustby Marko Bencun · b475b8d9 · Nov 12, 2025 · 7 filesMessage 45 · ThinTriage 0Details
Commit message · Marko Bencun

keystore: port is_locked to Rust

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritykeystore: port retained_seed_hash to Rustby Marko Bencun · ca1458f6 · Nov 12, 2025 · 5 filesMessage 45 · ThinTriage 0Details
Commit message · Marko Bencun

keystore: port retained_seed_hash to Rust

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidatekeystore: port copy_seed and retain_seed to Rustby Marko Bencun · 35dd5c89 · Nov 12, 2025 · 5 filesMessage 60 · AdequateLow 26Details
Commit message · Marko Bencun

keystore: port copy_seed and retain_seed to Rust

Same as with the bip39 seed in the previous commit.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
secret or key material
AI analysis · Low 26/100

This commit rewrites two internal seed-handling functions from C to Rust as part of an ongoing porting effort. It moves where the encrypted wallet seed is stored and how it is decrypted, but keeps the same encryption design. There is no direct evidence in the commit that this fixes or introduces a security bug; it is primarily a code-rewrite change.

Security candidatekeystore: port bip39 unlock/retain to Rustby Marko Bencun · e0451ea8 · Nov 12, 2025 · 6 filesMessage 80 · StrongLow 26Details
Commit message · Marko Bencun

keystore: port bip39 unlock/retain to Rust

retain_bip39_seed encrypted the seed, copy_bip39_seed decrypted
it. This is ported to a helper struct `RetainedEncryptedBuffer` that
does the same. The helper struct is made because the other
seed (_retained_seed_encrypted) does the exact same operation, just
with a different purpose string when hashing, so we can reuse that
later when porting retain_seed/copy_seed.

_is_unlocked_bip39 is not ported, as it is redundant and equivaent with
RETAINED_BIP39_SEED being Some().

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
secret or key material
AI analysis · Low 26/100

This commit rewrites the code that keeps the BIP-39 seed temporarily encrypted in memory, moving it from C to Rust. It is a refactoring/porting change, not a fix for a known bug or attack. The same encryption approach is preserved, but the change touches sensitive seed-handling code, so it deserves careful review.

Lower-prioritykeystore: use HAL/Random in create_and_store_seedby Marko Bencun · 7946f42b · Nov 12, 2025 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

keystore: use HAL/Random in create_and_store_seed

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Lower-priorityci: run unit tests on macosby Niklas Dusenlund · d38baecf · Nov 11, 2025 · 2 filesMessage 67 · AdequateTriage 0Details
Commit message · Niklas Dusenlund

ci: run unit tests on macos

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedworkflow/unlock: add unit test for failed passwordby Marko Bencun · 1010d2aa · Nov 10, 2025 · 1 fileMessage 83 · StrongInformational 15Details
Commit message · Marko Bencun

workflow/unlock: add unit test for failed password

Mainly to test that the number of remaining attempts is displayed -
other unit tests for unlocking exist in keystore.rs.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit only adds a new unit test and refactors existing test code to use a different hex literal helper. It does not change any production firmware behavior. The new test verifies that when a wrong password is entered during device unlock, the user sees a 'Wrong password, 9 tries remain' message and the device stays locked. There is no security fix or vulnerability here.

AI review queuedformattingby Niklas Dusenlund · 25b878ee · Nov 6, 2025 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Niklas Dusenlund

formatting

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only adds a single space after two type casts in the same C source file. It is a pure code-formatting change with no functional difference and no security relevance.

Lower-priorityci: Add missing ENV variableby Niklas Dusenlund · 3138388a · Nov 6, 2025 · 3 filesMessage 80 · StrongTriage 0Details
Commit message · Niklas Dusenlund

ci: Add missing ENV variable

TARGET_BRANCH was lost during refactoring of CI from a single script to
multiple github jobs

(also fix existing formatting issues)

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
documentation-only discount
Lower-priorityrust: add zeroizing str to cstr util functionby Marko Bencun · b2c49059 · Nov 6, 2025 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Marko Bencun

rust: add zeroizing str to cstr util function

Not using CString as it did not look to me like it was actually
preallocating for the null terminator, and reallocation would leave
unzeroed copies.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidateformatting: Indent preprocessor directivesby Niklas Dusenlund · 90895379 · Nov 5, 2025 · 63 filesMessage 35 · OpaqueInformational 15Details
Commit message · Niklas Dusenlund

formatting: Indent preprocessor directives

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive pathseed or entropy pathboot or update pathparser or protocol path
AI analysis · Informational 15/100

This commit is purely a code-style change. It tells the project's automatic formatter (clang-format) to indent preprocessor directives like #if, #include, and #error, and then applies that new rule across many source files. No program logic, security checks, or behavior were changed.