proudly announcing the proxychains 4.1 release, now with Mac OS X support
- completely threadsafe
- DNS lookup on proxy server for increased speed and TOR onion url compatibility
- many bugs fixed
grab a source tarball
here is the official git repo https://github.com/rofl0r/proxychains
(note that there is another fork by haad, which has most good things i coded, but also lots of bugs introduced by haad, so it is not recommended to use that one)
I you think that trolling is way to go, I 'm with you.
mirror url has changed to http://mirror.wzff.de/sabotage/tarballs/proxychains-4.1.tar.bz2
i'll leave the old link for a while but will remove it at some point.
What is the current status here? Are you both still maintaining your forks separately or were you able to resolve your differences? And is either of you likely to take over the project officially?
And since I'm asking questions, are there any plans to add PAC support and/or proxy auto-detection, e.g. via libproxy? And what about supporting static linking, and/or link-time binding to transparently permanently add proxy support to re-compilable applications which don't have it out of the box? At least on Unix-like systems this should be feasible, perhaps even without code changes to ProxyChains.
1) the debian maintainer Eugene V. Lyubimkin has proposed that https://github.com/rofl0r/proxychains shall be the official repo, because of its technical superiority
2) haad refused to collaborate
3) there are no plans to introduce a dependency to an external library.
as to static linking, this is impossible due to the way proxychains works: it uses dlsym to install hooks.
proxychains is intended to be used with existing dynamically-linked compiled binaries.
for an application that wants to use this functionality, it has to be written in a way that supports proxying, for example by using the rocksocks library i wrote:
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.