Error opening stream: system:111

[sheepdestroyer]

i got problem to compile but overcame it. Now compilation worked but i get the following "Error opening stream: system:111" when trying it :

[sheepdestroyer@sheepora tortunnel]$ ./torproxy -p 9050 -r torproxy 0.3 by Moxie Marlinspike. Retrieving directory listing... Choosing exit node at index: 677 out of 1566 listings... Connecting to exit node: 90.190.27.125:5190 SSL Connection to node complete. Setting up circuit. Connected to Exit Node. SOCKS proxy ready on 9050. Got SOCKS Connection... Got SOCKS Request: 74.125.235.176:80 Error opening stream: system:111

this happens with any attempt to use it, for exemple with the folllowing test :

[sheepdestroyer@sheepora ~]$ curl --socks5 localhost:9050 google.com curl: (7) Can't complete SOCKS5 connection to 127.0.0.1:1024. (4)

[Hengjie]

I get similar issues.

[cclements]

Same here. Definitely something broken somewhere.

[L0j1k]

Okay, I did a little digging into boost::system::error_code and what I can see here is that TorProxy is handing off a system-level error code. We see the "system:111" error category/code, which on a Linux system is:

define ECONNREFUSED 111 /* Connection refused */

I got this information from /usr/include/asm-generic/errno.h which you can see summarized on this webpage: http://www-numi.fnal.gov/computing/minossoft/releases/R2.3/WebDocs/Errors/unix_system_errors.html So... somehow we're getting a refused connection even though it successfully opens an SSL connection to the exit node. I'll do some more digging and see if I can find anything else out. If I don't update this, I probably fell asleep and then moved on to using socat. :P

[rofl0r]

@L0j1k hello, i've seen that you starred haad/proxychains i wanted to inform you that that repo is technically a catastrophe: see this explanation https://github.com/rofl0r/proxychains/wiki/quality-of-haad's-fork,-or-%22reasons-for-the-split%22

you should instead use https://github.com/rofl0r/proxychains

[L0j1k]

@rofl0r Thanks for the heads up. I didn't even see your repo. I'm not normally one for git fights, but you provide good examples. Also, you play DF, so you win by default.

[rofl0r]

@L0j1k glad to hear!

btw regarding the issue with tortunnel: i ran into it sometime ago as well, after i applied these 2 patches 1) make it possible to specify listening interface http://sprunge.us/XjAg 2) fix segfault enumerating tor hosts http://sprunge.us/ifSD (in a very unidiomatic way...)

according to a tor developer, tortunnel is considered an abuse of the network, so single-hop circuits were disabled a while back.