telekom-security/tpotce
1
0
Fork 0
mirror of https://github.com/telekom-security/tpotce.git synced 2025-07-02 01:27:27 -04:00
Code Issues Packages Projects Releases Wiki Activity

Start cleaning up and update documentation

Browse Source
This commit is contained in:
Marco Ochse
2017-10-23 13:02:04 +02:00
parent 70f75d51ee
commit 46264774b3
76 changed files with 3126 additions and 18799 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
docker/cowrie/README.md
View File

@ -1,32 +1,15 @@
# dockerized cowrie
[![](https://images.microbadger.com/badges/version/dtagdevsec/cowrie:1710.svg)](https://microbadger.com/images/dtagdevsec/cowrie:1710 "Get your own version badge on microbadger.com") [![](https://images.microbadger.com/badges/image/dtagdevsec/cowrie:1710.svg)](https://microbadger.com/images/dtagdevsec/cowrie:1710 "Get your own image badge on microbadger.com")
# cowrie
[cowrie](http://www.micheloosterhof.com/cowrie/) is an extended fork of the medium interaction honeypot [kippo](https://github.com/desaster/kippo).
This repository contains the necessary files to create a *dockerized* version of cowrie.
This dockerized version is part of the **[T-Pot community honeypot](http://dtag-dev-sec.github.io/)** of Deutsche Telekom AG.
The `Dockerfile` contains the blueprint for the dockerized cowrie and will be used to setup the docker image.
The `cowrie.cfg` is tailored to fit the T-Pot environment.
The `setup.sql` is also tailored to fit the T-Pot environment.
The `supervisord.conf` is used to start cowrie under supervision of supervisord.
Using systemd, copy the `systemd/cowrie.service` to `/etc/systemd/system/cowrie.service` and start using
```
systemctl enable cowrie
systemctl start cowrie
```
This will make sure that the docker container is started with the appropriate permissions and port mappings. Further, it autostarts during boot.
By default all data will be stored in `/data/cowrie/` until the honeypot service will be restarted which is by default every 24 hours. If you want to keep data persistently simply edit the ``service`` file, find the line that contains ``clean.sh`` and set the option from ``off`` to ``on``. Be advised to establish some sort of log management if you wish to do so.
The `docker-compose.yml` contains the necessary settings to test cowrie using `docker-compose`. This will ensure to start the docker container with the appropriate permissions and port mappings.
# Cowrie Dashboard
![Cowrie Dashboard](https://raw.githubusercontent.com/dtag-dev-sec/cowrie/master/doc/dashboard.png)
![Cowrie Dashboard](https://raw.githubusercontent.com/dtag-dev-sec/tpotce/master/docker/cowrie/doc/dashboard.png)