[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #19700 [Core Tor/Torsocks]: torsocks does not work with "connectx" (in netcat / nc)
#19700: torsocks does not work with "connectx" (in netcat / nc)
-----------------------------------+------------------------------
Reporter: egonline | Owner: dgoulet
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Core Tor/Torsocks | Version: Tor: unspecified
Severity: Normal | Keywords: torify torsocks
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
-----------------------------------+------------------------------
I found that 'torify', which wraps connections outbound through Tor, did
not work with "nc" (netcat) on Mac OS X in that connections exposed my
true IP address. I looked further into it, and torify works with the flag
to "-O" in nc (nc -O) which, according to the usage, utilizes the standard
connect() system call. However, by default, netcat seems to be now using
the "connectx" system call which torsocks is not hooking. I cannot find
much information on "connectx" except that related to the protocol "SCTP"
on BSD variants (including OS X).
Does anyone know anything about this? Is there any plans to hook calls to
"connectx()" (or, from what I've found, sctp_connectx() is the call)? The
protocol shows up as "tcp4" in a netstat on OS X.
nc usage flag info for -O:
-O Use old-style connect instead of connectx
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19700>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs