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

openalias: always enforce DNSSEC validation succeeds

Public commit record

What the developer wrote

Authored by SomberNight

50/100 · Thin
openalias: always enforce DNSSEC validation succeeds
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit removes the ability to skip DNSSEC security checks for OpenAlias lookups in the Electrum Bitcoin wallet. OpenAlias turns human-readable names like 'donate@example.com' into Bitcoin addresses using DNS. Previously, users or commands could pass a 'nocheck' flag to accept unvalidated DNS results, which is dangerous because DNS responses can be spoofed or tampered with. The patch now enforces that DNSSEC validation must succeed before any OpenAlias result is used, and it strips out the old 'nocheck' options and unvalidated warnings. This is a hardening change that closes a known weak path where an attacker on the network could trick the wallet into sending money to the wrong address.

Recommended action

Users and integrators should upgrade to a version containing this commit to ensure OpenAlias lookups cannot be used without successful DNSSEC validation. Anyone relying on the `nocheck` flag for sweep/payto/paytomany should stop using aliases in untrusted network environments or ensure proper DNSSEC deployment. No immediate incident response is indicated by the diff alone, but the change is a clear security hardening measure.

Security signals we found

01

Removal of a security bypass flag (`nocheck`) for alias verification

02

Fail-closed enforcement of DNSSEC validation in OpenAlias resolution

03

Removal of user warnings that previously allowed proceeding with unvalidated DNSSEC results

04

Docstring added stating DNS is completely insecure without DNSSEC

05

Change from optional validation to mandatory validation across CLI and GUI code paths

Risk score

Why this scored 59/100

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