AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 25 Bitcoin

fix(core): disable unused THP pairing methods

Public commit record

What the developer wrote

Authored by M1nd3r

57/100 · Thin
fix(core): disable unused THP pairing methods

[no changelog]
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
The short version

What changed, and why it matters

This commit removes two unused Bluetooth pairing methods (QR code and NFC) from the default list in Trezor's new 'THP' transport layer, leaving only the code-entry method active in normal builds. In debug/test builds, the removed methods are still available so internal tests can keep running. The change is framed as a cleanup of unfinished features, not as a response to a known security bug.

Recommended action

Treat as a defensive hardening change. Monitor issues #6036, #6037, and #6038 for completion of QR-code and NFC pairing implementations before re-enabling them in production. Verify that `__debug__` builds are not shipped to end users, since they retain the disabled methods.

Security signals we found

01

Reduction of attack surface by disabling unused pairing mechanisms in production builds

02

Debug-only re-enablement of disabled pairing methods for test coverage

03

TODO comments linking to follow-up issues, suggesting feature is incomplete rather than a vulnerability fix

Risk score

Why this scored 25/100

Our methodology →
Potential impact 5/30
Exploitability 3/25
Stealth signal 4/15
Affected reach 4/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.