rofl0r / rofl0r/proxychains-ng

proxychains does not work well with nmap

Open
#129 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
10.7k
Forks
1.1k
No merged PRs in 30d

Description

guys when i use proxychains to scan host without -A is can scan normal but with it it gonna get error.Need your help.
when i scan without -A:
[proxychains] config file found: /opt/proxychains/src/proxychains.conf
[proxychains] preloading /usr/local/lib/libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.11-git-5-ge527b9e

Starting Nmap 7.01 ( https://nmap.org ) at 2016-06-29 13:11 EDT
Nmap scan report for anhhungvieshare.com (173.236.74.12)
Host is up (0.20s latency).
rDNS record for 173.236.74.12: phx22.stablehost.com
Not shown: 955 filtered ports, 31 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
26/tcp open rsftp
80/tcp open http
82/tcp open xfer
110/tcp open pop3
143/tcp open imap
443/tcp open https
465/tcp open smtps
587/tcp open submission
993/tcp open imaps
995/tcp open pop3s
5666/tcp open nrpe

Nmap done: 1 IP address (1 host up) scanned in 10.70 seconds

And this is when i scan it with -A:
[proxychains] config file found: /opt/proxychains/src/proxychains.conf
[proxychains] preloading /usr/local/lib/libproxychains4.so
[proxychains] DLL init: proxychains-ng 4.11-git-5-ge527b9e

Starting Nmap 7.01 ( https://nmap.org ) at 2016-06-29 13:12 EDT
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:21 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:22 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:25 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:26 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:110 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:143 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:443 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:465 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:587 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:993 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:995 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:5666 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:8888 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:465 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:443 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:993 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:995 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:8888 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:25 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:8888 <--socket error or timeout!
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:25 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:25 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:80 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:993 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:143 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:995 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:82 ... OK
[proxychains] Strict chain ... 127.0.0.1:9050 ... 173.236.74.12:25 <--socket error or timeout!
Segmentation fault

And finnaly when i use proxychains with sparta to scan it the scan gonna crash.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source files or tests. Start by reproducing proxychains-ng with Nmap 7.01 using -A, then with Sparta, and compare the socket errors and segmentation fault; done means these scans no longer crash or fail in the reported way.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.