Opened 11 years ago

Closed 4 years ago

#801 closed defect (wontfix)

Torify+dsocks: A listener connection returned a socket with a mismatched family

Reported by: m4rco- Owned by: dgoulet
Priority: Low Milestone:
Component: Core Tor/Torsocks Version: 0.2.0.30
Severity: Keywords:
Cc: m4rco-, nickm, arma, proper@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by dgoulet)

When i try to torify something trought dsocks-torify.sh it doesn't works.

Example:
dsocks-torify.sh nmap -P0 -v -n 1.2.3.4 -p21 -sV

Starting Nmap 4.50 ( http://insecure.org ) at 2008-08-16 13:45 CEST
Initiating Connect Scan at 13:45
Scanning 87.29.167.157 [1 port]
nmap: (dsocks) couldn't connect to proxy at 127.0.0.1:9050
Discovered open port 21/tcp on 87.29.167.157
Completed Connect Scan at 13:45, 0.14s elapsed (1 total ports)
Host 87.29.167.157 appears to be up ... good.
Interesting ports on 87.29.167.157:
PORT STATE SERVICE
21/tcp open ftp

Nmap done: 1 IP address (1 host up) scanned in 0.204 seconds

this is the entry in the Tor debub log

[info] connection_handle_listener_read(): Bug: A listener connection returned a socket with a mismatched family. Socks listener for addr_family 2 gave us a socket with address family 0. Dropping.

i've the last version of dsocks aviable from darwinports.

Thanks to all!

bye

[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]

Child Tickets

Change History (4)

comment:1 Changed 11 years ago by nickm

That's very strange! It can only happen when an accept() call on an AF_INET listener returns an AF_UNSPEC socket,
(assuming that AF_INET==2 an AF_UNSPEC==0).

I wonder if the dsocks code is doing something weird here.

comment:2 Changed 7 years ago by proper

Cc: proper@… added

Do you still care about this bug or got it in meanwhile obsolete?

comment:3 Changed 4 years ago by nickm

Component: TorifyTorsocks
Owner: set to dgoulet

comment:4 Changed 4 years ago by dgoulet

Description: modified (diff)
Resolution: Nonewontfix
Status: newclosed

Too old and reported on deprecated version of torsocks. Closing it as obsolete.

Note: See TracTickets for help on using tickets.