From 19f0a243737d2dedab8b402e2c4519838d9fd6d0 Mon Sep 17 00:00:00 2001 From: Christian Cleberg Date: Mon, 8 Jul 2024 21:30:26 -0500 Subject: fix images for 2022 posts --- content/blog/2022-03-24-server-hardening.md | 7 ------- 1 file changed, 7 deletions(-) (limited to 'content/blog/2022-03-24-server-hardening.md') diff --git a/content/blog/2022-03-24-server-hardening.md b/content/blog/2022-03-24-server-hardening.md index 83168e4..ffe01d4 100644 --- a/content/blog/2022-03-24-server-hardening.md +++ b/content/blog/2022-03-24-server-hardening.md @@ -131,8 +131,6 @@ sudo ufw allow 22 sudo ufw enable ``` -![ufw](https://img.cleberg.net/blog/20220324-hardening-a-public-facing-home-server/ufw.png) - ## `ssh` 1. Using SSH Keys @@ -202,9 +200,6 @@ sudo ufw enable MFA for `ssh`, see my other post: [Enabling MFA for SSH](../enable-totp-mfa-for-ssh/). - ![SSH -MFA](https://img.cleberg.net/blog/20220324-hardening-a-public-facing-home-server/ssh_mfa.png) - ## `fail2ban` I haven't written a post on how I use `fail2ban`, but it's quite simple. I use @@ -223,8 +218,6 @@ sudo fail2ban-client status sshd This should be used as a last-resort defense and shouldn't be a replacement for the security measures mentioned above. -![fail2ban](https://img.cleberg.net/blog/20220324-hardening-a-public-facing-home-server/fail2ban.png) - # Switch Between the router and any local devices is my managed switch, which is used to -- cgit v1.2.3-70-g09d2