rofl0r

> ProxyChains-3.1 (http://proxychains.sf.net/) proxychains 3.1 isn't supported. use proxychains-ng instead.

> curl: (7) Unable to receive initial SOCKS5 response. suggests that OP configured **curl** to use a socks proxy, and then used proxychains-ng as well. it's either-or.

anyone tried to get a pure 32bit version of steam and run it with 32 bit proxychains-ng ? for the former there are 2 possible solutions, either use a 32...

> Experimental static AppImages at https://github.com/probonopd/go-appimage. i don't think using go for this is a good idea, go binaries tend to link to almost the entire go runtime, making the...

> I'm testing with CURL and it only supports SOCKS5 protocol, and not SOCKS4 so microsocks and curl are perfectly compatible... > Please, can you provide dual protocol support? why...

> With --socks5 yes; but when you try with SOCKS4, then NO! as expected... > Because I want to use it as an upstream proxy using the SOCKS4 protocol. what...

> A lot supports only SOCKS4 do you have some actual examples of programs supporting only socks4 ?

yeah, you can compile microsocks like this: `CPPFLAGS=-DCONFIG_LOG=0 make` which disables the logging. this is then hardcoded into the binary though. you could compile one with logging on and one...

usually one listens on "0.0.0.0" which means all interfaces. though i guess it wouldn't be hard to modify bind option to take a delimited list of addresses to listen on

> Listening to 0.0.0.0 seems not work . that's a bit vague. can you show strace log of starting microsocks with -i 0.0.0.0 including one try to connect to it...