rofl0r

the networks you're trying to connect to are in the private ranges, so you may need localnet directives for them

it's a difficult problem. at the point the config is parsed, these messages were already printed. i'd have to implement some sort of caching (involves memory allocation) and postpone printing...

proxychains' approach has well-known limitations. there's a lot of reasons why chrom* can fail, on the top of the list is sandboxing mechanisms. tbh i'm surprised that wine works through...

sudo command most likely doesnt work correctly with proxychains. it's a setuid binary and glibc dynlinker restricts its use with LD_PRELOAD. try first `sudo bash` then in the new shell...

yes? if you want to get free support, maybe you should at least provide some details.

is your proxy configured to support ipv6 ?

> If different instances of proxychains get the same result from time() or clock_gettime() that problem was observed with the use of time() (one-second granularity), but it's been resolved by...

proxychains works with applications that - use libc - are dynamically linked - are not sandboxed - don't clear environment variables if all of those are given, it should work...

i'm aware about TOCTTOU and its implications, but i figure the chances of proxychains.conf disappearing between the check and the usage are too small to be relevant. in all the...

`__USE_GNU` is an internal macro, most likely set by features.h when `_GNU_SOURCE` or similar is used. the latter is the macro supposed to be used by the application.