SELinux blocking Access

[richyrich]

I've spent the last couple of days trying to setup a Fedora 14 server with Samba to use as a PDC. Eventually, I managed to get it setup and logon to the domain, but my test users could only browse folders and not see, open or create any files (even though they should have had permission)

I finally found a thread (http://fedoraforum.org/forum/showthread.php?t=248629) on this forum which mentioned trying setenforce 0. As soon as I did this, I could see files on the server and all permissions seemed to be working. As I understand it, this command basically switches off SELinux, so I thought I'd find out some more info on it.

When searching for more info on SELinux I found this thread (http://fedoraforum.org/forum/showthread.php?t=258154) which mentions about relabelling. As a complete beginner in Fedora/Linux I have no idea what this means. How do you go about relabelling and what directories / files do you have to relabel.

When I have SELinux on and view the troubleshooting, I can see it blocks access and it says to fix it, I need to run setsebool -P samba_enable_home_dirs=1. But this boolean is already enabled in SELinux.

So, what should I do to resolve this problem? Just use setenforce 0? What booleans need to be set in SELinux for Samba to work correctly?

Any help would be appreciated..:)

[gthill]

I think it's safe to turn it off. Unless you know why you need it, you probably don't.

Others on the forum may be able convince you otherwise.

[richyrich]

Thanks for the reply.

I believe it provides additional security, so I guess it would be better to have it running than not? What would be the implications of setenforce 0? Does it make the server less secure?