[K12OSN] firestarter permission fail
Gavin Chester
sales at ecosolutions.com.au
Mon Apr 4 01:34:42 UTC 2005
On Sat, 2005-04-02 at 22:34 +0800, Gavin Chester wrote:
> Displaying my ignorance of permissions problems here in trying to work
> out why firestarter won't (fire)start :-)
>
> I noticed for the fist time since installing v4.2.0 a few weeks ago (as
> a dual-purpose server/workstation) that among the startup messages was
> the news that firestarter firewall was failing at bootup because of
> permissions. What is the name of the log file that lists services
> started? I wrongly thought it was dmesg and no other log file I checked
> shows the current boot (booted just 6hrs ago)
>
> I took a look at the /etc/firestarter/firewall.sh file and found it was
> owned by root, group root. I took the plunge and chown it to gavin,
> group root (see below) but that didn't seem to do the trick when I tried
> starting it from the CLI. These transactions are listed below if anyone
> can give me pointers on where to tackle this issue. I don't suppose I
> have firewall running since it fails on permissions, and I've become
> paranoid since repeated attempts at breakin recently via ssh (I've shut
> down sshd since I don't use it).
>
>
> [root at local ~]# chown -v gavin /etc/firestarter/firewall.sh
> changed ownership of `/etc/firestarter/firewall.sh' to gavin
> [root at local ~]# ls -l /etc/firestarter/firewall.sh
> -rw-r--r-- 1 gavin root 0 May 18 2004 /etc/firestarter/firewall.sh
>
>
> [root at local ~]# /etc/rc.d/init.d/firestarter start
> Flushing all current rules and user defined chains: [ OK ]
> Clearing all current rules and user defined chains: [ OK ]
> Zeroing all current rules: [ OK ]
> Applying Firestarter configuration: /etc/rc.d/init.d/firestarter: line
> 39: /etc/firestarter/firewall.sh: Permission denied
> &#-1;&#-1; [FAILED]
Looking further into the obvious clues with my own problem, I found that
the line where the fail occurred, line 39
of /etc/rc.d/init.d/firestarter, contained only this command:
$FS_CONFIG
... yet I can't find that command any where on my drive. Perhaps it's
buried in a binary somewhere? Either way, I'm no closer to seeing why
that is causing a permissions problem.
--
Regards,
Gavin Chester
More information about the K12OSN
mailing list