The Wayback Machine - https://web.archive.org/web/20200918150504/https://github.com/topics/port-scanner
Skip to content
#

port-scanner

Here are 147 public repositories matching this topic...

mzfr
mzfr commented Jun 15, 2019

Currently pressing ctrl+c while scans are going on we get a big traceback.
It would be nice if we can handle that traceback and print something nice like Canceled by the user or something similar.

Read this to understand how to do it properly.

DDOS Tool: To take down small websites with HTTP FLOOD. Port scanner: To know the open ports of a site. FTP Password Cracker: To hack file system of websites.. Banner Grabber: To get the service or software running on a port. (After knowing the software running google for its vulnerabilities.) Web Spider: For gathering web application hacking information. Email scraper: To get all emails related to a webpage IMDB Rating: Easy way to access the movie database. Both .exe(compressed as zip) and .py versions are available in files.

  • Updated Sep 8, 2020
  • Python
cbrutekrag
metadone666
metadone666 commented Oct 15, 2019

Hello !
A Fake Process will be awesome.
This is an example of a fake process command line :

trcpy(argv[0],FAKE); // fake the proccess name.
while(fgets(buff,sizeof(buff),fp))
{
c=strchr(buff,'n');
if(c!=NULL) *c='.';
if (!(fork()))
{
where=0;
// printf("--> attacking %s",buff);
for (i=0; i<count; i=i+2){
// printf("--> Trying %s:%s %sn",a[i],a[i+1],buff);
checkauth(a[i],a[i+1],buff

devmaximilian
devmaximilian commented Nov 3, 2019

Would it be possible to add support for excluding specific ports? I'm thinking this could be an additional argument passed to the script (a comma-delimited list of ports).

An example call could look like the following:

portforge.cr localhost 4440 4445 4442,4443

This would exclude ports 4442 and 4443.

The reasoning behind my feature request is that I might want to run a web server on

This tool aims at automating the identification of potential service running behind ports identified manually either through manual scan or services running locally. The tool is useful when nmap or any scanning tool is not available and in the situation during which you did a manual port scanning and then want to identify the services running behind the identified ports.

  • Updated Nov 19, 2019
  • Shell

Improve this page

Add a description, image, and links to the port-scanner topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the port-scanner topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.