Currently one can get their own IP and "shell" sessions recorded when testing the honeytarpot. Which is obviously not a good idea if one wants to use the recorded host IPs asa blacklist. Combined with the sync feature this could lead the unintended side effects.
An idea could be to introduce an IP whitelist section to the config, combined with safe credentials, similar to the sync feature itself. And then use that list in the addHost function (and other places) to prevent whitelisted IPs from being logged.
toxyl
commented
2 years ago
Currently one can get their own IP and "shell" sessions recorded when testing the honeytarpot. Which is obviously not a good idea if one wants to use the recorded host IPs asa blacklist. Combined with the sync feature this could lead the unintended side effects.
An idea could be to introduce an IP whitelist section to the config, combined with safe credentials, similar to the sync feature itself. And then use that list in the
addHostfunction (and other places) to prevent whitelisted IPs from being logged.