mushorg / buttinsky Goto Github PK

Finish the gevent event manager to spawn greenlets for new networks

We need a way to validate a settings file according to the assigned protocol

Add a hpfeeds client subscribing to a channel which provides botnet settings.
We are probably using JSON for setting encoding.
Add a hpfeeds client publishing data to a channel. We can start with some basic logging information to get status updates from the monitoring bot.

Debugging will improve a lot if we can enable file logging to a static text file.

In spawner.py

Under import -->
import modules.reporting.file_logger as file_logger

Under load -->
log.info("Task ID:" + identifier + " is loaded successfully into queue from source file <" + filename + ">")

Under main-->
log = file_logger.FileLogger(name="buttinsky").log()
log.info('Starting Buttinsky spawner')

Pls suggest if this viable

Test if this is feasible at all. IIRC most P2P protocols used are customized.

Provide DNS transport layer for botnet communication

Using the generalized data we using machine learning and clustering to generate a bot behavior definition.

Use the bot behavior definition to mimic a real bot.

Start documentation. Sphinx combined with github pages seems like a good option.

Running buttinsky.py throws up the error given below:

Traceback (most recent call last):
File "./buttinsky.py", line 26, in
set_nick = "NICK %s\r\n" % net_settings["nick"]
File "/usr/lib/python2.7/dist-packages/configobj.py", line 567, in getitem
val = dict.getitem(self, key)
KeyError: 'nick'

Have a look into various bots using P2P protocols for communication. What do we need to have in place so one can replicated the communication?

Add a hpfeeds sink to get botnet credentials from various channels.

Move the spawner into a separate module so we can reuse it in e.g. the HPFeeds sink or an eventual web API

Start writing documentation on how to use the tool, adding new plugins etc.
Preferably using Sphinx-Doc.

Monitor a directory for new setting files defining a new network. If there is a new setting, spawn a new network monitoring session

Provide XMPP as communication transport layer

Provide a cli (probably based on Cmd) to add new networks on the fly. Maybe extend to be used to manage the monitored networks.

Provide the standard HTTP methods and parsers for requests, responses, header and payloads.

A report summarizing the last two months

Wrap the main of the spawner in a try/except and close the HPFeeds connection if it's there and the spawner gets stopped.

Add optional TOR support to the network layer

Deva has create a connection in the spawner to HPFeeds which we now have to pass to the monitor.
The connection has to be passed to the log layer on line https://github.com/buttinsky/buttinsky/blob/dev/spawner.py#L147

The IRC protocol is no rocket science so I'd write it from scratch and get more flexibility this way.
I added a basic starting point to the repository handling NICK, USER, JOIN and PING.
It would be cool if we could configure the communication protocols by providing protocol definitions in the botnet settings.

Only connect to HPFeeds in the spawner if it is enabled.
https://github.com/buttinsky/buttinsky/blob/dev/spawner.py#L257

Implement a filter for collected botnet communication to identify the commands purpose. This will build the basis for the bot behavior definer.

A report summarizing the first six months.

Provide a basic binary based protocol handler