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.
iptables is not a firewall. iptables is a user-space application that allows one to configure the kernel-space rule-set of the the netfilter kernel module. A collection of rules composed and organized in such a way that they control network traffic into, out of, and through a host can be a firewall (or router). When you run iptables, it requires some arguments to modify or display the rule-set in the kernel module. Often, the sequence of iptables commands that creates a coordinated set of rules is encapsulated into a shell script, and this is often thought of as a firewall. The rules in the firewall script need to be composed in a way that creates a firewall suitable for the application. Sometimes the sequence of iptables commands is generated by a GUI tool, such as the ones you mentioned. If the firewall script you are using is not satisfactory, you can modify it. You can also modify the rules on-the-fly, using discrete iptables commands to add/delete/modify specific rules.
Port 22 is not normally FTP; it is SSH (FTP uses port 21). The whole concept of ports being 'open' is a misleading use of the term, in my opinion. A port can be thought of as 'open' if either of two things are true: an application or service is listening for incoming traffic on the specified port, or if there is no firewall rule that blocks traffic into (or out of, perhaps) a particular port. An application or service may be listening on a port, but receiving no traffic, due to the upstream application of a netfilter rule. In this situation, the application will not know that it will receive no traffic.
iptables is not a firewall. iptables
Port 22 is not normally FTP; it is SSH (FTP uses port 21). The whole concept of ports being 'open' is a misleading use of the term, in my opinion. A port can be thought of as 'open' if either of two things are true: an application or service is listening for incoming traffic on the specified port, or if there is no firewall rule that blocks traffic into (or out of, perhaps) a particular port. An application or service may be listening on a port, but receiving no traffic, due to the upstream application of a netfilter rule. In this situation, the application will not know that it will receive no traffic.
--- rod.
oops i do know hat port ftp is on, really! i typed without refering to the term. thanks for the info. i now know it is iptabes/netfilter. using something called firehol, to config it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.