5 ms·
I've advocated for years that each program should be ran as its own user and group, isolated from the rest of the system. So let's say you run Firefox, is shoul
by lakomen 5y ago
I've advocated for years that each program should be ran as its own user and group, isolated from the rest of the system.
So let's say you run Firefox, is should run as firefox_username user and group.
This way any exploit is ran with the user/group permissions, and unexploited it has no read write access outside its own user and group.
Selinux is a beast but there are tools to help with determining which settings need to be applied.
If you desire a truly locked down system, where you have a person or can afford a person dedicated to its security it's a good tool. Otherwise just turn it off.
How likely is it your server is going to be actively attacked? Usually very unlikely. We don't count the random and always present background brute force attempts, they're just background noise.
- dale_glass 5y agoYou can't do that, the permissions system isn't flexible enough, and the system will fight you. Eg, pulseaudio runs as the logged in user, and your firefox won't be able to talk to it. No youtube for you. Once you figure out the flexibility needed, you're back to SELinux pretty much.
- d2wa 5y agoThat works for services but not apps. For apps, Flatpak tries to solve this.