SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Firestarter does not detect the iptables in normal user mode, he says you dont have iptables, but I have iptables installed and can run as root very well. can anyone help me? Is it a permission problem?
Because Firestarter makes changes to your "system" you can't run it as a normal user, it must be run as root. You will need to either run firestarter from a root terminal, or if you have libgnomesu installed you can add gnomesu to the Exec= line in front of firestarter (Exec=gnomesu firestarter) in the /usr/share/applications/firestarter.desktop file. You will also need an rc.firewall script in /etc/rc.d so that your firewall will be started each time you boot.
Are you still running Dropline GNOME? If so I provide a Dropline Extra Firestarter package. You can download it from HERE. The Dropline Extra package is PAM enabled so if you are running a different GNOME now you can get my "regular" Firestarter package from HERE and my GNOMEsu (libgnomesu) from HERE. The last two packages are built using a clean Slackware 10.2 and Freerock GNOME 2.12.1 install. They both also put a rc.firewall.new file in /etc/rc.d so all you'll have to do is rename it to rc.firewall.
Whichever you download all you have to do is open a root terminal, cd to where the packages are located and type in:
upgradepkg --install-new *.tgz
The reason I always do upgradepkg is just in case the package is already installed it will upgrade it and with the --install-new switch if it ain't there it will installpkg it instead.
I use slack 10.2 with Dropline Gnome and 2.6.15 kernel. Done all you said. Firewall is started at boot-time, I login as normal user, go into a terminal, run "firestarter" and it gives me the same old problem, you must be root in order to run firestarter. In essence, I cant use firestarter as a normal user even with your packgage.
I run "gnomesu firestarter", asks for password and it seems to work, but in terminal appears this :
GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
I added the exec line, it dosent work, only gnomesu firestarter. But is there a way to actually logout of gnomesu? Or when I end the session of firestarter gnomesu ends?
Try Applications --> System Tools --> Firestarter
[EDIT]
After I replied to your post I noticed that you edited to include the gnomesu stuff. If you are running Dropline GNOME and downloaded the Firestarter package that ends in xdle.tgz then you don't NEED to add anything to the desktop file. It will use PAM to authenticate so you can remove gnomesu from the Exec= line. If, on the other hand, you downloaded the package that ends in xmmy.tgz then you don't NEED to edit the desktop file because I've already done that for you during the package creation. Either way, you don't NEED to edit the desktop file at all .
[/EDIT]
Initially, I compiled it from the sources from the offician firestarter site ...
EDIT
Removed everything, every package of firestarter, installed only yours, blissfull success! Keep up the good work
BTW : It asks me everytime I want to start firestarter for the pesky root password. I modify sudoers and add "username ALL= NOPASSWD: /usr/bin/firestarter" but when I launch it from a terminal with "sudo firestarter", it works fine but prints this on the terminal:
GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Initially, I compiled it from the sources from the offician firestarter site ...
EDIT
Removed everything, every package of firestarter, installed only yours, blissfull success! Keep up the good work
Great, glad you got it working!
Quote:
Originally Posted by Mercurius
BTW : It asks me everytime I want to start firestarter for the pesky root password.
That's exactly what it is supposed to do. My Dropline package uses PAM to authenticate but you STILL have to pass the root password to it.
Quote:
Originally Posted by Mercurius
I modify sudoers and add "username ALL= NOPASSWD: /usr/bin/firestarter" but when I launch it from a terminal with "sudo firestarter", it works fine but prints this on the terminal:
GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
By using sudo you are circumventing the PAM authenication. If you will look at /usr/bin/firestarter it is actually a symlink to /usr/bin/consolehelper. This consolehelper file "redirects" to the authenication file /etc/security/console.apps/firestarter.
You can check by creating a new user ("test" for example) and seeing if the problem persists with the new user.
MMYoung's latest package runs flawlessly (as far as I can tell), but you may have issues with previous configs (depending on how you set things up). One potential issue is that you set up the GNOME session improperly. Testing a new user will tell you if that may be the problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.