Endlessh vs Heralding
Endlessh
github.comHeralding
github.comSide by side
| Figure | Endlessh | Heralding |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Linux | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Honeypot Software | 7.7 (#7) | 7.5 (#12) |
| License | The repository identifies its license as the Unlicense. | GitHub identifies the project as GPL-3.0 licensed. |
| Purpose | Endlessh slowly sends an endless, random SSH banner to keep SSH clients occupied for hours or days. | Heralding is a simple honeypot that collects credentials. |
Plans
In their own words
Endlessh
Endlessh is a free, self-hosted SSH tarpit for Linux. It slowly sends random SSH banner text without ending, keeping unwanted SSH clients occupied for long periods. The project describes placing a real SSH server on another port so clients that connect to the tarpit remain there instead. Endlessh is a standalone, single-threaded C program that uses poll() to handle multiple clients. Because it sends the banner before cryptographic exchange, it does not rely on cryptographic libraries. Defaults include a 10000-millisecond interval between messages, a maximum banner line length of 32 characters, and a maximum of 4096 clients; excess connections wait in the queue. It supports IPv4 and IPv6, with options to bind to either address family alone. Diagnostics are quiet by default, with repeatable verbosity flags for standard and debug logging, plus syslog support. The configuration syntax is similar to OpenSSH and defaults to /etc/endlessh/config. The repository identifies the license as the Unlicense and provides GitHub Issues and Pull Requests for discussion and contributions.
Heralding
Heralding is a free, self-hosted network honeypot that collects credentials. It runs on Linux and supports FTP, Telnet, SSH, HTTP, HTTPS, POP3, POP3S, IMAP, IMAPS, SMTP, VNC, PostgreSQL and SOCKS5. When a protocol makes them available, its authentication log records usernames and plaintext passwords. It also writes authentication attempts, session summaries and full session data to CSV and JSON Lines files. Session details can include timestamps, duration, source and destination IP addresses and ports, protocol, authentication attempts and protocol-specific auxiliary data. Session log entries are written after sessions end; authentication entries appear once a password has been transmitted. The README describes pip installation on Debian-based systems and Docker deployment using port mapping. Python 3.7.0 or higher is required. For separate packet captures per session, the README points to Curisoum and says it must be enabled in Heralding.yml. GitHub identifies the project as GPL-3.0 licensed.