at main
3 folders
5 files
Formalize trackball QA: TRKRW parser + hardware suite
- debug_console.py: TrkSelfTest dataclass, parse_trk_selftest, and the
dut.trk_selftest() helper (device token, pin mapping, click level, ISR-armed
state, PASS/FAIL) mirroring kbd_selftest/imu_selftest.
- test_trk_selftest_parse.py: no-hardware parser unit tests over a MockDut
(quadrature PASS, click-held informational, absent, not-armed FAIL, boot
noise, missing line).
- test_trackball.py: trackball-capability-gated self-test (PASS, device match,
ISRs armed — the load-bearing input-path evidence for a device whose motion
cannot be synthesized) plus an absent-graceful check for the rest of the
fleet. Motion is intentionally not driven — it needs a physical finger.
Claude-Session: https://claude.ai/code/session_01SV58JXhfxhhc9DC6vdjBo4
Formalize trackball QA: TRKRW parser + hardware suite
- debug_console.py: TrkSelfTest dataclass, parse_trk_selftest, and the
dut.trk_selftest() helper (device token, pin mapping, click level, ISR-armed
state, PASS/FAIL) mirroring kbd_selftest/imu_selftest.
- test_trk_selftest_parse.py: no-hardware parser unit tests over a MockDut
(quadrature PASS, click-held informational, absent, not-armed FAIL, boot
noise, missing line).
- test_trackball.py: trackball-capability-gated self-test (PASS, device match,
ISRs armed — the load-bearing input-path evidence for a device whose motion
cannot be synthesized) plus an absent-graceful check for the rest of the
fleet. Motion is intentionally not driven — it needs a physical finger.
Claude-Session: https://claude.ai/code/session_01SV58JXhfxhhc9DC6vdjBo4
Harden BLE bond lifecycle and land full on-device QA coverage
Defensive BLE audit of src/ble/ (audit dossier: docs/security/audit-ble.md).
The stack was sound; this closes the one actionable finding plus the QA gaps.
BLE-L1 (the finding): BLE bonds survived a vault wipe / factory reset — the
NimBLE keystore (nimble_bond NVS), the kleidos_blnames name blob, and its RTC
mirror all live in NVS, which wipeAll() never touched, so a previous owner's
bonded hosts and the device IRK persisted across a factory reset. Add
BondStore::factoryReset() (erases all three backing stores, radio OFF) exposed
via Facade::factoryResetBonds() and wired into every wipe path (pin_state
brute-force wipe, settings wipe, boot recovery, debug WIPEVAULT/lockout). Clearing
the RTC mirror is essential — reconcile() would otherwise resurrect the bonds
after the post-wipe reboot. Validated on-device. Native regression in
test_bond_store / test_name_store.
QA coverage: implement and validate the eight proposed BLE QA tests —
nc-reject (QA-1), conn-param (QA-2), disconnect (QA-4), factory-reset regression
(QA-5), adv-minimization (QA-7) on the mastodon Linux/BlueZ central; redaction
(QA-6) + UTF-8 robustness (QA-8) in CI; and N4 eviction (QA-3) end-to-end on the
DUT via the ESP32 Plus1 central. New mastodon scenarios (adv-scan,
disconnect-mid-type, conn-param, evict, restore) in ble_attack.sh + ble_probe.py.
Plus1 harness: unify the separate _blehost/_wifihost binaries into one
command-switchable BLE+WiFi binary (m5stickc_plus1_host, MODE BLE|WIFI|NONE).
Add an OWNADDR command that rotates the central's LE random-static identity
(fills the DUT bond table for N4 eviction, no BlueZ). Fix two firmware bugs: the
harness was mute without KLEIDOS_USB_SERIAL_CONSOLE (serial facade compiled to
no-op stubs), and identity rotation broke discovery until OWNADDR/FORGET also
clear the resolving list (ble_hs_resolv_list_clear_all).
CVE maintenance: register CVE-2025-53470/53477 (NimBLE HCI, low-reachability)
and record the advertising-report/Mesh/BlueDroid/BluFi CVEs as not-applicable;
2026 re-check found no new NimBLE CVEs. Plus readability + file:line doc-drift
fixes across ble.md / cve-register.md.
Gates: native 233/233, sticks3 + m5stickc_plus2 + m5stickc_plus1_host build
clean, pio check no defects, clang-format/check_layout/check_variants/typos/
gitleaks/ruff/editorconfig all pass.
Claude-Session: https://claude.ai/code/session_01MyjYtwfLCwUUfGVYuTQqSv