From de8c29591b1288fb1931e4f756f1de63009d6295 Mon Sep 17 00:00:00 2001
From: mic0 <mic0@mic0.dev>
Date: Tue, 18 Nov 2025 14:49:09 +0100
Subject: [PATCH] Some pronounced warning

---
 setup.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/setup.md b/setup.md
index 6fe65ca..54e2fc2 100644
--- a/setup.md
+++ b/setup.md
@@ -34,6 +34,9 @@ firewall-cmd --add-service=ssh --permanent &&
 firewall-cmd --reload
 ```
 
+⚠️⚠️⚠️ `drop` zone will just drop all traffic if you dont configure it to use `public` zone like we show in [Firewall](firewall.md) section. If connections time out this is likely the reason. ⚠️⚠️⚠️
+
+
 ## Unattended upgrades
 
 ```sh
@@ -87,10 +90,11 @@ nvim .ssh/authorized_keys # paste relevant SSH public keys in here
 ```
 
 Try opening a new terminal and ssh-ing into `admin` user on the server, it should work.
-Be sure this is the case before you lock `root` account out.
 
 ### Locking the `root` account
 
+⚠️⚠️⚠️ Be sure you can SSH with another sudo enabled account like `admin` otherwise you WILL LOCK YOURSELF out of the machine. ⚠️⚠️⚠️
+
 Go back to `root` account now, otherwise you will need to `sudo` the commands below.
 The following commands will lock out the root by configuring `/etc/ssh/sshd_config` file.