Distributed Nmap Scanner.
The main goal of this project is to provide a wrapper around nmap, and distribute scans across several hosts.
PIP package published at
Install
% git clone https://github.com/0x4E0x650x6F/dscan.git
% cd dscan
% pip install .
% dscan
[*]\tDistribuited scan
usage: Distributed scanner [-h] --name NAME {srv,agent,config} ...
Distributed scanner: error: the following arguments are required: --name, cmd
Uninstall
% pip uninstall dscan
Generate self-sign certificate.
The following command generates a self sign certificate a private key, and two configuration files agent.conf and dscan.conf with default settings for the agent and for the server.
dscan --name <project-name> config -email mail@dscan.org -cn dscan \
-c pt -l earth -st nrw -o dscan -ou it -days 365
ls -a fubar
- agent.conf
- certfile.crt
- dscan.conf
- keyfile.key
Server output example
The following command starts the server, the --name is the name of the folder where the project files will be stored, this directory should contain the dscan.conf and the certificate private key generated from the previous command, the last argument is a existing file with a list of ip or networks to scan.
%dscan --name <project-name> srv --config dscan.conf targets.txt
Distributed Scan Status
========================
--------- ---------------- ------------
N Stages N Pending Tasks Completion %
--------- ---------------- ------------
4 0 0.00%
--------- ---------- ----------- ------------
Stage N Targets N Finished Completion %
--------- ---------- ----------- ------------
discovery 1 0 0.00%
--------------- --------- ----------- ------------
Agent Stage Task Status Target Ip
--------------- --------- ----------- ------------
127.0.0.1:53281 discovery DOWNLOADING 127.0.0.1/32
Agent output example
The following starts the agent, the --name is the name of the folder were the work files will be stores should contain a copy of the certificate, and the agent.conf file.
dscan --name <agent-project-name> agent --config <path-to-agent.conf> \
-s <server-ip-address> -p <server-port>
Distributed Scan Status
========================
------------ ------------------ ------
Target Nª completed Scans Status
------------ ------------------ ------
127.0.0.1/32 5 100
BTC: bc1qhzp6d5rtczyffwfaqxlca8cfqhc5m0xzarjy6ve8ujmxmgecmpeq08vppv
Metadata
Release files for dscan-4E656F 0.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dscan_4e656f-0.1.7.tar.gz | 46.1 kB | Without provenance | Details for dscan_4e656f-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dscan_4e656f-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for dscan_4e656f-0.1.7-py3-none-any.whl |
Total release size: 81.9 kB
Release files / dscan_4e656f-0.1.7.tar.gz
| Download URL | dscan_4e656f-0.1.7.tar.gz |
|---|---|
| Size | 46.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1207edcf71dcbbefcde483f542947da83cc2e666049051fcd046f9394d1ab55
|
|
BLAKE2b-256 checksum How to use checksums |
46509f638c6710069ba6f171d80a6820471b73f1d4f654fb88db0f0586e58d90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.5
|
Release files / dscan_4e656f-0.1.7-py3-none-any.whl
| Download URL | dscan_4e656f-0.1.7-py3-none-any.whl |
|---|---|
| Size | 35.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3eec3ae0152eb0f22ad669cd27cc225e821770082881f22d5aaec7ca80ce3fb6
|
|
BLAKE2b-256 checksum How to use checksums |
2814acce6021573774fc3f250e354dcdd7794c0cb19610d2f520dd7ddff6f451
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.5
|
Security for dscan-4E656F 0.1.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.