I'm mobile, but has this been updated? I used this in college back in 08 and it was much better than iptables but I don't know if it's kept up with the times.
FireHOL – Linux firewalling and traffic shaping for humans
21–24 of 24 posts
Re: FireHOL – Linux firewalling and traffic shaping for humans
#22We have a couple of servers we can’t move to the cloud for a variety of reasons. In addition, they are running some super legacy applications. Because of this, we’ve really had to focus on OS level security to protect the application (OS is surprisingly Ubuntu 16). Good Linux Security Software: - ModSecurity V3...tough to figure out but so worth it. An incredible L7 Firewall. Immediately provides benefits - UFW...utt…
Which headers are you talking about?
Re: FireHOL – Linux firewalling and traffic shaping for humans
#23We have a couple of servers we can’t move to the cloud for a variety of reasons. In addition, they are running some super legacy applications. Because of this, we’ve really had to focus on OS level security to protect the application (OS is surprisingly Ubuntu 16). Good Linux Security Software: - ModSecurity V3...tough to figure out but so worth it. An incredible L7 Firewall. Immediately provides benefits - UFW...utt…
It also spews a bunch of chains all over iptables, making it harder to understand when you actually need to use it directly for something more advanced like mangling.
Re: FireHOL – Linux firewalling and traffic shaping for humans
#24We have a couple of servers we can’t move to the cloud for a variety of reasons. In addition, they are running some super legacy applications. Because of this, we’ve really had to focus on OS level security to protect the application (OS is surprisingly Ubuntu 16). Good Linux Security Software: - ModSecurity V3...tough to figure out but so worth it. An incredible L7 Firewall. Immediately provides benefits - UFW...utt…
I find that UFW is more of a pain than its worth when it comes to simple rules everybody needs like "block everything, allow this handful of ports", mostly because the syntax is too english-like and so it's easier to get confused how you're supposed to write the rule. It also spews a bunch of chains all over iptables, making it harder to understand when you actually need to use it directly for something more advanced…
> block everything, allow this handful of ports
This is trivial.
ufw default deny incoming
ufw allow 22