fzorb/website
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update content/posts/honeypot.md
Some checks failed
pipeline / deploy-job (push) Failing after 2m38s
Details

Browse Source
This commit is contained in:
fzorb 2025-01-03 13:52:24 +02:00
parent 1abd583c77
commit 7b6cf882a6
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/posts/honeypot.md
View File

@ -1,7 +1,7 @@
+++ +++
title = 'Running an SSH honeypot to troll skids' title = 'Running an SSH honeypot to troll skids'
date = 2025-01-03T11:10:19+02:00 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. 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.
@ -84,3 +84,7 @@ WantedBy=multi-user.target
systemctl daemon-reload systemctl daemon-reload
systemctl enable --now sshesame systemctl enable --now sshesame
``` ```
And now you can have skids waste their time hacking your box. Yay!
P.S. Happy 2025