All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: yocto-patches@lists.yoctoproject.org
Subject: [pseudo][PATCH 0/6] Add landlock support, fix seccomp
Date: Thu, 12 Nov 2026 10:19:52 -0600	[thread overview]
Message-ID: <1794500398-31706-1-git-send-email-mark.hatle@kernel.crashing.org> (raw)

The first 3 changes add support for landlock.  This was recently
reported by Richard Tollerton that xz on arch linux was now using
landlock and breaking pseudo invocations.  The first patch is a
test case, second patch moves to using /proc instead of a chdir
(with fallback to prior behavior) and third patch intercepts the
syscall and avoids landlock.  This was implemented as a belt and
suspenders type approach, as there have been instances of similar
software in the past using non-standard ways to activate.

During review and testing, it was observed that the prctl/seccomp
implementation was incomplete.  Add tests, and then fix the
existing implementation.

Mark Hatle (6):
  test-landlock: Add a Landlock sandbox test
  pseudo_client: Connect to the server without changing directory
  ports/linux/pseudo_wrappers: Report Landlock as unsupported
  test-seccomp: Check that seccomp is never really enabled
  ports/linux/pseudo_wrappers: Fake seccomp filters set by prctl()
  ports/linux/pseudo_wrappers: Fake seccomp strict mode in syscall()

 README.security               |  14 ++++
 ports/linux/pseudo_wrappers.c |  29 +++++++--
 pseudo_client.c               |  77 +++++++++++++++-------
 test/test-landlock.c          | 146 ++++++++++++++++++++++++++++++++++++++++++
 test/test-landlock.sh         |  24 +++++++
 test/test-seccomp.c           | 121 ++++++++++++++++++++++++++++++++++
 test/test-seccomp.sh          |  12 ++++
 7 files changed, 395 insertions(+), 28 deletions(-)
 create mode 100644 test/test-landlock.c
 create mode 100755 test/test-landlock.sh
 create mode 100644 test/test-seccomp.c
 create mode 100755 test/test-seccomp.sh

-- 
1.8.3.1


             reply	other threads:[~2026-11-12 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 16:19 Mark Hatle [this message]
2026-11-12 16:19 ` [pseudo][PATCH 1/6] test-landlock: Add a Landlock sandbox test Mark Hatle
2026-11-12 16:19 ` [pseudo][PATCH 2/6] pseudo_client: Connect to the server without changing directory Mark Hatle
2026-11-12 16:19 ` [pseudo][PATCH 3/6] ports/linux/pseudo_wrappers: Report Landlock as unsupported Mark Hatle
2026-11-12 16:19 ` [pseudo][PATCH 4/6] test-seccomp: Check that seccomp is never really enabled Mark Hatle
2026-11-12 16:19 ` [pseudo][PATCH 5/6] ports/linux/pseudo_wrappers: Fake seccomp filters set by prctl() Mark Hatle
2026-11-12 16:19 ` [pseudo][PATCH 6/6] ports/linux/pseudo_wrappers: Fake seccomp strict mode in syscall() Mark Hatle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1794500398-31706-1-git-send-email-mark.hatle@kernel.crashing.org \
    --to=mark.hatle@kernel.crashing.org \
    --cc=yocto-patches@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.