<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Samuel Matildes - Knowledge Base</title><link>https://docs.matildes.dev/tags/security/</link><description>Recent content in Security on Samuel Matildes - Knowledge Base</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 26 May 2026 14:15:13 +0100</lastBuildDate><atom:link href="https://docs.matildes.dev/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>How Antivirus Software Can Prevent Linux Boot: Troubleshooting Guide</title><link>https://docs.matildes.dev/linux/admin/antivirus-boot-issues/</link><pubDate>Fri, 31 Oct 2025 00:00:00 +0000</pubDate><guid>https://docs.matildes.dev/linux/admin/antivirus-boot-issues/</guid><description>&lt;h2 id="understanding-antivirus-boot-interference"&gt;Understanding Antivirus Boot Interference&lt;a class="td-heading-self-link" href="#understanding-antivirus-boot-interference" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Antivirus software, while crucial for system security, can sometimes interfere with the Linux boot process. This occurs when security modules become overly aggressive during system initialization, potentially causing boot failures, readonly filesystem mounts, or service startup issues.&lt;/p&gt;
&lt;h3 id="common-symptoms"&gt;Common Symptoms&lt;a class="td-heading-self-link" href="#common-symptoms" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;System fails to boot completely&lt;/li&gt;
&lt;li&gt;Filesystem mounts as readonly (&lt;code&gt;ro&lt;/code&gt;) instead of read-write (&lt;code&gt;rw&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Critical services fail to start&lt;/li&gt;
&lt;li&gt;Boot hangs at specific points&lt;/li&gt;
&lt;li&gt;SELinux/AppArmor policy violations during boot&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="filesystem-readonly-issues"&gt;Filesystem Readonly Issues&lt;a class="td-heading-self-link" href="#filesystem-readonly-issues" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;One of the most common problems occurs when antivirus software causes the root filesystem to mount readonly. This prevents the system from writing critical boot files and can halt the initialization process.&lt;/p&gt;</description></item><item><title>Kernel Mode vs User Mode: Privilege Levels and System Call Execution</title><link>https://docs.matildes.dev/linux/kernel/kernel-mode-vs-user-mode/</link><pubDate>Tue, 14 Jan 2025 00:00:00 +0000</pubDate><guid>https://docs.matildes.dev/linux/kernel/kernel-mode-vs-user-mode/</guid><description>&lt;p&gt;&lt;i class="fas fa-shield-alt" aria-hidden="true"&gt;&lt;/i&gt; CPU Privilege Levels and Execution Contexts&lt;/p&gt;
&lt;h2 id="summary"&gt;Summary&lt;a class="td-heading-self-link" href="#summary" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Modern processors implement hardware-enforced privilege levels to isolate untrusted user code from critical kernel services. Linux uses two primary modes: &lt;strong&gt;kernel mode&lt;/strong&gt; (ring 0, CPL 0, EL1) and &lt;strong&gt;user mode&lt;/strong&gt; (ring 3, CPL 3, EL0). Kernel mode grants unrestricted access to CPU features, physical memory, I/O ports, and privileged instructions. User mode restricts access to a virtualized, isolated address space and requires kernel mediation for hardware resources. The transition between modes occurs via system calls, interrupts, and exceptions, all managed by the kernel&amp;rsquo;s interrupt and system call handlers. Understanding this separation is fundamental to security, performance optimization, and kernel debugging.&lt;/p&gt;</description></item></channel></rss>