[tor-bugs] #8137 [Torsocks]: add option to allow connections to local addresses

[Tor Bug Tracker & Wiki]

#8137: add option to allow connections to local addresses
----------------------+-----------------------------------------------------
 Reporter:  proper    |          Owner:  ioerror
     Type:  defect    |         Status:  new    
 Priority:  normal    |      Milestone:         
Component:  Torsocks  |        Version:         
 Keywords:            |         Parent:         
   Points:            |   Actualpoints:         
----------------------+-----------------------------------------------------

Comment(by proper):

 Replying to [comment:18 cypherpunks]:
 > Replying to [comment:17 proper]:
 > > It lets KGpg fail fatally (wrapped gpg with torsocks), because it
 doesn't understand the torsocks error message.
 >
 > Can you grab a stack trace of this crash?

 Sorry for my wording. "Fails fatally" shouldn't mean crash of kgpg. When I
 clicked on details after trying to connect, I saw the torsocks warning
 (the usual ...may be a TCP DNS reque...).

 The problem is, kgpg wants to phrase gpg's output and gets confused by the
 torsocks warning.

 > >
 > > Gpg itself also fails non-fatally.
 >
 > Is this the same situation as we have with git?

 Yes.

 gpg --recv-keys 9B157153925C303A42253AFB9C131AD3713AAEEF
 gpg: requesting key 713AAEEF from hkp server pool.sks-keyservers.net
 18:28:01 libtorsocks(4719): connect: Connection is to a local address
 (192.168.0.10), may be a TCP DNS request to a local DNS server so have to
 reject to be safe. Please report a bug to
 http://code.google.com/p/torsocks/issues/entry if this is preventing a
 program from working properly with torsocks.
 gpg: key 713AAEEF: "adrelanos <adrelanos at riseup dot net>" not changed
 gpg: Total number processed: 1
 gpg:              unchanged: 1

 > Was 192.168.0.10 also a dns server in your environment

 Yes.

 (Same non-fatal fail when /etc/resolv.conf is empty on 192.168.0.11 and if
 that DnsPort on 192.168.0.10 is disabled.)

 > If so, I'm beginning to think this is the correct behavior because the
 connections appear to be dns lookups to a local dns server (at least
 that's what it appears to be in my local tests).

 Ok, I understand. Could you add an option (configuration file, environment
 variable or command line switch) to suppress that warning please?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8137#comment:19>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online