On Friday 07 March 2008 19:21:06 Therese Trudeau wrote: > > Therese, the setroubleshoot package mentioned here was installed by > > default on my system. If you go to that after you have had a failure it > > generally tells you what it saw as a threat, and what to do about it if > > it should be allowed. Usually it's just a matter of copy and paste a line > > of command. > > Thanks Anne, > > Will setting to permissive prevent real time threats, or just tell me what > happened after the fact of a failure? > I'm no expert on this, Therese, but I doubt the advice you've been given that setting to permissive is the same as having it disabled. Why? Because I had quite a number of problems with it set to permissive, mainly ones that stopped samba working. Once I had sorted out the necessary commands samba has behaved without problems. If it was as ineffective as setting it to disabled I would not have had to do this. I'd say set it to permissive, use setroubleshooter, and if you still can't sort it, either post here what setroubleshooter says about it or google for parts of the message. Anne
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
