med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

335
active users

#selinux

2 posts2 participants0 posts today
Lars Marowsky-Brée 😷<p>I have *sincere* doubts whether SELinux truly improves security on a Linux desktop, or whether it is just a royal PITA.</p><p>Because clearly, an openvpn script wanting to drop in a dnsmasq config files &amp; reload a systemd service should be this fun.</p><p>Just how many people do y'all think don't just swat this with "selinux=0" and move on with our lives?</p><p>(Outside the group of people developing SELinux or distribution maintainers.)</p><p><a href="https://mastodon.online/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.online/tags/SELinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SELinux</span></a></p>
openSUSE Linux<p><a href="https://fosstodon.org/tags/Leap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Leap</span></a> 16.0 now defaults to <a href="https://fosstodon.org/tags/SELinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SELinux</span></a>, <a href="https://fosstodon.org/tags/Myrlyn" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Myrlyn</span></a> + <a href="https://fosstodon.org/tags/Cockpit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cockpit</span></a> step in for <a href="https://fosstodon.org/tags/YaST" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>YaST</span></a>, &amp; <a href="https://fosstodon.org/tags/zypper" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>zypper</span></a> has parallel <a href="https://fosstodon.org/tags/repo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>repo</span></a> downloads. <a href="https://fosstodon.org/tags/Xfce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Xfce</span></a> users on <a href="https://fosstodon.org/tags/Wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wayland</span></a> can enjoy greetd/gtkgreet instead of <a href="https://fosstodon.org/tags/LightDM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LightDM</span></a>—ideal for modern minimalists. <a href="https://news.opensuse.org/2025/08/04/leap-16-rc/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.opensuse.org/2025/08/04/l</span><span class="invisible">eap-16-rc/</span></a></p>
Jan Wildeboer 😷:krulorange:<p>Welcome to the family, OpenSUSE Leap! Finally :) The 16.0 Release Candidate makes it official. <a href="https://social.wildeboer.net/tags/SELinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SELinux</span></a> becomes the default.</p><p><a href="https://news.opensuse.org/2025/08/04/leap-16-rc/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.opensuse.org/2025/08/04/l</span><span class="invisible">eap-16-rc/</span></a></p>
9Lukas5 🚂 🐧Fedora SELinux
Miha Markič<p>Any expert on <a href="https://mastodon.social/tags/selinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selinux</span></a> over here? I need to create a custom (file) type and a custom domain, make type accessible only from said domain.</p>
Tris<p>If there's any job opening related to <a href="https://chaos.social/tags/selinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selinux</span></a>, let me know :) </p><p><a href="https://chaos.social/tags/getfedihired" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>getfedihired</span></a> <a href="https://chaos.social/tags/redhat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>redhat</span></a></p>
openSUSE Linux<p>Find out what happened in this <a href="https://fosstodon.org/tags/oSC25" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>oSC25</span></a> talk about the switch of <a href="https://fosstodon.org/tags/SELinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SELinux</span></a> as the default MAC system in <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openSUSE</span></a> Tumbleweed, This talk will explore the shift from <a href="https://fosstodon.org/tags/AppArmor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AppArmor</span></a> and the lessons learned. A must-watch for those following system security! 🐧 <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openSUSE</span></a> <a href="https://youtu.be/8wBLbhSjDwE?si=1fOBIHkq1KkU5ynV" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">youtu.be/8wBLbhSjDwE?si=1fOBIH</span><span class="invisible">kq1KkU5ynV</span></a></p>
Richard Chamberlain<p>Tried integrating ROS2 on Oracle Linux with SELinux—no go.<br>Switched to AppArmor on Ubuntu—easier, yes. Effective? Not quite.</p><p>colcon and AppArmor don’t play well together. Turns out, AppArmor’s simplicity can limit it in complex dev environments.</p><p>Here’s my story, what didn’t work, and where I’m heading next:<br>🔗 <a href="https://richard-sebos.github.io/sebostechnology/posts/AppArmor-ROS2/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">richard-sebos.github.io/sebost</span><span class="invisible">echnology/posts/AppArmor-ROS2/</span></a></p><p>Boosts appreciated if you think secure ROS2 needs better tooling. 🧵</p><p><a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> <a href="https://mastodon.social/tags/ROS2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ROS2</span></a> <a href="https://mastodon.social/tags/AppArmor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AppArmor</span></a> <a href="https://mastodon.social/tags/SELinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SELinux</span></a> <a href="https://mastodon.social/tags/DevSecOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DevSecOps</span></a> <a href="https://mastodon.social/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> <a href="https://mastodon.social/tags/Robotics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Robotics</span></a></p>
openSUSE Linux<p><a href="https://fosstodon.org/tags/SELinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SELinux</span></a> becomes default on openSUSE! Learn how Mandatory Access Control evolves for Tumbleweed at the <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openSUSE</span></a> Conference. 🔐 <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://fosstodon.org/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> <a href="https://events.opensuse.org/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">events.opensuse.org/</span><span class="invisible"></span></a></p>
ricardo :mastodon:<p>Fortifying <a href="https://fosstodon.org/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> With <a href="https://fosstodon.org/tags/SELinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SELinux</span></a> by Enforcing Mandatory Access Control for Ultimate System Security </p><p><a href="https://www.linuxjournal.com/content/fortifying-debian-selinux-enforcing-mandatory-access-control-ultimate-system-security" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">linuxjournal.com/content/forti</span><span class="invisible">fying-debian-selinux-enforcing-mandatory-access-control-ultimate-system-security</span></a></p>
Rasmus Lindegaard<p>I am experimenting with MicroOS running btrfs and SELinux. </p><p>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. </p><p>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</p><p><a href="https://fosstodon.org/tags/selinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selinux</span></a> <a href="https://fosstodon.org/tags/microos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>microos</span></a> <a href="https://fosstodon.org/tags/OpenSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSUSE</span></a></p>
TZL<p>Anyone currently have a take on the <a href="https://mstdn.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> concerns of <a href="https://mstdn.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mstdn.social/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> user <a href="https://mstdn.social/tags/namespaces" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>namespaces</span></a> <a href="https://mstdn.social/tags/usernamespaces" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>usernamespaces</span></a>? I have been rereading into it wondering whether enabling or disabling is the best approach. They seem rather insignificant with considerable surface area for attack, from my understanding. However, more applications check for/need them nowadays.</p><p>I think kernel <a href="https://mstdn.social/tags/hardening" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hardening</span></a> advice is still to disable. Makes me wonder if should e.g. be considered only if <a href="https://mstdn.social/tags/AppArmor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AppArmor</span></a> / <a href="https://mstdn.social/tags/SELinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SELinux</span></a> is active.</p>
Jan ☕🎼🎹☁️🏋️‍♂️<p>Been testing out the <a href="https://fedi.kcore.org/tags/virtiofs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>virtiofs</span></a> support now baked into <a href="https://fedi.kcore.org/tags/proxmoxVE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proxmoxVE</span></a>. It works, had to do some <a href="https://fedi.kcore.org/tags/selinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selinux</span></a> adjustments on <a href="https://fedi.kcore.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fedora</span></a> to allow my <a href="https://fedi.kcore.org/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podman</span></a> containers to use the mountpoint. Added this policy</p><p>```<br>(allow container_t unlabeled_t ( dir ( read write )))<br>```</p><p>In raw speed it is definitely not a winner - <a href="https://fedi.kcore.org/tags/nfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nfs</span></a> is easily double the speed. But on this particular VM I don't need the speed - it is nice that this is all self-contained now, and I can actually remove NFS altogether.</p><p><a href="https://fedi.kcore.org/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proxmox</span></a></p>
FurbyOnSteroids<p>Ah.. nothing beats spending 2 hour trying to create a simple <a href="https://ohai.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> 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 <a href="https://ohai.social/tags/SELinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SELinux</span></a> wants from you. <a href="https://ohai.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a></p>
Scott Williams 🐧<p>I recently read my 8 year old daughter the <a href="https://mastodon.online/tags/SELinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SELinux</span></a> coloring book before school. I'm training up the next generation of <a href="https://mastodon.online/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> adventurers!</p><p><a href="https://mastodon.online/tags/parenting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>parenting</span></a> <a href="https://mastodon.online/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHat</span></a></p>

Ugh #SELinux is the worst. I'm sure it's 100% my lack of understanding it though. I have my installation scripts all worked out with #Rex. At first for #AlmaLinux 8 but also adapted it to 9.

I had it all working properly under 9, but this new VPS somehow mounts the root disk in read-only mode after a reboot when SELinux has been enabled.

I'm *really* tempted to just keep it in permissive mode and ignore it for the rest of my life.