If like me, you enjoy the simplicity of UFW (Uncomplicated Firewall) on your Ubuntu servers be careful when you turn it on. UFW doesnâ€™t have any default rules to allow ssh inbound by default, if you arenâ€™t careful when turning it on you could find yourself locked out, and if you donâ€™t have direct console access to the server that could mean being locked out forever! Not a conversation you want to have with a client, or your boss,â€¦ or tech support at your friendly cloud provider.
So before turning UFW on for the first time here are couple quick tips.
The easy way
Build your allow rule first.
sudo ufw allow 22/tcp sudo ufw show added
Only then after seeing the output which confirms the rule is added, should you turn on ufw.
sudo ufw enable
The less easy way â€“ edit the file directly
Why would you want to use the less easy way!? Well, you may have need to copy this file over to a newly built server. Maybe because you like to know where configuration files hide. Or maybe just because you like to do thingsÂ a different way. Anyway whatever your reasons may be here you go.
Edit the user.rules file at /lib/ufw
sudo vim /lib/ufw/user.rules
Add the following lines directly under the section that says RULES
### RULES ### ### tuple ### allow tcp 22 0.0.0.0/0 any 0.0.0.0/0 in -A ufw-user-input -p tcp --dport 22 -j ACCEPT
Iâ€™d like to say that I didnâ€™t learn this the hard way but alas I seem to have locked myself out one too many times!
Be careful with the â€œeasyâ€ tools. They will bite you if you arenâ€™t paying close attention!
Luke has an RHCSA for Red Hat Enterpirse Linux 7 and currently works as a Linux Systems Adminstrator in Ohio.
This post, re-published here with permission, wasÂ originally published on Luke’s site here.
Leave a Reply