On a recent install I cannot get system-config-selinux to start, it gives :
Traceback (most recent call last):
File "/usr/share/system-config-selinux/system-config-selinux.py", line 57, in <module>
gnome.program_init("SELinux Management Tool", "5")
AttributeError: 'module' object has no attribute 'program_init'
I am learning SELinux from LinuxCBT and I'm stuck at one place. Now video is on RHEL 4 (so tell me if things has changed since, cause I can't find anything related) shows how to disable SELinux security on httpd. It's following way
I have been using Fedora for about two years. I love it except one thing: I can not get used to SELinux. SELinux in Fedora evolves rapidly and it is not uncommon that an updated SELinux breaks up other things. So here is my question: is it really useful for a desktop which doesn't have a whole bunches of services running except OpenSSH? I am deciding whether to disable SELinux for good.
So we're supposed to be able to understand SeLinux? Over the last few days while using Fedora 18 Beta I've been seeing some SeLinux warnings while doing system wide searches. While I've been able to handle SeLinux issues on my own (for the most part) this proposed solution baffles me.
I keep getting SELinux error messages that state "SELinux is preventing samba (/usr/sbin/smbd) "search" to / (fusefs_t)." and the like, seems that pretty much everything I do generates some kind of error. I currently have SELinux set to permissive but I don't want to continue to run that way.