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

lightningd: conceal secret config values in listconfigs

Public commit record

What the developer wrote

Authored by Andezion

73/100 · Adequate
lightningd: conceal secret config values in listconfigs

Changelog-Changed: JSON-RPC: `listconfigs` shows `...` instead of the value of `wallet`, `recover`, `tor-service-password`, `bitcoin-rpcpassword` and the old `bookkeeper-db`, for every caller; unset ones are omitted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

(cherry picked from commit 6ed212e4856bce2b3392bac1d2fe2df90f3edfde)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit changes Core Lightning's `listconfigs` RPC command so that several secret or sensitive configuration values are hidden and shown as '...' instead of their real content. Previously, anyone who could call `listconfigs` could see values like the Bitcoin RPC password, wallet database connection string, recovery seed, Tor service password, and old bookkeeper database details. The commit also fixes a bug where concealed options were still being shown when they were not actually set. This is a security hardening change that reduces the risk of leaking credentials to unauthorized callers.

Recommended action

Treat this as a security hardening fix and include it in release notes. Operators should upgrade to prevent accidental credential exposure through `listconfigs` and audit any existing logs or backups that may have captured these values. No immediate incident response is required unless `listconfigs` output has been shared with untrusted parties.

Security signals we found

01

Concealment of sensitive configuration values in RPC output

02

Fix for unset concealed options still being exposed

03

Credential-leak prevention for Bitcoin RPC, wallet DSN, recovery secret, Tor password

04

Schema documentation updated to reflect concealment behavior

05

Security-relevant hardening with no functional protocol change

Risk score

Why this scored 65/100

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