Scannerl works on Debian/Ubuntu/Arch (but will probably work on other distributions as well). It uses a master/slave architecture where the master node will distribute the work (host(s) to fingerprint) to its slaves (local or remote). The entire deployment is transparent to the user.

Why use ScannerlWhen using conventional fingerprinting tools for large-scale analysis, security researchers will often hit two limitations: first, these tools are typically built for scanning comparatively few hosts at a time and are inappropriate for large ranges of IP addresses. Second, if large range of IP addresses protected by IPS devices are being fingerprinted, the probability of being blacklisted is higher what could lead to an incomplete set of information. Scannerl is designed to circumvent these limitations, not only by providing the ability to fingerprint multiple hosts simultaneously, but also by distributing the load across an arbitrary number of hosts. Scannerl also makes the distribution of these tasks completely transparent, which makes setup and maintenance of large-scale fingerprinting projects trivial; this allows to focus on the analyses rather than the herculean task of managing and distributing fingerprinting processes by hand. In addition to the speed factor, scannerl has been designed to allow to easily set up specific fingerprinting analyses in a few lines of code. Not only is the creation of a fingerprinting cluster easy to set up, but it can be tweaked by adding fine-tuned scans to your fingerprinting campaigns.It is the fastest tool to perform large scale fingerprinting campaigns.For more:

InstallationSee the different installation options under wiki installation pageTo install from source, first install Erlang (at least v.18) by choosing the right packaging for your platform: Erlang downloadsInstall the required packages:

Distributed setupTwo types of nodes are needed to perform a distributed scan:

Master node: this is where scannerl’s binary is run

Slave node(s): this is where scannerl will connect to distribute all its work

The master node needs to have scannerl installed and compiled while the slave node(s) only needs Erlang to be installed. The entire setup is transparent and done automatically by the master node.Requirements for a distributed scan:

TARGETS: -f <target> --target <target> target: a list of target separated by a comma. -F <path> --target-file <path> path: the path of the file containing one target per line. -d <domain> --domain <domain> domain: a list of domains separated by a comma. -D <path> --domain-file <path> path: the path of the file containing one domain per line.

NODES: -s <node> --slave <node> node: a list of node (hostnames not IPs) separated by a comma. -S <path> --slave-file <path> path: the path of the file containing one node per line. a node can also be supplied with a multiplier (<node>*<nb>).

Standalone usageScannerl can be used on the local host without any other host. However, it will still create a slave node on the same host it is run from. Therefore, the requirements described in Distributed setup must also be met.A quick way to do this is to make sure your host is able to resolve itself with

and create an SSH key (if not yet present) and add it to the authorized_keys (you need an SSH server running):

cat $HOME/.ssh/id_rsa.pub >> $HOME/.ssh/authorized_keys

The following example runs an HTTP banner grabing on google.com from localhost

./scannerl -m httpbg -d google.com

Distributed usageIn order to perform a distributed scan, one need to pre-setup the hosts that will be used by scannerl to distribute the work. See Distributed setup for more information.Scannerl expects a list of slaves to use (provided by the -s or -S switches).

./scannerl -m httpbg -d google.com -s host1,host2,host3

List available modulesScannerl will list the available modules (output modules as well as fingerprinting modules) with the -l switch:

Modules argumentsArguments can be provided to modules with a colon. For example for the file output module:

./scannerl -m httpbg -d google.com -o file:/tmp/result

Result formatThe result returned by scannerl to the output modules has the following form:

module, target, port, result

Where

module: the module used (Erlang atom)

target: IP or hostname (string or IPv4 address)

port: the port (integer)

result: see below

The result part is of the form:

status, type,Value

Where status, type is one of the following tuples:

ok, result: fingerprinting the target succeeded

error, up: fingerprinting didn’t succeed but the target responded

error, unknown: fingerprinting failed

Value is the returned value – it is either an atom or a list of element

Extending ScannerlScannerl has been designed and implemented with modularity in mind. It is easy to add new modules to it:

Fingerprinting module: to query a specific protocol or service. As an example, the fp_httpbg.erl module allows to retrieve the server entry in the HTTP response.

Output module: to output to a specific database/filesystem or output the result in a specific format. For example, the out_file.erl and out_stdout.erl modules allow respectively to output to a file or to stdout (default behavior if not specified).

To create new modules, simply follow the behavior (fp_module.erl for fingerprinting modules and out_behavior.erl for output module) and implement your modules.New modules can either be added at compile time or dynamically as an external file.See the wiki page for more.