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

config: apply --torisolation to --proxy without credentials

Public commit record

What the developer wrote

Authored by Boris Nagaev

73/100 · Adequate
config: apply --torisolation to --proxy without credentials

With --proxy and --torisolation, Tor stream isolation was only enabled
when --proxyuser or --proxypass was also set, so a plain
--proxy=127.0.0.1:9050 --torisolation silently ran without it. The
credentials were only meant to decide whether to warn that they get
overridden, as they did when isolation was added in 2015; the two
conditions were merged in a 2016 refactor.

Enable isolation whenever --torisolation is set, except in bridge mode,
where --onion is also set and gets the isolation instead.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes a configuration bug in btcd, a Bitcoin node implementation. When a user enabled Tor stream isolation with --torisolation and used a proxy without a username/password, the isolation was silently not applied. The fix makes --torisolation work as expected regardless of whether proxy credentials are set, except in 'bridge mode' where a separate onion proxy is configured. The practical effect is that affected users' connections through Tor were not being isolated as they believed, potentially reducing their privacy.

Recommended action

Users running btcd with --proxy and --torisolation but without --proxyuser/--proxypass should upgrade to this commit or a release containing it, because their Tor stream isolation was not active. Operators relying on isolation for privacy should verify their configuration after upgrading. No immediate active-exploitation response is needed; this is a privacy-hardening fix.

Security signals we found

01

Privacy configuration silently ignored

02

Tor stream isolation bypass

03

User expectation mismatch between flags and behavior

04

Regression introduced by prior refactor

Risk score

Why this scored 49/100

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