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

24
docker/dionaea/README.md
View File

@ -1,29 +1,15 @@
# dockerized dionaea
[![](https://images.microbadger.com/badges/version/dtagdevsec/dionaea:1710.svg)](https://microbadger.com/images/dtagdevsec/dionaea:1710 "Get your own version badge on microbadger.com") [![](https://images.microbadger.com/badges/image/dtagdevsec/dionaea:1710.svg)](https://microbadger.com/images/dtagdevsec/dionaea:1710 "Get your own image badge on microbadger.com")
# dionaea
[dionaea](https://github.com/DinoTools/dionaea) is a low interaction honeypot with focus on capturing malware.
This repository contains the necessary files to create a *dockerized* version of dionaea.
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 dionaea and will be used to setup the docker image.
The `Dockerfile` contains the blueprint for the dockerized dionaea and will be used to setup the docker image.
The `dionaea.conf` is tailored to fit the T-Pot environment.
The `supervisord.conf` is used to start dionaea under supervision of supervisord.
Using systemd, copy the `systemd/dionaea.service` to `/etc/systemd/system/dionaea.service` and start using
```
systemctl enable dionaea
systemctl start dionaea
```
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/dionaea/` 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 dionaea using `docker-compose`. This will ensure to start the docker container with the appropriate permissions and port mappings.
# Dionaea Dashboard
![Dionaea Dashboard](https://raw.githubusercontent.com/dtag-dev-sec/dionaea/master/doc/dashboard.png)
![Dionaea Dashboard](https://raw.githubusercontent.com/dtag-dev-sec/tpotce/master/docker/dionaea/doc/dashboard.png)

BIN
docker/dionaea/doc/dashboard.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 621 KiB

After

Width:  |  Height:  |  Size: 418 KiB

2
docker/dionaea/docker-compose.yml
View File

@ -34,7 +34,7 @@ services:
- "5060:5060/udp"
- "5061:5061"
- "27017:27017"
image: "dtagdevsec/dionaea:1706"
image: "dtagdevsec/dionaea:1710"
volumes:
- /data/dionaea/roots/ftp:/opt/dionaea/var/dionaea/roots/ftp
- /data/dionaea/roots/tftp:/opt/dionaea/var/dionaea/roots/tftp