{"id":13437683,"url":"https://github.com/haad/proxychains","last_synced_at":"2025-05-14T10:10:40.161Z","repository":{"id":39097050,"uuid":"1410762","full_name":"haad/proxychains","owner":"haad","description":"proxychains - a tool that forces any TCP connection made by any given application to follow through proxy like TOR or any other SOCKS4, SOCKS5 or HTTP(S) proxy.  Supported auth-types: \"user/pass\" for SOCKS4/5, \"basic\" for HTTP.","archived":false,"fork":false,"pushed_at":"2024-06-08T02:20:54.000Z","size":538,"stargazers_count":7106,"open_issues_count":24,"forks_count":646,"subscribers_count":144,"default_branch":"master","last_synced_at":"2025-04-09T03:09:33.136Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"http://proxychains.sourceforge.net/","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/haad.png","metadata":{"files":{"readme":"README.md","changelog":"ChangeLog","contributing":null,"funding":null,"license":"COPYING","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS","dei":null,"publiccode":null,"codemeta":null}},"created_at":"2011-02-25T12:27:05.000Z","updated_at":"2025-04-08T12:21:34.000Z","dependencies_parsed_at":"2023-02-02T18:45:53.115Z","dependency_job_id":"65ab61c2-67d5-4ccc-b498-473528fc8730","html_url":"https://github.com/haad/proxychains","commit_stats":null,"previous_names":[],"tags_count":6,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/haad%2Fproxychains","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/haad%2Fproxychains/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/haad%2Fproxychains/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/haad%2Fproxychains/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/haad","download_url":"https://codeload.github.com/haad/proxychains/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254120170,"owners_count":22017953,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-07-31T03:00:59.282Z","updated_at":"2025-05-14T10:10:40.112Z","avatar_url":"https://github.com/haad.png","language":"C","readme":"# ProxyChains ver. 4.3.0 README\n\n![build-badge](https://github.com/haad/proxychains/actions/workflows/buildci.yml/badge.svg)\n\n\nProxyChains is a UNIX program, that hooks network-related libc functions\nin dynamically linked programs via a preloaded DLL and redirects the\nconnections through SOCKS4a/5 or HTTP proxies.\n\nWARNING: this program works only on dynamically linked programs.\nalso both proxychains and the program to call must use\nthe same dynamic linker (i.e. same libc)\n\n## Known limitations of the current version\n\nwhen a process forks, does a DNS lookup in the child, and then uses\nthe ip in the parent, the corresponding ip mapping will not be found,\nthis is because the fork can't write back into the parents mapping table.\nIRSSI shows this behavior, so you have to pass the resolved ip address\nto it. (you can use the proxyresolv script (requires \"dig\") to do so)\n\nthis means that you can't currently use tor onion urls for irssi.\nto solve this issue, an external data store (file, pipe, ...) has to\nmanage the dns \u003c-\u003e ip mapping. of course there has to be proper locking.\nshm_open, mkstemp, are possible candidates for a file based approach,\nthe other option is to spawn some kind of server process that manages the\nmap lookups. since connect() etc are hooked, this must not be a TCP server.\n\nI am reluctant on doing this change, because the described behavior\nseems pretty idiotic (doing a fork only for a DNS lookup), and irssi\nis currently the only known affected program.\n\n## Installation\n\n### Using release version\n\n*Proxychains-4.3.0* are available with pkgsrc to everyone using it on _Linux_,\n_NetBSD_, _FreeBSD_, _OpenBSD_, _DragonFlyBSD_ or _Mac OS X_. You just need to install\npkgsrc-wip repository and run\n  make install\nin a wip/proxychains directory.\n\nYou can find out more about pkgsrc on link:http://www.pkgsrc.org[pkgsrc] and about pkgsrc-wip on\nlink:https://pkgsrc.org/wip[Pkgsrc-wip homepage]\n\n### Installing on Mac OS X with homebrew\n\nYou can install current proxychains on Mac OS X with an homebrew. You have to\ndownload unofficial link:https://gist.github.com/3792521[homebrew formula] from\nto your BREW_HOME by default /usr/local/Library/Formula/ and run\n\n```\n$ brew install proxychains\n```\n\n### Running Current Source code version\n\n```\n# needs a working C compiler, preferably gcc\n./configure\nmake\nsudo make install\n```\n\n## Changelog\n\n*Version (4.x)* removes the dnsresolver script which required a dynamically\nlinked \"dig\" binary to be present with remote DNS lookup.\nthis speeds up any operation involving DNS, as the old script had to use TCP.\nadditionally it allows to use .onion urls when used with TOR.\nalso it removed the broken autoconf build system with a simple Makefile.\nthere's a ./configure script though for convenience.\nit also adds support for a config file passed via command line switches/\nenvironment variables.\n\n*Version (3.x)* introduces support for DNS resolving through proxy\nit supports SOCKS4, SOCKS5 and HTTP CONNECT proxy servers.\n\n* Auth-types\n ** socks - \"user/pass\",\n ** http - \"basic\"\n\n## When to use it\n\n* When the only way to get \"outside\" from your LAN is through proxy server.\n* To get out from behind restrictive firewall which filters outgoing ports.\n* To use two (or more) proxies in chain:\n\n```\n   like: your_host \u003c--\u003e proxy1 \u003c--\u003e proxy2 \u003c--\u003e target_host\n```\n\n* To \"proxify\" some program with no proxy support built-in (like telnet)\n* Access intranet from outside via proxy.\n* To use DNS behind proxy.\n\n### Some cool features\n\n* This program can mix different proxy types in the same chain\n\n```\n  like: your_host \u003c--\u003esocks5 \u003c--\u003e http \u003c--\u003e socks4 \u003c--\u003e target_host\n```\n\n* Different chaining options supported\n  random order from the list ( user defined length of chain ).\n  exact order  (as they appear in the list )\n  dynamic order (smart exclude dead proxies from chain)\n* You can use it with any TCP client application, even network scanners\n  yes, yes - you can make portscan via proxy (or chained proxies)\n  for example with Nmap scanner by fyodor (www.insecure.org/nmap).\n\n```\n  proxychains nmap -sT -PO -p 80 -iR  (find some webservers through proxy)\n```\n\n* You can use it with servers, like squid, sendmail, or whatever.\n* DNS resolving through proxy.\n\n## Configuration\n\nproxychains looks for configuration in the following order:\n\n* SOCKS5 proxy host ip and port in environment variable ${PROXYCHAINS_SOCKS5_HOST} ${PROXYCHAINS_SOCKS5_PORT}\n  (if ${PROXYCHAINS_SOCKS5_PORT} is set, no further configuration will be searched. if ${PROXYCHAINS_SOCKS5_HOST} isn't set, host ip will become \"127.0.0.1\")\n* file listed in environment variable ${PROXYCHAINS_CONF_FILE} or\n  provided as a -f argument to proxychains script or binary.\n* ./proxychains.conf\n* $(HOME)/.proxychains/proxychains.conf\n* /etc/proxychains.conf\n\nsee more in */etc/proxychains.conf*\n\n### Usage Example\n\n```\n$ proxychains4 telnet targethost.com\n```\n\nin this example it will run telnet through proxy(or chained proxies)\nspecified by *proxychains.conf*\n\n### Usage Example\n\n```\n$ proxychains4 -f /etc/proxychains-other.conf targethost2.com\n```\n\nin this example it will use different configuration file then *proxychains.conf*\nto connect to targethost2.com host.\n\n### Usage Example\n\n```\n$ proxyresolv targethost.com\n```\n\nin this example it will resolve targethost.com through proxy(or chained proxies)\nspecified by *proxychains.conf*\n\n### Usage Example:\n\n```\n$ ssh -fN -D 4321 some.example.com\n$ PROXYCHAINS_SOCKS5_HOST=127.0.0.1 PROXYCHAINS_SOCKS5_PORT=4321 proxychains zsh\n```\n\nin this example, it will run a shell with all traffic proxied through\nOpenSSH's \"dynamic proxy\" (SOCKS5 proxy) on localhost port 4321.\n\n### Usage Example:\n\n```\n$ export PROXY_DNS_SERVER=8.8.8.8\n$ proxychains4 telnet targethost.com\n```\n\nin this example, it will telnet to targethost.com using the 8.8.8.8\nnameserver supplied by the user through the PROXY_DNS_SERVER\n","funding_links":[],"categories":["C","\u003ca id=\"1a9934198e37d6d06b881705b863afc8\"\u003e\u003c/a\u003e通信\u0026\u0026代理\u0026\u0026反向代理\u0026\u0026隧道","Applications","[Visual Basic](#visual-basic)","\u003ca id=\"d03d494700077f6a65092985c06bf8e8\"\u003e\u003c/a\u003e工具","Networking","Specialized Tools"],"sub_categories":["\u003ca id=\"f932418b594acb6facfc35c1ec414188\"\u003e\u003c/a\u003eSocks\u0026\u0026ShadowSocksXx","Proxy","\u003ca id=\"160b0cdb52f30bdc3f222aa08c91d10d\"\u003e\u003c/a\u003eproxychains","Network Utilities"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fhaad%2Fproxychains","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fhaad%2Fproxychains","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fhaad%2Fproxychains/lists"}