FC6 SELinux problem

markelo · 03-11-2007, 05:03 PM

Ok. I upgraded my kernel and now I am getting following messages ( these are part from dmesg ).

Code:

SELinux: initialized (dev cpuset, type cpuset), not configured for labeling
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
SELinux: initialized (dev hdb3, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev fuse, type fuse), not configured for labeling
SELinux: initialized (dev fuse, type fuse), not configured for labeling
SELinux: initialized (dev fuse, type fuse), not configured for labeling
SELinux: initialized (dev fuse, type fuse), not configured for labeling

Should I do something for this labeling issue or what? I use ntfs-3g driver and selinux has problem with this and FUSE but what is problem with that cpuset?

I am really lost with this SELinux stuff and security contextes and audit and whatever...

vargadanis · 03-11-2007, 09:52 PM

I know that SELinux just messed up everything when I tried to enable it. Many, many tutorials out there for FC6 strongly suggest to disable SELinux. Check out howtoforge.com and you will see.

I know that it doesn't make thing so much more secure and safe that it was worth bothering. I know that it might sound LAME but this is Linux not Windows. It is secure by default unless you run something as root. (^_^) [Some people will kill me for that post, I know that - sorry SELinux funs. x_0]

PhillipHuang · 03-12-2007, 04:06 AM

Quote:

Originally Posted by vargadanis

I know that SELinux just messed up everything when I tried to enable it. I know that it doesn't make thing so much more secure and safe that it was worth bothering. I know that it might sound LAME but this is Linux not Windows. It is secure by default unless you run something as root.

Vargadanis, I agree with you. SELinux has too many things to screw up, it seems to be an annoy job. I dislike SELinux for it makes things harder, though it really enhances the security level of the system.

In my opinion, security issues caused by "setuid" and "setgid" can be avoided in the programming stage, which is the progrmmer's responsiblity. To the end user and customer, easy-using is the most important even than OS security.

The good idear, SELinux still has a long way to go.

Phillip