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

use ca validation or tofu pinning for public servers depending on certificate type

Public commit record

What the developer wrote

Authored by Craig Raw

50/100 · Thin
use ca validation or tofu pinning for public servers depending on certificate type
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit changes how Sparrow Wallet validates TLS certificates when connecting to public Electrum servers. Previously, the app avoided saving certificates for public servers and relied on user-approved certificate 'pinning' (TOFU). Now it tries to use normal certificate authority (CA) validation for public servers that have CA-signed certificates, while still using pinning for self-signed certificates. The change also deletes a saved pinned certificate if it expires on a public server, so the app can fetch a fresh, CA-validated one. This is a security-hardening change, not an obvious vulnerability fix, though the prior behavior could have made man-in-the-middle attacks against public servers easier if users routinely accepted changed certificates.

Recommended action

Review the new CA validation path for completeness: ensure hostname verification is enforced, that the isCaSigned helper correctly handles full chains and does not mask validation errors, and that fallback from expired pinned certificates to CA validation cannot be abused by an attacker who can delete or corrupt local cert files. Consider whether public-server TOFU pinning should be deprecated entirely in favor of CA validation.

Security signals we found

01

Change in TLS certificate validation strategy for public servers

02

Addition of CA trust manager path alongside existing pinned-certificate trust manager

03

New certificate storage helpers for CA-signed certificates (.cacert)

04

Deletion of expired pinned certificates for public servers to enable CA re-validation

05

UI error messages updated to mention CA validation failure

06

No explicit CVE, advisory, or vendor security disclosure in commit or references

Risk score

Why this scored 52/100

Our methodology →
Potential impact 12/30
Exploitability 10/25
Stealth signal 8/15
Affected reach 12/15
Confidence 7/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.