Grimler91
commented
2 years ago Posting details for all these devices would get get complicated, so I'll try to summarize instead
termux-info output for at least the device(s) where it fails would be useful. I have no idea if Fire HD, Fxtec and Unithertz are arm or aarch64 devices, or what kernel version they are using.
It possible this issue isn't with the Android release, but rather some common property using to build these specific Android ROMs.
Rather than ROM specific it seems more likely that it has to do with the kernel version and available syscalls. Your previous fix solved the earlier issues by adding support to torsocks for handling additional syscalls. Unfortunately though the kernel version doesn't guarantee a certain set of syscalls, kernel developers might have backported additional syscalls to make kernel work with a newer android version.
stale[bot]
xtkoba
Problem description
While setting up a couple of new Android 8.1 test devices, I realized that torsocks wasn't working. I inititally thought it might be an issue with the recent package updates, so I tested it on my other devices. It seems to work just fine on 7.0, 8.0, 10.0 and 11.0 but hangs (aka is broken) on 8.1 and 9.0.
It's worth noting that my 8.1 devices are actually both using Lineage 15.1. But I have two different Android 9.0 devices, from different manufacturers (Unihertz and Fxtec), and they are both failing in the same way (they just hang).
What steps will reproduce the bug?
Running:
torsocks curl api4.ipify.orgWill hang, until killed. On the other hand, running with
proxychains4or havingcurlconnect to the TOR SOCKS5 proxy directly both work.What is the expected behavior?
The command should return the IP address of the TOR exit node.
System information
Posting details for all these devices would get get complicated, so I'll try to summarize instead. I tested torsocks using a Samsung with droid 7.0, a Motorola with droid 8.0, an Onn device with droid 10, and a Samsung with droid 11. I also tested torsocks using a Fire HD device with Lineage 18.1 (aka droid 11) and Gateway with droid 11, but both of those devices were using armeabi-v7a versions of Android, so not a great test case.
The devices that were failing/hanging were a Fire HD with Lineage 15.1 (aka droid 8.1), an Fxtec with Android 9, and a Unithertz device, also with Android 9.
So far I've tried recompiling torsocks on the Lineage 15.1 device without success. I haven't tried running it via a debugger yet. I wanted to open up the issue first. I'm hoping someone else can confirm my findings by testing torsocks on other devices with Android 8.1 and 9.0 so we can confirm the problem is specific to Android 8.1 and 9.0. It possible this issue isn't with the Android release, but rather some common property using to build these specific Android ROMs.
I thought the Termux team might have a bigger sample size to poll.
I also noticed that
lsof -nwas triggering a segmentation fault on the failing devices. And while torsocks was working on the 32 bit droid 11 devices it was also complaining about a missing system call.