Opened 5 years ago

Closed 4 years ago

#16627 closed defect (duplicate)

torsocks 2.1 doesn't work with Oracle Java 8 (Mac OS X 10.9.5)

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

Description

torsocks 2.1 works OK with all applications except Oracle Java 8

For example:

$ torsocks telnet 184.105.238.114
Trying 184.105.238.114...
Connected to 184.105.238.114.
Escape character is '^]'.
This is the telnet autoresponder at v6address.com.
You have connected over IPv4.
Your IP address is 82.X.Y.Z
Connection closed by foreign host.

With java:

$ torsocks java -jar utm_admin.jar 
[Jul 21 11:35:33] WARNING torsocks[11015]: [syscall] Unsupported syscall number 180. Denying the call (in tsocks_syscall() at syscall.c:465)
[Jul 21 11:35:36] WARNING torsocks[11015]: [syscall] Unsupported syscall number 180. Denying the call (in tsocks_syscall() at syscall.c:465)
dyld: lazy symbol binding failed: Symbol not found: _JRSUIGetKey
  Referenced from: /Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libosxui.dylib
  Expected in: flat namespace

dyld: Symbol not found: _JRSUIGetKey
  Referenced from: /Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/jre/lib/libosxui.dylib
  Expected in: flat namespace

Trace/BPT trap: 5

Versions:

$ torsocks --version
Torsocks 2.1.0
$ torsocks java -version
java version "1.8.0_31"
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)

Child Tickets

Attachments (2)

java-crash-with-torsocks.txt (69.7 KB) - added by s.lobanov 5 years ago.
Crash report when java starts with torsocks
config.log (43.9 KB) - added by s.lobanov 5 years ago.
config.log (./configure)

Download all attachments as: .zip

Change History (4)

Changed 5 years ago by s.lobanov

Crash report when java starts with torsocks

Changed 5 years ago by s.lobanov

Attachment: config.log added

config.log (./configure)

comment:1 Changed 5 years ago by yawning

Hm. Not sure if dgoulet has an OSX box, and I don't, and won't.

[Jul 21 11:35:33] WARNING torsocks[11015]: [syscall] Unsupported syscall number 180. Denying the call (in tsocks_syscall() at syscall.c:465)
[Jul 21 11:35:36] WARNING torsocks[11015]: [syscall] Unsupported syscall number 180. Denying the call (in tsocks_syscall() at syscall.c:465)

From what I can tell, syscall 180 is kdebug_trace which is kernel debugger related, and intentionally undocumented. It probably has nothing to do with the issue, at hand. You could try whitelisting it (src/lib/syscall.c), the relevant syscalls.master entry is:

180	AUE_KDEBUGTRACE	ALL 	{ int kdebug_trace(int code, int arg1, int arg2, int arg3, int arg4, int arg5) NO_SYSCALL_STUB; }

But, more likely this is some weird dynamic linker/loader issue.

comment:2 Changed 4 years ago by dgoulet

Resolution: duplicate
Severity: Normal
Status: newclosed

Java is a massive beast that it would be nice to support. Closing this in favor of #11579.

Note: See TracTickets for help on using tickets.