From 7b6cf882a657c9b75c35821a5fb86fee616d58f7 Mon Sep 17 00:00:00 2001 From: fzorb Date: Fri, 3 Jan 2025 13:52:24 +0200 Subject: [PATCH] Update content/posts/honeypot.md --- content/posts/honeypot.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/posts/honeypot.md b/content/posts/honeypot.md index 23edf2f..497a4eb 100644 --- a/content/posts/honeypot.md +++ b/content/posts/honeypot.md @@ -1,7 +1,7 @@ +++ title = 'Running an SSH honeypot to troll skids' date = 2025-01-03T11:10:19+02:00 -draft = true +draft = false +++ If you've ever looked at a public server's SSH logs, you would have probably found tens of failed connections from IP addresses you are not associated with. Those are bots that are trying to bruteforce their way into your Linux bots. An easy way you can change this is by changing the SSH port, but that's just lame. What you should do is do a *little bit of trolling*. So today, we'll be configuring `sshesame` to listen on port 22 and some other common ssh ports. @@ -83,4 +83,8 @@ WantedBy=multi-user.target ```sh systemctl daemon-reload systemctl enable --now sshesame -``` \ No newline at end of file +``` + +And now you can have skids waste their time hacking your box. Yay! + +P.S. Happy 2025 \ No newline at end of file