SELinux provides a strong security measure that can make an SELinux-enabled operating system a type of “fortress”: the so-called “confined users” [1] [2] [3], which add security and isolation capabilities that are in several respects comparable to containers but without many of their restrictions in GUI use cases (this topic is focused on desktop use cases, not server, infra, and such). By default, SELinux does not enforce much within user accounts but only around them. But in graphical desktop...
yeah, same. I am currently on NixOS, but looking to move away because it’s lacking support any MAC. I really love NixOS and it’s declarative approach to things, but i can’t live with such a large security hole in my home Network.
As soon as i find a Distro that has MAC and allows for at least semi-declarative configuration, i am switching. But being able to declare an env/dconf setting in my config and sync it across all devices is just too powerful
while i think that ansible is really cool, it’s not the same as Nix.
correct me if i’m wrong, but afaik Ansible just modifies the current state of the System with a declarative configuration.
Nix reverts your system back to install and then applies the configuration. The result is that in Nix if i remove something from the configuration.nix it is as if it never existed, whereas on Ansible it stays unless i manually run a task to uninstall it.
yeah, same. I am currently on NixOS, but looking to move away because it’s lacking support any MAC. I really love NixOS and it’s declarative approach to things, but i can’t live with such a large security hole in my home Network.
As soon as i find a Distro that has MAC and allows for at least semi-declarative configuration, i am switching. But being able to declare an env/dconf setting in my config and sync it across all devices is just too powerful
I suggest you check Silverblue + Ansible (or CoreOS/IoT for server stuff).
while i think that ansible is really cool, it’s not the same as Nix.
correct me if i’m wrong, but afaik Ansible just modifies the current state of the System with a declarative configuration.
Nix reverts your system back to install and then applies the configuration. The result is that in Nix if i remove something from the configuration.nix it is as if it never existed, whereas on Ansible it stays unless i manually run a task to uninstall it.