<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Seccomp on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/seccomp/</link>
    <description>Recent content in Seccomp on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 08 May 2026 08:59:31 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/seccomp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using seccomp to Lock Down Container Privileges in Linux</title>
      <link>https://linuxeries.org/post/2026-05-08-using-seccomp-to-lock-down-container-privileg/</link>
      <pubDate>Fri, 08 May 2026 08:59:31 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-05-08-using-seccomp-to-lock-down-container-privileg/</guid>
      <description>&lt;h2 id=&#34;introduction-to-seccomp&#34;&gt;Introduction to seccomp&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen seccomp, short for &amp;ldquo;secure computing,&amp;rdquo; become an essential tool in my Linux toolkit. It&amp;rsquo;s a Linux kernel feature that lets you filter system calls, effectively limiting what a process can do. This is especially useful when running containers - it helps prevent a compromised container from causing damage to the host system. In this article, I&amp;rsquo;ll explore how to use seccomp to lock down container privileges in Linux.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
