[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-talk] JonDo uses Tor v0.2.3.25 SocksPort but not for v0.2.4.20-v0.2.4.23; why?
On 08/02/2014 01:17 PM, krishna e bera wrote:
> On 14-08-02 01:48 PM, Mirimir wrote:
>> I've been playing with JAP/JonDo routed through Tor. The JonDo client
>> has a SOCKS proxy option, and it works well with Tor v0.2.3.25
>> SocksPorts in Ubuntu 14.04.1 x64. I installed Tor from the Ubuntu 12.04
>> repository, by the way.
>> After upgrading Tor to v0.2.4.20, which is default in Ubuntu 14.04, the
>> JonDo client can no longer use Tor SocksPorts. Upgrading Tor to the
>> latest v0.2.4.23 doesn't restore that functionality.
>> Please share insight. I'm guessing that a security fix in Tor, or in
>> libraries that it uses, has broken something about how the JonDo client
>> uses SOCKS proxies.
> JAP/JonDo is not affiliated with TorProject so this isnt the place to
> expect support for their products. There is a topic on their support
> forum that may address your issue:
> Jondo no longer able cascade Tor using Port 9150
Right, I'm in that thread. And they seem confused. The SocksPort number
is irrelevant. What matters is the Tor release being used (v.i.).
My intent here is to figure out what changed in Tor that broke JonDo's
SOCKS proxy code. Knowing that, I can file a more coherent bug report
with JonDonym. Or maybe I can even find a workaround.
> Can you be more specific how Tor isnt responding as expected?
What I know now is that JonDo can connect through SocksPort 9050 when
Tor v0.2.4.18-rc or earlier is installed, but not when Tor v0.2.4.19 or
later is installed.
> Maybe pastebin the torrc you are using.
It's the default torrc, not modified.
> Are there two copies of Tor running on your system?
No, there aren't two copies of Tor running. I've not installed the Tor
browser. And each test VM has only ever had one Tor upgrade from release
v0.2.3.25. I'm building from git.
> Check sudo netstat -lpn | fgrep tor to see on which ports the
> running Tor is listening.
It's not a port number issue. I'm using default SocksPort 9050.
> Turn on notice level logging in torrc and watch for connections
> on the socks port.
I'll see what debug logs from both Tor and JonDo tell me.
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to