public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Paul Holzinger <pholzing@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] selinux: Allow passt to use setgid and setuid capabilities in namespace
Date: Fri, 2 Oct 2026 12:13:10 +0200	[thread overview]
Message-ID: <62775387-4e00-43c6-9ce8-6ea5da4616c9@redhat.com> (raw)
In-Reply-To: <20261002070045.2065145-1-sbrivio@redhat.com>


On 02/10/2026 09:00, Stefano Brivio wrote:
> Starting from commit 7bf1595c9242 ("isolation: Don't create our userns
> as nobody"), we unconditionally set uidmap and gidmap in the detached
> user namespace.
>
> Allow that in SELinux rules. We also need to allow explicit access to
> the related files.
>
> While at it, add the matching class requirements in pasta.te, which I
> forgot (harmless as they were indirectly required, but not really
> correct).
>
> Link: https://bodhi.fedoraproject.org/updates/FEDORA-2026-3a8fb909da#comment-4790590
> Fixes: 71b74e924426 ("isolation: Don't create our userns as nobody")
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> ---
>   ...pen-permissions-on-netns-directory-o.patch |  72 +++++
>   contrib/selinux/passt.te                      |   7 +-
>   contrib/selinux/pasta.te                      |   2 +-
>   contrib/selinux/pasta.te.orig                 | 266 ++++++++++++++++++
>   4 files changed, 344 insertions(+), 3 deletions(-)
>   create mode 100644 contrib/selinux/0001-selinux-Enable-open-permissions-on-netns-directory-o.patch
>   create mode 100644 contrib/selinux/pasta.te.orig
I assume these two new files are not meant to be committed/part of this 
patch?


  reply	other threads:[~2026-10-02 10:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  7:00 Stefano Brivio
2026-10-02 10:13 ` Paul Holzinger [this message]
2026-10-02 10:31   ` Stefano Brivio

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=62775387-4e00-43c6-9ce8-6ea5da4616c9@redhat.com \
    --to=pholzing@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).