If there's any job opening related to #selinux, let me know :)
If there's any job opening related to #selinux, let me know :)
Find out what happened in this #oSC25 talk about the switch of #SELinux as the default MAC system in #openSUSE Tumbleweed, This talk will explore the shift from #AppArmor and the lessons learned. A must-watch for those following system security! #Linux #openSUSE https://youtu.be/8wBLbhSjDwE?si=1fOBIHkq1KkU5ynV
'"[…] #SELinux stops all access unless allowed by policy. […] Before the SELinux 3.6 userspace version, it was not possible to drop any access already allowed in the base SELinux policy or in a module. […] The changes in the latest SELinux userspace release 3.6 introduced support for deny rules. They are documented in Access Vector Rules: "Remove the access rights defined from any matching allow rules.""'
https://developers.redhat.com/articles/2025/06/04/how-selinux-deny-rules-improve-system-security
The AlmaLinux and Fedora setups set SELINUX to permissive, until I find time to allow the right port in selinux...
#SELinux becomes default on openSUSE! Learn how Mandatory Access Control evolves for Tumbleweed at the #openSUSE Conference. #Linux #Security https://events.opensuse.org/
I am experimenting with MicroOS running btrfs and SELinux.
I have some storage i use for Minecraft server data for instance, on the partition i have a directory with readonly snapshots. The server will not boot properly, because it's running auto relabeling and cannot relabel the readonly stuff.
What's the correct way to handle this? I've tried mounting the partition in different locations, but it seems everything is targeted by the relabel
Ah.. nothing beats spending 2 hour trying to create a simple #systemd service + timer + bash script to back up an sqlite database every week and it just not working because random permission issues just for selinux to be the culprit. Love how you need another tool to actually understand wtf #SELinux wants from you. #linux
@opensuse Tumbleweed rolling release moves from AppArmor to SELinux for its underlying security layer
https://www.linux-magazine.com/Online/News/openSUSE-Tumbleweed-Ditches-AppArmor-for-SELinux
#openSUSE #Tumbleweed #AppArmor #SELinux #Linux #OpenSource #distro #FOSS #security
So #opensuse switched to #selinux. Changing my systems works. Only Steam is not running, because selinux blocks boolean.
I have to admit, that I don't understand selinux. Is there a easy to understand tutorial? I don't want to mess around.
In the suse forum I found this solution:
sudo setsebool selinuxuser_execmod 1
..but with hint: If you understand the risks.
I don't understand the risc :)
#openSUSE Adopts #SELinux as Default MAC (Mandatory Access Control) System on New #Tumbleweed Installations https://9to5linux.com/opensuse-replaces-apparmor-with-selinux-on-new-tumbleweed-installations
#Tumbleweed Weekly Review #SELinux is now the default LSM for new installs! Plus:
KDE Gear 24.12.2
GNOME Shell 47.4
GIMP 3.0 RC3
Coming soon: #Linux Kernel 6.13.2, #PipeWire 1.3.82 & #Python 3.13!
https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/Z4GBJPYANFF4KQ2FL4NKPHNRNMLOCPMG/
Stay updated on #Tumbleweed's #SELinux transition! Follow discussions & progress on #openSUSE's Factory mailing list
https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/G3W5NIY3OKRBHPHWTPYEUPSS4LKZN77N/
Starting with snapshot 20250211, #SELinux becomes the default #MAC system for new installs, boosting security! #AppArmor is still optional. The first #boot might take a little time. #openSUSE #Tumbleweed https://news.opensuse.org/2025/02/13/tw-plans-to-adopt-selinux-as-default/
Big Change in #Tumbleweed! Starting with snapshot 20250211, #SELinux will be the default Mandatory Access Control (MAC) system in enforcing mode! Users can still opt for AppArmor during installation. Read more about it! #openSUSE https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/G3W5NIY3OKRBHPHWTPYEUPSS4LKZN77N/
@kde@floss.social @kde@lemmy.kde.social
Thx for the info, then it is like that.
Here is the goal proposal
https://phabricator.kde.org/T17370
Tbh, #bubblewrap would need to be fixed drastically to be as secure as the #Android #sandbox. And (I am not sure yet) I think even #Snaps are more secure (on #Ubuntu with #Apparmor patches) than #Flatpak with the current system.
As far as I understood, sandboxing needs to happen in #userspace, with tools like #fuse doing the work while being restricted by #MAC like #SELinux or Apparmor.
@kde@floss.social @kde@lemmy.kde.social
Can you tell us what happens on the "sandbox all the things" goal?
I think this is a pretty crucial step forward, even though #sandbox technologies (most often through user namespaces) are more problematic than I initially thought.
(Basically, user #namespaces open up #privesc dangers to the monolithic #kernel, which is incredible. #Android and #ChromeOS use #LXC, mounts and #SELinux for #sandboxing)