Opened 6 years ago

Closed 5 years ago

#11541 closed defect (invalid)

torsocks Does Not Work with dig on Fedora 20

Reported by: eviljoel Owned by: dgoulet
Priority: Medium Milestone:
Component: Core Tor/Torsocks Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I am trying to follow the nmap-ncat instructions here https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO/ssh for connecting to a tor hidden service over SSH. I can't seem to get it working. This is what I execute "torsocks dig @213.73.91.35 +tcp +short www.google.com" which returns ";; communications error to 213.73.91.35#53: end of file". When I execute "dig @213.73.91.35 +tcp +short www.google.com" without torsocks, IP addresses are returned. I have verified I am connected to tor via setting up my Firefox (not tor browser bundle) proxy settings and going to check.torproject.org.

I am on Fedora 20. I am using tor version tor.x86_64-0.2.4.21-tor.1.rh20 and torsocks version torsocks.x86_64-1.3-2.fc20. You can contact me at eviljoel@… if you have any questions.

Child Tickets

Change History (4)

comment:1 Changed 6 years ago by dgoulet

Quickly, can you tell me which version of torsocks you are using? I can see that Fedora 20 still uses the 1.3 which has been replaced recently by 2.0 (still in rc cycle).

You might want to go with the new version on the git head or/and ping packagers that they should update :). https://gitweb.torproject.org/torsocks.git

comment:2 Changed 6 years ago by eviljoel

It was in my original post but torsocks.x86_64-1.3-2.fc20. I'll try your suggestion after work and see if Fedora maintainers update that stuff mid-release. If they do, I'll request that they update it.

comment:3 Changed 6 years ago by eviljoel

That did work. The following command now returns IP addresses:

ssh -o "ProxyCommand nc --proxy 127.0.0.1:9050 --proxy-type socks4 $(LD_PRELOAD=/home/eviljoel/Desktop/torsocks/torsocks/src/lib/.libs/libtorsocks.so.0.0.0 dig @213.73.91.35 +tcp +short %h | head -n 1) %p" www.google.com

Unfortunately, I was actually trying to resolve an .onion URL. I missed the line that says "...nmap-ncat version is not compatible with .onion addresses...". I guess I'll have to roll my own netcat-openbsd.

Anyway, thanks for helping me out with this. I definitely learned something in the process.

comment:4 Changed 5 years ago by dgoulet

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.