DEBUG: (boolean) Enable more verbose output to the console.The following options are supported in the /etc/default/dionaea files:

# files which can influence the attractiveness of the honeypot. These directories can include custom dionaea.cfg and service configurations # A specific 'personality' directory for the dionaea honeypot may be specified SERVICES=(blackhole epmap ftp http memcache mirror mongo mqtt pptp sip smb tftp upnp) # blackhole, epmap, ftp, http, memcache, mirror, mongo, mqtt, mssql, mysql, pptp, sip, smb, tftp, upnp # Leaving this blank will default to the docker container IP The following is an example env file: # This can be modified to change the default setup of the unattended installation Prior to starting, Dionaea will parse options passed to the container via the env_file specification in the docker-compose file. Please note that while Dionaea will run without the NET_ADMIN capability set, it will consume 100% of a CPU and notįunction optimally. Example dionaea docker-compose.yml version: '3' While they may serve as a basisįor users with advanced deployment needs, most users should default to theĬonfiguration files provided by the deployment scripts in the CHN web interface. To help you understand the various options. The env files, as well as the docker-compose.yml files below are intended Please see your system documentation for adding a user to the docker group. Please ensure the user on the system installing the honeypot is in the local The default deployment model uses Docker and Docker Compose to deploy containers for the project's tools, and so, require the following: 'Dionaea's intention is to trap malware exploiting vulnerabilities exposed by services offerd to a network, the ultimate goal is gaining a copy of the malware.' Prerequisites The CommunityHoneyNetwork dionaea honeypot is an implementation of Dionaea, configured to report logged attacks to the CommunityHoneyNetwork management server.

Docker ip address yml