rofl0r
you could run the dehydrated script with `proxychains4 bash -x /path/to/dehydrated` so we can see which exact command is failing. also please use latest git of proxychains, some issues have...
thanks, the isolated curl command seems to work fine here on both debian and sabotage linux hosts, with latest git and both socks5/http proxies. the issue you're facing could be...
please provide a pcap for the case that fails (using wireshark or tcpdump). > ... original proxychains repository ... that repo is not original at all, it's an unmaintained copy...
according to your previous log, your proxy runs on localhost. ``` [proxychains] Strict chain ... 127.0.0.1:3128 ``` so you already shared your IP address publicly, and it's the same everybody...
thanks. looks like your squid is configured to not allow CONNECT requests to standard HTTP ports...
theoretically one could add an option that makes it so that when the connect target is port 80, and the last proxy in the chain is a http proxy, the...
> Otherwise I could do it later please go ahead > does it mean that we could make a change in proxychains so it will work with the default squid...
that's a non-issue and i'm not interested in "fixing" it, because the fix is already here: https://github.com/rofl0r/proxychains-ng/issues/246#issuecomment-401019706 i guess this can be closed now, right ?
likely a bug of alpine. since proxychains is by default built with debug info it should be sufficient to rebuild alpine with debug info and then debug it as you...