📅 Original date posted:2015-08-18
📝 Original message:So I checked, and the code described *does not* run when behind a
proxy of any kind, including tor:
https://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8faea9c2b2c785a2f5b68aa4c23#diff-11780fa178b655146cb414161c635219R265
At least based on my admittedly weak understanding of how the internal works.
Hopefully I save the next reader of your post from also having to dig
around to find the code and realize this is a false alert.
On Tue, Aug 18, 2015 at 6:36 PM F L via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> Bitcoin XT contains an unmentioned addition which periodically downloads
> lists of Tor IP addresses for blacklisting, this has considerable privacy
> implications for hapless users which are being prompted to use the
> software. The feature is not clearly described, is enabled by default, and
> has a switch name which intentionally downplays what it is doing
> (disableipprio). Furthermore these claimed anti-DoS measures are trivially
> bypassed and so offer absolutely no protection whatsoever.
>
> Connections are made over clearnet even when using a proxy or onlynet=tor,
> which leaks connections on the P2P network with the real location of the
> node. Knowledge of this traffic along with uptime metrics from
> bitnodes.io can allow observers to easily correlate the location and
> identity of persons running Bitcoin nodes. Denial of service can also be
> used to crash and force a restart of an interesting node, which will cause
> them to make a new request to the blacklist endpoint via the clearnet on
> relaunch at the same time their P2P connections are made through a proxy.
> Requests to the blacklisting URL also use a custom Bitcoin XT user agent
> which makes users distinct from other internet traffic if you have access
> to the endpoints logs.
>
>
>
> https://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8faea9c2b2c785a2f5b68aa4c23
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
Christophe Biocca [ARCHIVE] /
npub1mt…9g5zm
2023-06-07 15:48:19
in reply to nevent1q…f29u
Author Public Key
npub1mtxs7jztn027d9cylej99hltqq9vq84uxm80zl4naxafd9hpxqwsj9g5zmPublished at
2023-06-07 15:48:19Event JSON
{
"id": "8a160a822507541399aabbde9741d12cdd58340ae443a7f246530bc1a8a85faf",
"pubkey": "dacd0f484b9bd5e69704fe6452dfeb000ac01ebc36cef17eb3e9ba9696e1301d",
"created_at": 1686152899,
"kind": 1,
"tags": [
[
"e",
"9e65fc10f160e3a1f8abcad8d1666e0dcd59346530c1336724fc0d2af6334cc4",
"",
"root"
],
[
"e",
"a009c5b16c66fc4dc78356bf0e93aa3e76e646320a364f5f417a10375fc105eb",
"",
"reply"
],
[
"p",
"fc7892eea47289e31dc49660ebe7f00108707eb2ee3b59909accdf0afaa4eb61"
]
],
"content": "📅 Original date posted:2015-08-18\n📝 Original message:So I checked, and the code described *does not* run when behind a\nproxy of any kind, including tor:\n\nhttps://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8faea9c2b2c785a2f5b68aa4c23#diff-11780fa178b655146cb414161c635219R265\n\nAt least based on my admittedly weak understanding of how the internal works.\n\nHopefully I save the next reader of your post from also having to dig\naround to find the code and realize this is a false alert.\n\nOn Tue, Aug 18, 2015 at 6:36 PM F L via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Bitcoin XT contains an unmentioned addition which periodically downloads\n\u003e lists of Tor IP addresses for blacklisting, this has considerable privacy\n\u003e implications for hapless users which are being prompted to use the\n\u003e software. The feature is not clearly described, is enabled by default, and\n\u003e has a switch name which intentionally downplays what it is doing\n\u003e (disableipprio). Furthermore these claimed anti-DoS measures are trivially\n\u003e bypassed and so offer absolutely no protection whatsoever.\n\u003e\n\u003e Connections are made over clearnet even when using a proxy or onlynet=tor,\n\u003e which leaks connections on the P2P network with the real location of the\n\u003e node. Knowledge of this traffic along with uptime metrics from\n\u003e bitnodes.io can allow observers to easily correlate the location and\n\u003e identity of persons running Bitcoin nodes. Denial of service can also be\n\u003e used to crash and force a restart of an interesting node, which will cause\n\u003e them to make a new request to the blacklist endpoint via the clearnet on\n\u003e relaunch at the same time their P2P connections are made through a proxy.\n\u003e Requests to the blacklisting URL also use a custom Bitcoin XT user agent\n\u003e which makes users distinct from other internet traffic if you have access\n\u003e to the endpoints logs.\n\u003e\n\u003e\n\u003e\n\u003e https://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8faea9c2b2c785a2f5b68aa4c23\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e",
"sig": "a8e3bd2c2fd63b8da5a98ee1fb15704257d6469b2a299531d534d514bea08fd9efa0f26826bc80b088d44739d05c0c21fe9a8869527241f80727354711dfe97a"
}