This may be the wrong list for this question, but has anyone used the firestarter RPM with Selinux? I seem to get a lot of errors relating to selinux on network startup/shutdown when firestarter is installed. I am using 2.6.12.1 kernel.
Mark Bidewell
On Thu, 2005-30-06 at 17:31 -0400, Mark Bidewell wrote:
This may be the wrong list for this question, but has anyone used the firestarter RPM with Selinux? I seem to get a lot of errors relating to selinux on network startup/shutdown when firestarter is installed. I am using 2.6.12.1 kernel.
Me also. (Re: FC4 dhcp, firestarter and SE Linux permission denied messages). I got the dhcp problem that I had fixed (for some reason it had a Ford motor company IP addy in the dhcpd.conf) and I sent a message yesterday to the list listing some of the SE Linux errors that I was still getting.
Another user responded that I'd get better response from the SE Linux list and he cc'd the message there. I haven't seen any response yet, but later / tomorrow I'll try posting the errors in messages and in Audit to see if I can get some help.
DaveN
On Thu, 2005-06-30 at 17:31 -0400, Mark Bidewell wrote:
This may be the wrong list for this question, but has anyone used the firestarter RPM with Selinux? I seem to get a lot of errors relating to selinux on network startup/shutdown when firestarter is installed. I am using 2.6.12.1 kernel.
hey mark -- yup. join the crowd. i was unable to do much with it with selinux in enforcing mode. but, i've forgotten to go back and check since the new policies have come out.
john
On 6/30/05, Mark Bidewell mark.bidewell@alumni.clemson.edu wrote:
This may be the wrong list for this question, but has anyone used the firestarter RPM with Selinux? I seem to get a lot of errors relating to selinux on network startup/shutdown when firestarter is installed. I am using 2.6.12.1 kernel.
Mark Bidewell
Hi Mark;
Here too. I ended up removing FS from the desktops, but on the server it seems to be working. That may be because I haven't rebooted yet. I'll be wathing this thread, hopefully there is a resolution.
-P
P Jones wrote:
On 6/30/05, Mark Bidewell mark.bidewell@alumni.clemson.edu wrote:
This may be the wrong list for this question, but has anyone used the firestarter RPM with Selinux? I seem to get a lot of errors relating to selinux on network startup/shutdown when firestarter is installed. I am using 2.6.12.1 kernel.
Mark Bidewell
Hi Mark;
Here too. I ended up removing FS from the desktops, but on the server it seems to be working. That may be because I haven't rebooted yet. I'll be wathing this thread, hopefully there is a resolution.
-P
I tracked the problem with firestarter down to /etc/dhclient-exit-hooks which contains the line "sh /etc/firestarter/firestarter.sh start" which starts firestarter independed of the firestater init script. Removing this line solves the selinux errors and the firewall policy still seems to be in effect. I am theroizing that the line above is executed when the dhclient daemon attempts to shutdown as well as start thus attempting to start the firewall while closing the interface. I think this is what selinux is flagging. I haven't checked to see if there is a reason for that command yet.
Mark Bidewell
On Friday 01 Jul 2005 19:33, Mark Bidewell wrote:
This may be the wrong list for this question, but has anyone used the firestarter RPM with Selinux? I seem to get a lot of errors relating to selinux on network startup/shutdown when firestarter is installed. I am using 2.6.12.1 kernel.
I tracked the problem with firestarter down to /etc/dhclient-exit-hooks which contains the line "sh /etc/firestarter/firestarter.sh start" which starts firestarter independed of the firestater init script. Removing this line solves the selinux errors and the firewall policy still seems to be in effect. I am theroizing that the line above is executed when the dhclient daemon attempts to shutdown as well as start thus attempting to start the firewall while closing the interface. I think this is what selinux is flagging. I haven't checked to see if there is a reason for that command yet.
Yep, I can confirm this clears up all the Selinux/Kernel boot errors related to FS and all seems to be running "ok" so far.
Thanks for finding this,
Colin