Comment on How to harden against SSH brute-forcing?
Waryle@jlai.lu 1 week ago
You can look up for:
- Setting up max authentication attemps per connection -> slows up a lot brute force attack, if your password is strong enough, that’s already a big step to secure your server.
- Generate SSH Keys and disable password authentication -> do this only if you’re connecting through the same devices, because you won’t be able to connect from any device that has not being set up.
- Set up Crowdsec -> it’s a service which scans logs and will block access to any suspicious IPs. It also relies on a crowdsourced list of I.P.s that are identified as threat and will preventively block them
LlilL@lemm.ee 1 week ago
Is this an alternative/replacement to fail2ban or something you would use along with f2b?
CausticFlames@sopuli.xyz 1 week ago
You could technically still use it alongside f2b, but in my experience Crowd-Sec seems to do a better job and can do the same things.
LlilL@lemm.ee 1 week ago
Thank for that! You just turned a student onto a new tool to play with.