Tor warns me about socks4 using port 8333

[bp]

My wallet is the simple Windows one  Bitcoin vs. o.3.23 beta.
It doesn't do socks 4a which Tor seems to want. Is there a way around this  (that doesn't require a Linix guru recompiling something)?

I don't like those yellow waring messages:

"Jul 06 18:12:45.953 [Warning] Your application (using socks4 to port 8333) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via privoxy or socat) instead. For more information, please see https://wiki.torproject.org/TheOnionRouter/TorFAQ#SOCKSAndDNS."

It only does it when I'm runnining bitcoin, which I want to while I'm Tor browsing.

[1713586733]

1713586733

[1713586733]

1713586733

[1713586733]

1713586733

[1713586733]

1713586733

[1713586733]

1713586733

[akwala]

Here are the instructions to use Tor through Privoxy: http://www.privoxy.org/faq/misc.html#TOR

[bp]

Here are the instructions to use Tor through Privoxy: http://www.privoxy.org/faq/misc.html#TOR

I've got the bundle running polipo. "They" say it's better due to pipelining?

[akwala]

I've got the bundle running polipo. "They" say it's better due to pipelining?

Check the value of socksProxyType in polipo config -- you probably want it to be 'socks4a' or 'socks5':
http://www.pps.jussieu.fr/~jch/software/polipo/manual/SOCKS-parent-proxies.html

[bp]

I've got the bundle running polipo. "They" say it's better due to pipelining?

Check the value of socksProxyType in polipo config -- you probably want it to be 'socks4a' or 'socks5':
http://www.pps.jussieu.fr/~jch/software/polipo/manual/SOCKS-parent-proxies.html

# Uncomment this if you want to use a parent SOCKS proxy:

socksParentProxy = "localhost:9050"
socksProxyType = socks5

that's how it reads now. I'm thinking the missing pound signs at the beginning of those 2 lines means it is already configured to use socks 5.
I could try 4a?
I wish Bitcoin just had 4a built in as I believe that is where the problem is being generated.

[akwala]

# Uncomment this if you want to use a parent SOCKS proxy:

socksParentProxy = "localhost:9050"
socksProxyType = socks5

that's how it reads now. I'm thinking the missing pound signs at the beginning of those 2 lines means it is already configured to use socks 5.
I could try 4a?
I wish Bitcoin just had 4a built in as I believe that is where the problem is being generated.

Your polipo config looks right. My Bitcoin client (on linux) offers only socks4 for connecting thru a proxy, yours is too most likely.

Satoshi addressed the issue in this thread: https://174.143.149.98/smf/index.php?topic=22.0

When using proxy port 9050, it will only make one attempt to connect to IRC, then give up, since it knows it will probably always fail because IRC servers ban all the TOR exit nodes.  If you're using another port, it would assume it might be a regular old normal proxy and would keep retrying IRC at longer and longer intervals.  You should not use Polipo or Privoxy as those are http filters and caches that would corrupt Bitcoin's messages if they make any changes.  Bitcoin might be trying to overcome it by reconnecting.  You should use port 9050.

As riX says, the "is giving Tor only an IP address. Apps that do DNS..." warnings are nothing to worry about.  Bitcoin doesn't use DNS at all in proxy mode.

This is from Feb 2010 but most likely still applies. I am now at the boundary of my knowledge re this... here's what Tor FAQ saya about this warning:
https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#IkeepseeingthesewarningsaboutSOCKSandDNSandinformationleaks.ShouldIworry