Traceback appears, when trying to scan myself with nmap.
See original GitHub issueSteps to reproduce the problem:
- Run mitmproxy.
- Scan yourself with nmap:
nmap -sT localhost
Traceback:
System information
Mitmproxy: 3.0.0.dev0004 (commit 68c32d8) Python: 3.5.2 OpenSSL: OpenSSL 1.1.0g 2 Nov 2017 Platform: Linux-4.4.0-104-generic-x86_64-with-Ubuntu-16.04-xenial
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (2 by maintainers)
Top Results From Across the Web
Dealing with Misidentified and Unidentified Hosts
Run the command nmap -O -sV -T4 -d <target> , where <target> is the misidentified system in question. Look at the OS detection...
Read more >How can I scan open ports without being traced back
I would like to scan open ports of a server. But as far as I know, when I try to scan the open...
Read more >How to skip an IP when using Nmap in Python?
I am using nmap in python, and trying to scan the network using a text file. All the scan ranges are in a...
Read more >Writeup: Traceback on Hack The Box | by Frank Leitner
This scan comes back with just two open ports, 22 with OpenSSH listening and 80 with an Apache on the other side. nmap...
Read more >Receiving XML exception from nmap.scan() results.
Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/nmap/nmap.py", line 322, in analyse_nmap_xml_scan dom ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am working on it, give me some time yes I was wrong, let me modify my code little bit more
This is a race. Nmap connects to the socket, and immediately disconnects. We fire up the client connection thread, and attempt to retrieve the peer name from the connection. At this point the connection is closed, and we get OSError.