Skip to content

Configuration

Jump to bottom
AlgoSecureAdmin edited this page Jul 6, 2020 · 1 revision

Client/Worker connection to server

WORKER AND CLIENT

You will have to create the config file Pollenisator/config/client.cfg on each worker.

A sample is provided so you just have to copy it

cp config/clientSample.cfg config/client.cfg

It has 8 lines.

  • host: The server ip on which the mongo database and sftp is listening.

  • mongo_port: port on which the mongo database is open (27017 by default)

  • sftp_port: port on which the SFTP server is listening.

  • ssl: True or False, activate ssl on all communications with the mongo database. The certificates must be present in the Pollenisator/ssl/ directory if this option is True.

  • user: The mongo user which have the read/write access to your mongo database.

  • password: The password for the above user

  • sftp_user: the system user configured for sftp

  • sftp_password: the password setted for the sftp_user

Import default commands with pollenisator client

Some commands are provided in a gzip file. To import them, run the client, just go to your Pollenisator folder and run it :

$ cd ~/Pollenisator

$ python3 pollenisator.py

Fill the connection form.

Once connected, go to File -> Import Commands and select Pollenisator/exports/pollenisator_commands.gzip

Tools configuration (Workers and optional for client)

Each commands launched on a system will read files in the config/tools.d/ directory to find which binary to use and which plugin to run.

Each installed tool on a worker should be present in the config/tools.d/ directory. If you want to use tools locally from your pollenisator client, you also have to declare tools in this directory.

There is a default file in that directory which will always be read first. Then, each entry can be overloaded if another json file in this directory uses the same command name.

For each tool you have to set a name, a way to execute its binary and the plugin file's name. It uses the json format like "<Command name>": {"bin":"<Way to execute the command>", "plugin":"<Python plugin file name>"}

The plugin name must have the exact same name as the Python Class declared inside.

For exemple, the worker tools.d directory uses the default json file:

{
"Nmap.tcp": {"bin":"nmap", "plugin":"Nmap"},
"Nmap.top_udp": {"bin":"nmap", "plugin":"Nmap"},
"Nmap.bdd": {"bin":"nmap", "plugin":"Nmap"},
"Nmap.vpn": {"bin":"nmap", "plugin":"Nmap"},
"Nmap.supervision": {"bin":"nmap", "plugin":"Nmap"},
"Nmap.services": {"bin":"nmap", "plugin":"NmapServices"},
"Nmap.services.udp": {"bin":"nmap", "plugin":"NmapServices"},
"Nmap.services_scripts": {"bin":"nmap", "plugin":"Default"},
"Nmap.all.tcp": {"bin":"nmap", "plugin":"Nmap"},
"Nmap.ip.allTcp": {"bin":"nmap", "plugin":"Nmap"},
"Nmap.ip.udp": {"bin":"nmap", "plugin":"Nmap"},
"WhatWeb.http": {"bin":"whatweb", "plugin":"WhatWeb"},
"WhatWeb.https": {"bin":"whatweb", "plugin":"WhatWeb"},
"TestSSL": {"bin":"testssl.sh", "plugin":"TestSSL"},
"Nikto": {"bin":"nikto", "plugin":"Nikto"},
"digReverseLookUp": {"bin":"dig", "plugin":"DigReverseLookup"},
"pythonReverseLookUp": {"bin":"python", "plugin":"PythonReverseLookup"},
"Sublist3r": {"bin":"sublist3r.py", "plugin":"Sublist3r"},
"Dirsearch.http": {"bin":"dirsearch.py", "plugin":"Dirsearch"},
"Dirsearch.https": {"bin":"dirsearch.py", "plugin":"Dirsearch"},
"Knockpy": {"bin":"knockpy.py", "plugin":"Knockpy"},
"crtsh": {"bin":"crtsh.py", "plugin":"Crtsh"},
"ssh_scan": {"bin":"ssh_scan", "plugin":"SSHScan"},
"amap": { "bin":"amap", "plugin":"Default"},
"amap.udp": {"bin":"amap", "plugin":"Default"},
"headercollector.http": {"bin":"python2 /home/HeaderCollector/headercollector.py", "plugin":"HeaderCollector"},
"headercollector.https": {"bin":"python2 /home/HeaderCollector/headercollector.py", "plugin":"HeaderCollector"},
"http-methods": {"bin":"nmap", "plugin":"HttpMethods"},
"smbmap": {"bin":"smbmap.py", "plugin":"SmbMap"},
"smbmap_greybox": {"bin":"smbmap.py", "plugin":"SmbMap"},
"smb-enum-users": {"bin":"nmap", "plugin":"Default"},
"nmap-script-vuln": {"bin":"nmap","plugin":"Default"},
"enum4linux": {"bin":"enum4linux.pl", "plugin":"Default"},
"ftp-anon": {"bin":"nmap", "plugin":"Default"},
"Nmap.quick": {"bin":"nmap", "plugin":"Nmap"},
"ike-scan" : { "bin" : "ike-scan", "plugin":"Default"},
"Nmap.verify.tcp": {"bin":"nmap", "plugin":"Nmap"},
"Nmap.verify.udp": {"bin":"nmap", "plugin":"Nmap"},
"CME.recon": {"bin":"cme", "plugin":"CME"},
"CME.usecreds": {"bin":"cme", "plugin":"CME"},
"eternalblue": {"bin":"nmap", "plugin":"EternalBlue"},
"bluekeep": {"bin":"rdpscan", "plugin":"BlueKeep"},
"openrelay": {"bin":"nmap", "plugin":"Default"},
"searchsploit": {"bin":"searchsploit", "plugin":"SearchSploit"}
}

The "bin" argument will be placed at the beginning of each command corresponding to it's name. You have to ensure that the binary is launchable as it is written in this file. You may use a fullpath as in the headercollector.http example.

Home

Clone this wiki locally