scan - Actually start a scan based on predefined workflow¶
# Practical Scan Usage:## Start a simple scan with default 'general' flow
osmedeus scan -t sample.com
## Start a scan directly with a module with inputs as a list of http domains like this https://sub.example.com
osmedeus scan -m ~/osmedeus-base/workflow/direct-module/dirbscan.yaml -t http-file.txt
## Start a general scan but exclude some of the modules
osmedeus scan -t sample.com -x screenshot -x spider
## Start a simple scan with other flow
osmedeus scan -f vuln -t sample.com
## Scan for CIDR with file contains CIDR with the format '1.2.3.4/24'
osmedeus scan -f cidr -t list-of-cidrs.txt
osmedeus scan -f cidr -t '1.2.3.4/24'# this will auto convert the single input to the file and run## Directly run the vuln scan and directory scan on list of domains
osmedeus scan -f vuln-and-dirb -t list-of-domains.txt
## Directly run the general but without subdomain enumeration scan on list of domains
osmedeus scan -f domains -t list-of-domains.txt
## Use a custom wordlist
osmedeus scan -t sample.com -p 'wordlists={{Data}}/wordlists/content/big.txt' -p 'fthreads=40'## Scan list of targets
osmedeus scan -T list_of_targets.txt
## Get target from a stdin and start the scan with 2 concurrency
cat list_of_targets.txt | osmedeus scan -c 2
queue - Running the scan with input from queue file¶
