From 2de4ec0dc7646fab825efd66864d8a6f43dce9f1 Mon Sep 17 00:00:00 2001 From: Muhammad Nauman Raza Date: Thu, 4 Apr 2024 23:11:31 +0100 Subject: [PATCH] chore: fix typo --- blog/home_server_security.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/home_server_security.typ b/blog/home_server_security.typ index 8ac0fc4..1e74528 100644 --- a/blog/home_server_security.typ +++ b/blog/home_server_security.typ @@ -57,6 +57,6 @@ The fairly basic stuff you'd need to do in this case doesn't make much room for - This probably doesn't need to be said, but *use strong passwords*! - Host a #link("https://fail2ban.org")[fail2ban] instance to ban hosts making bruteforce attempts. -I think that's all there is for almost everyone, and is basically the minimal amount of effort a home server administrator should do. Personally, I would prefer to enforce a VPN connection in order to access my _personal_ services for that extra layer of security (because why'd they need to be exposed to the internet?). This can be done faily easily with tailscale, and for the slightly more paranoid - #link("https://headscale.net/")[headscale] is a viable...alternative? Anyways, I've got a blog post that explores headscale in a little more detail, which might be worth checking out. +I think that's all there is for almost everyone, and is basically the minimal amount of effort a home server administrator should do. Personally, I would prefer to enforce a VPN connection in order to access my _personal_ services for that extra layer of security (because why'd they need to be exposed to the internet?). This can be done fairly easily with tailscale, and for the slightly more paranoid - #link("https://headscale.net/")[headscale] is a viable...alternative? Anyways, I've got a blog post that explores headscale in a little more detail, which might be worth checking out. Well, that's all I wanted to say. It's been a while since my last blog post, and the inspiration for this one came seemingly randomly - I hope someone finds this useful.