Unattended install¶
Every installer question has a flag. --yes accepts the defaults, and --dry-run shows every step and command without
changing anything. The full list of options is in the Installer reference.
Manager¶
Management on eth0, one decoy on each of eth1, eth2 and eth3:
sudo ./install.sh manager --yes --mgmt-if eth0 \
--domain corp.example.com --profile it \
--roles windows-file-server,windows-domain-controller,linux-web-hosting \
--names windows-file-server=RS-FS-01,windows-domain-controller=RS-DC-01,linux-web-hosting=RS-WEB-01 \
--role-ifaces windows-file-server=eth1,windows-domain-controller=eth2,linux-web-hosting=eth3 \
--web-theme helpdesk --public-ip no --geoip yes --allow-ssh 10.8.0.0/24
The decoy shares the management address, so all three admin allow-lists are required. Bait documents then report
only from 10.8.0.0/24, the web UI list; the installer warns about it.
Remote sensor¶
Manager link on eth0, decoy on eth1's own IP:
Rules for --yes¶
--yes uses the default of every question only if it is valid, and stops with a message naming the flag otherwise:
--domainis required (there is no default domain);- more roles than usable interfaces, or more than 3, is an error;
--role-ifacesmust give each decoy a different interface;- sensor: when the decoy is on the interface that reaches the manager,
--allow-sshis required; - when a decoy is on the management interface,
--allow-ui,--allow-sensorand--allow-sshare required, and if other host services listen on that interface,--close-other-servicesis required (the error lists them); - ports held by host services need
--stop-conflicting; - uid 10001 must be free on the host;
--no-ssh-movetogether with a decoy on the management interface is an error.