rofl0r / rofl0r/proxychains-ng
proxychains+nmap/telnet shows that all ports open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 10.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
When I use nmap or telnet with procxychains4, it seems that all ports open,just like this:
proxychains4 -q nmap -n 202...* | head
Starting Nmap 6.40 ( http://nmap.org ) at 2015-10-16 22:26 CST
Nmap scan report for 202...*
Host is up (0.00034s latency).
PORT STATE SERVICE
1/tcp open tcpmux
3/tcp open compressnet
4/tcp open unknown
6/tcp open unknown
7/tcp open echo
proxychains4 -q telnet 202...* 7777
Trying 202......
Connected to 202....
Escape character is '^]'.
Why do such things happen?
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
Reproduce the reported behavior with proxychains4, nmap, and telnet using the commands and proxy setup from the issue. Trace how proxied connection results are reported and determine why unreachable ports appear open; done means identifying the cause and confirming corrected port states with both commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100