secureblue is for those whose first priority is using Linux, and second priority is security. secureblue does not claim to be the most secure option available on the desktop. We are limited in that regard by the current state of desktop Linux standardization, tooling, and upstream security development. What we aim for instead is to be the most secure option for those who already intend to use Linux. As such, if security is your first priority, secureblue may not be the best option for you.
If security is your FIRST priority, they outright say their work is limited. So… that’s where I’m getting it from.
Linux is used in security contexts. What do you think Kali Linux is for? There’s a linux distro that is literally a hypervisor to separate everything into VMs (Qubes). Fedora allows you to activate more security options like SELinux (which is also one way Android achieves more security BTW). And I could go on, but it seems you chose to be ignorant before making the claim linux was insecure.
Linux distros babe many flavors and eachallows a different focus.
Many desktop Linux distros have poor security defaults. Fedora even disables the restrictions on ptrace by default, which is strange considering the browser sandbox needs ptrace restrictions in order to function properly. Debian and Ubuntu default to apparmor which is very insecure (remember crackarmor?) and Arch has basically no security ootb and the AUR is essentially NEEDED in order to use it for most things, despite how unvetted and messy it is. Kali is not for daily driving, for the record.
I implore you to read SecureBlue’s documentation which is where the bulk of my knowledge has been from. Even Android is not as secure as it could be, there is a reason that GrapheneOS, the pinnacle of Android security, doesn’t even consider their build of Android secure enough.
Fedora’s choice to have ptrace_scope 0 sure is strange, it seems they had a discussion about it to revert it back to the upstream default of 1.
SEL being important was actually the main reason why in the light of recent kernel vulnerabilities I switched back to openSUSE, after being on Void for a while as inspired by this guide.
That the AUR is insecure lays basically in its name, I really don’t get why people would use for anything but the most niche packages.
What Android is doing well compared to Linux is that it has proper per application compartmentalization, whereas *nix systems would require each program to be run by a different user to separate them, though Linux is also improving in that regard, for example through SEL or the flatpak sandbox.
Maybe it is someone who blasts astroturfing? Idk
I mean I guess following the messaging of one of the only explicitly security-focused Linux distros is considered “astro turfing” then? Hmm.
From their site directly:
If security is your FIRST priority, they outright say their work is limited. So… that’s where I’m getting it from.
Linux is used in security contexts. What do you think Kali Linux is for? There’s a linux distro that is literally a hypervisor to separate everything into VMs (Qubes). Fedora allows you to activate more security options like SELinux (which is also one way Android achieves more security BTW). And I could go on, but it seems you chose to be ignorant before making the claim linux was insecure.
Linux distros babe many flavors and eachallows a different focus.
Many desktop Linux distros have poor security defaults. Fedora even disables the restrictions on ptrace by default, which is strange considering the browser sandbox needs ptrace restrictions in order to function properly. Debian and Ubuntu default to apparmor which is very insecure (remember crackarmor?) and Arch has basically no security ootb and the AUR is essentially NEEDED in order to use it for most things, despite how unvetted and messy it is. Kali is not for daily driving, for the record.
I implore you to read SecureBlue’s documentation which is where the bulk of my knowledge has been from. Even Android is not as secure as it could be, there is a reason that GrapheneOS, the pinnacle of Android security, doesn’t even consider their build of Android secure enough.
Fedora’s choice to have ptrace_scope 0 sure is strange, it seems they had a discussion about it to revert it back to the upstream default of 1.
SEL being important was actually the main reason why in the light of recent kernel vulnerabilities I switched back to openSUSE, after being on Void for a while as inspired by this guide.
That the AUR is insecure lays basically in its name, I really don’t get why people would use for anything but the most niche packages.
What Android is doing well compared to Linux is that it has proper per application compartmentalization, whereas *nix systems would require each program to be run by a different user to separate them, though Linux is also improving in that regard, for example through SEL or the flatpak sandbox.
Yeah I pretty much chose to take matters into my own hands by importing some of the SecureBlue defaults (with a few modifications) into my config.