<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lockdown on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/lockdown/</link>
    <description>Recent content in Lockdown on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 07 May 2026 03:01:01 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/lockdown/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux Kernel Lockdown Mode Without the Enterprise Drama</title>
      <link>https://linuxeries.org/post/2026-05-07-linux-kernel-lockdown-mode-without-the-enterp/</link>
      <pubDate>Thu, 07 May 2026 03:01:01 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-05-07-linux-kernel-lockdown-mode-without-the-enterp/</guid>
      <description>&lt;h2 id=&#34;introduction-to-kernel-lockdown-mode&#34;&gt;Introduction to Kernel Lockdown Mode&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been using Linux for years, and one feature that&amp;rsquo;s really caught my attention is Kernel Lockdown Mode. This security feature restricts access to certain kernel features, making it more difficult for an attacker to escalate privileges or modify the kernel. It was introduced in Linux kernel 5.4, back in 2019, and has been improved in subsequent releases. As of 2026, Kernel Lockdown Mode is a mature feature that can be easily enabled on most Linux distributions.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
