kind of sick of the crazy number of bruteforce bots attacking certain well-known IP ranges... I think I'll just run honeypots and put SSH on port 1337 from now on instead lol
=> More informations about this toot | More toots from froge@social.glitched.systems
@froge@social.glitched.systems i moved ssh to another port because of all the traffic, somehow my fail2ban also sometimes shoot people requesting weird nginx urls from my server
=> More informations about this toot | More toots from Stellar@mk.absturztau.be
@Stellar@mk.absturztau.be yeah the web bots shooting random exploits at everything are also kinda funny, I see a lot of those on corporate AWS and google cloud IP ranges too
normally I would just put SSH behind a VPN, but some services are low risk for me and honestly not worth the effort... easier to move SSH and log everything the bots do in a honeypot for when I'm bored lol
=> More informations about this toot | More toots from froge@social.glitched.systems
@froge@social.glitched.systems i use only keys with my ssh, its safe right?
=> More informations about this toot | More toots from Stellar@mk.absturztau.be
@Stellar@mk.absturztau.be I meaaaannnnnnn
safe until SSH has another exploit :D
=> More informations about this toot | More toots from froge@social.glitched.systems
@froge@social.glitched.systems :aducknervous: oh no oh no
=> More informations about this toot | More toots from Stellar@mk.absturztau.be
@froge Guess why I literally have a repo with a table.of blocklists just to keep track of all the malicious networks and hosts...
=> More informations about this toot | More toots from kkarhan@infosec.space This content has been proxied by September (ba2dc).Proxy Information
text/gemini