<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Conmon on *scratch*</title>
    <link>https://www.scrivano.org/tags/conmon/</link>
    <description>Recent content in Conmon on *scratch*</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 06 Jun 2026 10:03:54 +0000</lastBuildDate>
    <atom:link href="https://www.scrivano.org/tags/conmon/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Playing with seccomp notifications in the OCI runtime</title>
      <link>https://www.scrivano.org/posts/2020-08-10-seccomp-notifications/</link>
      <pubDate>Mon, 10 Aug 2020 10:40:19 +0200</pubDate>
      <guid>https://www.scrivano.org/posts/2020-08-10-seccomp-notifications/</guid>
      <description>&lt;p&gt;A couple weekends ago I&amp;rsquo;ve played with seccomp user notifications and how they can be used in the OCI containers stack. Seccomp user notifications are a Linux kernel feature that lets a privileged monitor process intercept specific syscalls made by a less-privileged container, inspect the arguments, and either emulate the syscall or return an error. This opens up possibilities for safely expanding what unprivileged containers can do — for example, emulating &lt;code&gt;mknod&lt;/code&gt; — without granting broad kernel capabilities to the container itself.&lt;/p&gt;&#xA;&lt;p&gt;Seccomp user notifications are a powerful Linux kernel feature, that&#xA;delegates syscalls handling to a userland program.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
