Linux - Security This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
12-16-2005, 07:38 PM
|
#1
|
Senior Member
Registered: May 2004
Location: Albuquerque, NM USA
Distribution: Debian-Lenny/Sid 32/64 Desktop: Generic AMD64-EVGA 680i Laptop: Generic Intel SIS-AC97
Posts: 4,250
Rep:
|
Do I need something more flexible than Firestarter?
I've used Firestarter for a long time and like it a lot. Simple and apparently quite secure. The one thing I want to do that I can't seem to do is define exceptions to Inbound traffic rules.
As I understand it, I can open a port to all comers only. There does not seem to be a way to tell Firestarter that anyone can use this port EXCEPT a specifically named ip address or a range of addresses. Am I missing something?
Is there perhaps a blacklist file that I can populate which iptables will check without prompting from Firestarter? Or is there another iptables GUI that allows such rulemaking. I notice that my 'Debian Bible' recommends Shorewall. Anyone familiar with that?
|
|
|
12-16-2005, 07:54 PM
|
#2
|
Member
Registered: Dec 2004
Location: IN, USA
Distribution: debian etch
Posts: 402
Rep:
|
Shorewall is kind of a config file for iptables. That's what I use. It's easy. If you use KDE, you can go with guarddog.
|
|
|
12-16-2005, 09:35 PM
|
#3
|
Member
Registered: Jun 2005
Posts: 73
Rep:
|
|
|
|
01-05-2006, 09:57 AM
|
#4
|
Member
Registered: Oct 2003
Location: New York
Distribution: Debian Sid
Posts: 185
Rep:
|
Quote:
Originally Posted by rickh
I've used Firestarter for a long time and like it a lot. Simple and apparently quite secure. The one thing I want to do that I can't seem to do is define exceptions to Inbound traffic rules.
As I understand it, I can open a port to all comers only. There does not seem to be a way to tell Firestarter that anyone can use this port EXCEPT a specifically named ip address or a range of addresses. Am I missing something?
Is there perhaps a blacklist file that I can populate which iptables will check without prompting from Firestarter? Or is there another iptables GUI that allows such rulemaking. I notice that my 'Debian Bible' recommends Shorewall. Anyone familiar with that?
|
I use Shorewall on Debian. It's very good, but not that simple to use. It is easier than writing iptables scripts by hand, but not nearly as simple as the GUIs (Firestarter, Guarddog). You edit config files (at least 4 or so for a minimal config) and the Shorewall scripts then generate the iptable rules for you. Note that any mistakes (and you WILL make them!) result in the firewall locking down the system and you then have to sift through slightly cryptic startup error messages and log files to find the problem. Also, shorewall has no running process that you can monitor like the GUIs; you need to look at the log files (or the console messages). There are scripts (I use fwlogwatch) to sift through the Shorewall log messages.
|
|
|
All times are GMT -5. The time now is 10:20 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.
|
Latest Threads
LQ News
|
|