thanwer/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Minor fixes.

Browse Source
This commit is contained in:
Thanwer 2024-10-26 21:45:30 -03:00
parent 06019f657c
commit 3e4b180492
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/posts/ssh-hardening.md
View File

@ -9,7 +9,7 @@ tags = [
]
+++
As you could see on my last post about [fail2ban]({{< ref "/posts/fail2ban-basics" >}} "Fail2ban basics"), the SSH services are a popular target for brute force attacks, we really should take our time to improve our server's security.
As you could see on my last post about [fail2ban]({{< ref "/posts/fail2ban-basics" >}} "Fail2ban basics"), the SSH service is a popular target for brute force attacks, we really should take our time to improve our server's security.
On top of iptables rules and fail2ban jails, we have a couple parameters that we can fine-tune on our servers to make another layer of protection.
@ -36,7 +36,7 @@ If you would like to have yet another level of security, you can implement [2FA
### Disable unnused authentication methods
By default, OpenSSH server comes with more authentication methods that you problaly are not using enabled by default. You acn disable them to reduce the attack surface of your server:
By default, OpenSSH server comes with more authentication methods that you problaly are not using enabled by default. You can disable them to reduce the attack surface of your server:
```bash
ChallengeResponseAuthentication no