Bitcoin Forum
December 05, 2016, 04:57:52 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: bitcoind + vidalia and potenially dangerous connections  (Read 5199 times)
Red Emerald
Hero Member
*****
Offline Offline

Activity: 742



View Profile WWW
November 15, 2011, 01:02:15 AM
 #1

I setup a small xubuntu VM to act as a safe for my wallet.  I installed tor, polipo, and vidalia more for fun than anything.  I set bitcoind to use the tor proxy and set my browser to use polipo.  My browser is able to connect to the tor network fine.

I added the proxy to my bitcoin.conf
Code:
proxy=127.0.0.1:9050

Bitcoin seems to be using the proxy, but when I look at Vidalia's message log, I see lots of

Quote
Potentially Dangerous Connection!
One of your applications established a connection through Tor to "x.x.x.x:8334" using a protocol that might leak information about your destination. Please ensure you configure your applications to use only SOCKS4a or SOCKS5 with remote hostname resolution.

So then I did

Code:
sudo apt-get install torsocks

and then I start the daemon with

Code:
torify bitcoind -daemon

but I get console warnings and I still get the "Potentially Dangerous Connection!" messages

Code:
[user@btc-ubuntu ~]$ torify bitcoind -daemon
16:57:35 libtorsocks(2539): The symbol res_init() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_query() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_search() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_send() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_querydomain() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_init() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_query() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_search() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_send() was not found in any shared library. The error reported was: not found!
16:57:35 libtorsocks(2539): The symbol res_querydomain() was not found in any shared library. The error reported was: not found!

Has anyone done this successfully without warning messages?

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Red Emerald
Hero Member
*****
Offline Offline

Activity: 742



View Profile WWW
November 15, 2011, 01:08:39 AM
 #2

I found this page, but am still not sure if I even need to change anything. https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#IkeepseeingthesewarningsaboutSOCKSandDNSandinformationleaks.ShouldIworry

I'm pretty sure bitcoin only uses IP addresses anyway, so I'm thinking these warnings are probably mistaken.

theymos
Administrator
Legendary
*
Offline Offline

Activity: 2492


View Profile
November 15, 2011, 06:10:04 AM
 #3

Bitcoin does do some DNS stuff for bootstrapping, though that message would appear regardless. You can disable the warning with a torrc option.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
marcus_of_augustus
Legendary
*
Offline Offline

Activity: 2086



View Profile
November 15, 2011, 06:52:41 AM
 #4

Bitcoin does do some DNS stuff for bootstrapping, though that message would appear regardless. You can disable the warning with a torrc option.

Disabling the warning does not stop the DNS leak of bitcoin's that Tor has detected though.

theymos
Administrator
Legendary
*
Offline Offline

Activity: 2492


View Profile
November 15, 2011, 08:17:58 AM
 #5

The message appears because Bitcoin is talking to IPs directly over SOCKS4. Even if you stop Bitcoin from using DNS with the -nodnsseed and -noirc switches, you'll still get the warning.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
finway
Hero Member
*****
Offline Offline

Activity: 714


View Profile
November 15, 2011, 09:34:42 AM
 #6

Seems bitcoin client adapts tor not well.

Red Emerald
Hero Member
*****
Offline Offline

Activity: 742



View Profile WWW
November 15, 2011, 07:24:00 PM
 #7

The message appears because Bitcoin is talking to IPs directly over SOCKS4. Even if you stop Bitcoin from using DNS with the -nodnsseed and -noirc switches, you'll still get the warning.

But those flags would be safer, correct? I'm fine with warnings if I am sure that the IPs were given as IPs and not as names.

theymos
Administrator
Legendary
*
Offline Offline

Activity: 2492


View Profile
November 16, 2011, 02:40:33 AM
 #8

But those flags would be safer, correct?

Maybe a little bit.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
astana
Member
**
Offline Offline

Activity: 98


View Profile
November 16, 2011, 04:38:41 AM
 #9

why on earth would you run your bitcoin wallet on tor, to me that's just asking some to hack you.
finway
Hero Member
*****
Offline Offline

Activity: 714


View Profile
November 16, 2011, 04:47:12 AM
 #10

why on earth would you run your bitcoin wallet on tor, to me that's just asking some to hack you.

To stay anonymous.

marcus_of_augustus
Legendary
*
Offline Offline

Activity: 2086



View Profile
November 17, 2011, 10:02:57 PM
 #11

why on earth would you run your bitcoin wallet on tor, to me that's just asking some to hack you.

Actually almost the opposite is true.

Running an unproxied bitcoin always from the same static IP on the internet is like dropping your trousers in public. (Having an unencrypted wallet connected to such a node would be like bending over with trousers around ankles in public.)

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!