webster Posted March 29, 2013 Share Posted March 29, 2013 DNmap is a framework to distribute nmap scans among several clients. It reads an already created file with nmap commands and send those commands to each client connected to it. The framework use a client/server architecture. The server knows what to do and the clients do it. All the logic and statistics are managed in the server. Nmap output is stored on both server and client. Usually you would want this if you have to scan a large group of hosts and you have several different internet connections (or friends that want to help you). Connection topology This is the hidden content, please Sign In or Sign Up Features of the framework Clients can be run on any computer on Internet. Do not have to be on a local cluster or anything. It uses the TLS protocol for encryption. Dnmap server features If the server gets down, clients continue trying to connect until the server gets back online. If the server gets down, when you put it up again it will send commands starting from the last command given before the shutdown. You do not need to remember where it was. You can add new commands to the original file without having to stop the server. The server will read them automatically. If some client goes down, the server will remember which command it was executing and it will re-schedule it for later. It will store every detail of the operations in a log file. It shows real time statistics about the operation of each client, including: Number of commands executed Last time seen Uptime Version of the client If the client is being run as root or not. It calculates the amount of commands executed per minute The historic average of the amount of commands executed per minute The status of the client (Online, Offline, Executing or Storing) [*]You can choose which port to use. Defaults to 46001 [*]Only the Online clients are shown in the running stats. Dnmap client features If the server gets down, it keeps connecting to it until it gets up again. Strip strange characters from the command sent by the server. Tries to avoid command injection vulns. It only executes the nmap command. It deletes the command send by the server and changes it by the known and trusted nmap binary on the system. You can select an alias for your user. You can change which port the client connects to. If the command sent by the server does not have a -oA option, the client add it anyway to the command, so it will always have a local copy of the output. For more information about DNmap please check the following links: This is the hidden content, please Sign In or Sign Up Link to comment Share on other sites More sharing options...
Recommended Posts