Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
Suppose your computer is in the internal network of an organization where a number of technicians and hackers are working there, are the following firewall rules sufficient?
Code:
iptables -P INPUT DROP
iptables -P OUTPUT ACCEPT
iptables -P FORWARD DROP
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A INPUT -i lo -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT
iptables -N SYN_FLOOD
iptables -A INPUT -p tcp --syn -j SYN_FLOOD
iptables -A SYN_FLOOD -m limit --limit 5/s --limit-burst 10 -j RETURN
iptables -A SYN_FLOOD -j DROP
I know there are many parameters to consider, but I wanted to know what rules are enough for a firewall. I use Tor on my Debian box.
Seems reasonable enough; all inbound traffic is rejected except ESTALISHED and RELATED, and you've remembered to ACCEPT everything going to "lo".
The SYN_FLOOD chain is redundant as you've already defined DROP as the default policy, but if it's intended as a framework for later rules that may accept certain inbound traffic, it makes sense.
I will be the first to admit that I have no confidence in my own ability to set up "iptables rules" correctly. Namely, that I would not expose myself to some vulnerability that I did not know about. Or, "patch" some vulnerability but actually fail to do so [correctly].
Instead, I use open tools such as Shorewall to do the heavy-lifting for me. (And I have been very surprised at the complex set of rules that such tools have put in place.)
Shorewall allows me to describe "what I want," in terms that I can understand, and it then undertakes to do the "voodoo" for me. I like it that way. Because, to me, "iptables is(!) 'voodoo!'"
Last edited by sundialsvcs; 03-15-2023 at 01:34 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.