Seperate components like git about honeytrap HOT 2 CLOSED

Questions

1. For Honeytrap Server is this the base server we have running when lunching the honeytrap main.go file?

2. For Honeytrap CLI as to containers and attack information, are we already gathering this data and storing them internally?

• If it is based on the information from the event data received, do we have certain sensors that allow us capture specific types as attackers information or do we consider all sessions as attackers?

• Will honeytrap CLI be an interactive shell or will it just print out information has regards containers, attackers, sessions?

from honeytrap.

We wish to expose certain commands which allows us to retrieve specific information from running instance.

• honeytrap lxc ls
  This command will allow us detail existing running containers based on deployed provider, which will inform of running containers and attached IPs and data transmitted if possible.

• honeytrap lxc kill
  This command will allow us to abruptly stop a running container with our deployed server.

• honeytrap lxc rm
  This command will allow us to remove an existing container from all available created containers.

• honeytrap lxc create
  This command will allow us to create a container with an existing lxc containers.

from honeytrap.