<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Selinux on </title>
    <link>https://wassimaouadi.com/tags/selinux/</link>
    <description>Recent content in Selinux on </description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 28 Jul 2026 21:31:13 +0200</lastBuildDate>
    <atom:link href="https://wassimaouadi.com/tags/selinux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SELinux</title>
      <link>https://wassimaouadi.com/posts/linuxselinux/</link>
      <pubDate>Tue, 28 Jul 2026 21:31:13 +0200</pubDate>
      <guid>https://wassimaouadi.com/posts/linuxselinux/</guid>
      <description>&lt;p&gt;SELinux is an implementation of the Mandatory Access Control security model in the Linux kernel. It bears more weight than the Discretionary Access Control security model, implemented as the Unix-based file permissions (ugo, rwx); To illustrate the power of SELinux, a Linux user, even the &lt;em&gt;root&lt;/em&gt; account, gets denied access to his own files if the result of the SELinux authorization chain is a deny.&lt;/p&gt;&#xA;&lt;p&gt;SELinux assigns a context (aka label) to every Linux user, process, file, directory, port, socket, hardware device, etc. These are considered as either subjects (Linux users and processes) or objects (files, directories, ports, &amp;hellip;).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
