Firestarter

[Marco Mandl]

On Sat, 06 Jan 2007 21:42:16 -0500, Jeffrey F. Bloss wrote:

> Garry Knight wrote:
> 
>> Marco Mandl wrote:
>> 
>> > after a reboot the iptables are cleared again despite
>> > firestarter is called according to sysv-rc-conf.
>> 
>> You cuold look through /etc/rc2.d to see if any other firewall
>> scripts are being run at boot.
> 
> I have the exact same "problem" as the OP on my laptop. Firestarter
> fails to load if I'm not logged in (no network up). That's even if I
> CTRL+ALT+F1 and try to start it as root, without first logging in to my
> user account and connecting to *some* network. Gives me the bright red
> [FAILED] raspberries.
> 
> I haven't investigated it too much for a number of reasons which add up
> to me not needing full time firewalling on my laptop. I do remember
> seeing an FAQ somewhere that suggested solving the problem by adding
> '<user name> ALL=NOPASSWD: /usr/sbin/firestarter' to sudoers so you
> can fire it without entering a password, then adding firestarter to your
> userland startup. That way it should be automagically active as soon as
> you log in. Check paths, <user name> is your user/login name, blah blah
> blah... and as far as I'm concerned this is an unacceptable breach of
> security. Again, YMMV.

I don't understand this. I thought the firestarter program itself is just
a frontend form maintaining the rules and monitoring. And the init scripts
are called by the root user at boot time anyway, aren't they?

Or do the init scripts have other dependencies like an established
connection?

/m