Endlessh is an SSH tarpit that very slowly sends an endless, random SSH banner. It keeps SSH clients locked up for hours or even days at a time. The purpose is to put your real SSH server on another port and then let the script kiddies get stuck in this tarpit instead of bothering a real server.
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/endlessh:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The app listens on the port mapped for ssh connections. To log to file, set the environment variable LOGFILE to true and map a volume for /config. The logs will be under /config/logs/endlessh.
Endlessh is an SSH tarpit that very slowly sends an endless, random SSH banner. It keeps SSH clients locked up for hours or even days at a time. The purpose is to put your real SSH server on another port and then let the script kiddies get stuck in this tarpit instead of bothering a real server.
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/endlessh:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The app listens on the port mapped for ssh connections. To log to file, set the environment variable LOGFILE to true and map a volume for /config. The logs will be under /config/logs/endlessh.
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
You can also remove the old dangling images:
dockerimageprune
-
Via Watchtower auto-updater (only use if you don't remember the original parameters)¶
Pull the latest image at its tag and replace it with the same env variables in one run:
You can also remove the old dangling images: docker image prune
Warning
We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.
12.06.23: - Rebase to Alpine 3.18, deprecate armhf.
05.03.23: - Rebase to Alpine 3.17.
23.09.22: - Migrate to s6v3.
20.07.22: - Rebase to Alpine 3.16.
16.04.22: - Rebase to Alpine 3.15.
07.10.21: - Fix typo on MAXLINES var.
08.06.21: - Add BINDFAMILY option.
16.04.21: - Initial Release.
\ No newline at end of file
diff --git a/images/docker-series-troxide/index.html b/images/docker-series-troxide/index.html
index 43b675cc14..504e73501b 100644
--- a/images/docker-series-troxide/index.html
+++ b/images/docker-series-troxide/index.html
@@ -53,4 +53,4 @@
--pull\-tlscr.io/linuxserver/series-troxide:latest.
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static