3 ms·
What's the best guide you know for SE Linux as a desktop?
by simonebrunozzi 11y ago
What's the best guide you know for SE Linux as a desktop?
- noja 11y agoYou don't need a guide, it just works. If you're installing stuff from rpm (and not from a weird backalley repo) then it all just works.
- kochthesecond 11y agoHah. I'm a linux user and even I dont believe it's that simple.
- JupiterMoon 11y agoFor GNU/Linux I find that if you stick with the commonly used packages things in your distributions repositories (on supported hardware) things do just work and it is that simple. However, (and it is a big however!) the moment you go try something slightly different good luck to you...
- simoncion 11y ago> You don't need a guide, it just works. It "just works" if the package you're installing has a corresponding SELinux profile. If it doesn't, you're in for a world of "fun" trying to come up with a correct profile. (I've played with both SELinux and Grsecurity MAC systems in the past. I know that it's not impossible to create these profiles. I also know that it's not infrequently an enormous pain in the ass, and a thing that even experts sometimes get wrong.)
- noja 11y agoIf something doesn't have a profile then it runs unconfined. That's simplified, but really does work out of the box unless you do something weird (then you flip a boolean) or very weird (then you create a custom module). But for a normal desktop user, it does just work.
- simoncion 11y agoOh! That's super useful. I stand corrected. I wonder if grsec's MAC system has grown an equivalent feature in the past four or five years. (If I overlooked the existence of such a thing in grsec, I'm gonna be so embarrassed.)
- waz0wski 11y agoThe Linux Foundation published a guide recently[1] which has recommendations for desktop. Take into consideration that unless you're running SELinux in full-enforcing mode (NOT targeted-enforcing, the default!), you still have a HUGE attack surface on your machine if you're using a web browser alone. This presentation[2] also goes into some detail about an overall layered security approach and touches on workstation security. If you really-really-really need security, you could consider something like QubesOS[3] to segregate your applications. [1] https://github.com/lfit/itpol/blob/master/linux-workstation-security.md https://github.com/lfit/itpol/blob/master/linux-workstation-... [2] http://kernsec.org/files/lss2015/giant-bags-of-mostly-water.pdf http://kernsec.org/files/lss2015/giant-bags-of-mostly-water.... [3] https://www.qubes-os.org https://www.qubes-os.org