Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've always understood Firestarter to be a graphical frontend to iptables.
iptables are a part of the kernel.
You need to start Firestarteter as Root as indeed you do most GUI configuration programs, but once you have created the rules in iptables with the Firestarter GUI it doesn't need to be run again unless you need to make changes to those rules.
Firestarter is a GUI tool that creates script that run iptables. iptables is a user-land program that configures the kernel netfilter module rules. You might be able to run the GUI as a regular user, except that it will try to launch iptables, which requires root privileges. Also, the GUI tries to create scripts that are installed in /etc/.., which is normally requires root write access. That is why the rules it creates are persistent, and get reloaded after booting.
Since firestarter is a GUI application, is it safe to assume that it has to run sometime during or after the user login?
If so, you could try a shell script that is run by the user (when the user presses enter after entering username and password).
1) xhost +localhost # to give GUI to another user.
2) sudo firestarter # assuming the sudoers file has the necessary entry to allow user to run a sudo command.
3) xhost -localhost # to remove GUI from other users.
Last edited by bigrigdriver; 02-12-2008 at 10:22 AM.
thats like music to my ears! (the gui is only a ?configurator? and you don't need it running all the time YaY!)
now i just need to know how to shut !every! port, then open them up on a per-program that "I" use basis
I'll read that guide soon +thanx
>>my experience> i went into the options and shut everything down, but then i couldn't use any net apps, so i guessed that i'd have to use netstat and know how to 'add rules' but I didn't know how... um, now i've looked and see that iptables 'does' have some good rules in it> but it still doesn't pass the test over at shieldsup>>