Quote from: BitcoinFX on February 01, 2010, 10:08:54 PM
“Your application (using socks5 on port xxxx) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via polipo or socat) instead.”
Bitcoin is using ip-adresses, not hostnames, so there’s no need for dns. Tor thinks that since bitcoin is trying to connect to an ip without looking it up through tors internal dns, it’s using a regular dns.
Quote from: BitcoinFX on February 01, 2010, 10:08:54 PM
However, I still get occasional warnings for these ports 8333 (expected Bitcoin ‘default’) and 6667 (which if i’m not mistaken is an IRC port !?)
Bitcoin is using port 8333, even though it’s relaying it through tor on port 9050.. Tongue 6667 is irc, bitcoin uses an irc-server to distribute the nodelist. (If you know the ip of another computer running bitcoin, you can specify the -connect option to avoid using the nodelist).
Quote from: BitcoinFX on February 01, 2010, 10:08:54 PM
However, Bitcoin must try to connect with all nodes to check its not missing any blocks !
No, it’s enough if you’re just connected to one single node, as long as it’s got a copy of the longest block-chain.