rofl0r / rofl0r/proxychains-ng
proxychains Set multi-level agen,tor as a proxyheader has problems
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 10.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
socks5 127.0.0.1 9050 # Even the socks port of Tor on the public web cannot be replaced here
socks5 PROXY2 1080
socks5 PROXY3 1080
I use proxychains -f /etc/Torproxylist.conf curl ident.me, happen "socket error or timeout".
But it doesn't matter if I use any of the proxies in the proxy chain alone, or if I comment out Tor's proxies, the rest of the proxies can still form the proxy chain
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported proxychains command with the three-entry configuration, then trace the proxy-chain handling and SOCKS/Tor interaction in the C sources. Done means the listed chain works when Tor is included, while the existing behavior for individual proxies remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100