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.
Honestly, using ssh to log into the server to modify iptables is probably the best solution. Giving the Apache user control over your firewall rules is a seriously bad idea (an attacker could easily use DNAT to redirect all traffic to a malicious host for a man-in-the-middle attack). If you absolutely needed a remote GUI for manipulating iptables, you should at least use a protocol that encrypts traffic (like an ssl tunnel or ssh) and use a robust method of authentication. I'm not a fan of webmin, but I know it already has a module for remote iptables management and I would bet there are other similar solutions as well.
In that case, you could improve it by using an https connection instead so that the auth credentials are passed over an encrypted link rather than in plaintext. Basic auth would work in that scenario, but one of the other forms of Apache-supported authentication might be better (like digest). It would also help if you could limit access to that PHP page using a directory container and specifying only a limited number of IPs. That should keep anyone from hammering away at it. I still don't like linking Apache and IPtables together due to issues if Apache/PHP gets exploited, but those improvements might help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.