8 Comments
- mmcgrath, on 11/20/2007, -0/+4I have to say its too bad SELinux was introduced as it was. My first experiences with it were so poor that for a long time I just turned it off. Thats not the case anymore, its gotten easier to understand and easier to configure.
- diggityduggity, on 11/20/2007, -0/+3Nice overview. SELinux has really matured to the point where I never even notice that it's on.
- HarryBauzonia, on 11/21/2007, -0/+2Your comment prompted me to enable it (just now) on my ftp server. I've always disabled it because it turned the system into a slow pig.
I'll see how it goes. - xjamesm, on 11/21/2007, -0/+2Yep, it is a pity, but there was no way that SELinux could have been delivered in a perfect state with both ease of use and high security -- this is extremely difficult stuff, and hasn't even been done before in a generally available OS with millions of general purpose users. SELinux had to be introduced iteratively, with a real feedback loop from users, and quite possibly the only way this is even achievable at all is because of open source.
(I'm an SELinux developer...) - osopolare, on 11/22/2007, -0/+1Is may be obscure and complex to you Marluz, but if you were to RTFM you'd see that it has very significant security benefits.
- schestowitz, on 11/20/2007, -1/+1I was at the point where I had to use the CLI a few days ago, only to allow SSH connections from the outside. Maybe it's time to look at Fedora again. :-)
- mwiriadi, on 11/20/2007, -1/+1Yeah I would have to agree. There are occasions I still have issues with it but I'm not to sure what causes the issues even with the error since they go to /dev/null
- mariuz, on 11/21/2007, -2/+1it's still security trough obscurity and complexity


What is Digg?
No big deal, vassever. Bruno is our latest guest for Digg Dialogg.