CryptoUpdated 16h ago

A separate Tor flaw affected thousands of nodes using a non-default setting.

Unlike the mining bug, this one depended on a specific configuration, not a default Bitcoin Core installation. A node had to explicitly enable the non-default -whitelist option. In affected setups, incoming Tor peers got whitelist permissions, which lift various denial-of-service limits and privacy protections. Some software vendors bundled Bitcoin Core with Tor and set the whitelist range to match the Tor daemon’s address; the advisory says that left thousands of reachable mainnet nodes trusting all incoming Tor connections. Default setups were unaffected.

1 publisher1 report

Coverage started 16h ago