Incorporate Honeyd for multiple honeypots on the same instance #1019
Replies: 2 comments 2 replies
-
Thanks for the idea (updated your link, though). While HoneyD might still be a great honeypot and checking all the boxes its project has been abandoned. Neither the issues, nor the PRs are being actively managed, not to mention its codebase. So, when we started with T-Pot back in 2015 we already decided against HoneyD for the mentioned reasons. Ever since we have deprecated honeypots that are not actively maintained. I.E. for T-Pot 22.03 all Py2 based honeypots using deprecated Py2 modules via PyPi have already been removed and have been replaced with new honeypots. This is part of our due diligence. Thanks again and sorry, but no, we will not incorporate HoneyD. |
Beta Was this translation helpful? Give feedback.
-
See the functionality, not the implementation, of HoneyD. This would allow users to intermix real servers with numerous honeypots. |
Beta Was this translation helpful? Give feedback.
-
While honeyd is dated, it still works and allows for multiple honeypots on the same instance via configuration. https://github.com/DataSoft/Honeyd. Additionally, it allows for additional low interaction services via python scripting. To connect an attacker to T-Pot's existing individualized honeypots simply proxy the connection.
This would allow users to intermix real servers with numerous honeypots.
Beta Was this translation helpful? Give feedback.
All reactions