4 ms·
If I have public key authentication set up for ssh, should I even bother with fail2ban, firewalld-rest, port knocking, etc.? There's no way anyone is brute forc
by oehtXRwMkIs 6y ago
If I have public key authentication set up for ssh, should I even bother with fail2ban, firewalld-rest, port knocking, etc.? There's no way anyone is brute forcing my ed25519 key, so what's the point? Sure security should be layered and all that but it seems like public key auth is so strong by itself anything on top seems unnecessary.
- avtar 6y ago> If I have public key authentication set up for ssh, should I even bother with fail2ban If someone's bruteforcing their way in via ssh it's probably worthwhile blocking them before they start trying other services.
- jooize 6y agoMight protect against some ludicrous attack that we're not considering. Limiting attempts seems to me to always be a good idea.
- RL_Quine 6y agoThere's no point to this at all, it's just making services more fragile. If "brute force" attacks are a concern, you are a fool that has password authentication turned on. If you have password authentication turned off, why does it matter?
- calvinmorrison 6y agoGiven some other attacks to ssh over the years, isn't it safer to use fail2ban
- fmajid 6y agoIt's very easy for brute-force attacks from botnets to consume all your SSH process slots and then you are locked out.
- yearoflinux 6y agoYou are reducing attack vectors. How do you know your ssh implementation is secure?
- jschwartzi 6y agoHow can you find out if you only get three tries a month?