Originally this was a reply to this article about a Windows feature called Recall, but there’s a good argument the author’s concerns resonate far beyond Windows and Meta to proprietary generally.
Originally this was a reply to this article about a Windows feature called Recall, but there’s a good argument the author’s concerns resonate far beyond Windows and Meta to proprietary generally.
I’ve been wondering about a similar change, or possibly to Arch. What I’m still wondering about is security: Fedora has Selinux enabled all over the system, and Opensuse and Arch do not. Anyone know what level of risk this mitigates?
I think OpenSUSE Tumbleweed has SELinux enabled now too. I’m not sure what you mean by all over the system, as I’m not that familiar with SELinux yet. I believe that Tumbleweed used to use AppArmor but recently switched to SELinux? I also believe that Leap (the stable version of OpenSUSE) still uses AppArmor.
Based on opensuse’s docs, it seems to be in permissive state, whereas on my Fedora by default:
$ selinuxenabled && echo yup yup $ getenforce EnforcingNot sure if the warm fuzzy feelings I get from this are justified (like what are the actual applied rules on apps? I have no idea), but it is a bit warmer and fuzzier.
I see, thanks, I didn’t know the details. I just had a faint recollection that they had switched from AppArmor to SELinux.
I wouldn’t worry about security. Mainly because more security always means less things work as intended, and there’s not really any malware targeting Linux. Just like, pick a distro, use it, and pivot based on things you like or dislike