From: Paul Moore <paul@paul-moore.com>
To: "Christian Göttsche" <cgoettsche@seltendoof.de>, selinux@vger.kernel.org
Cc: "Christian Göttsche" <cgzones@googlemail.com>,
"Stephen Smalley" <stephen.smalley.work@gmail.com>,
"Ondrej Mosnacek" <omosnace@redhat.com>,
"Thiébaud Weksteen" <tweek@google.com>,
"Bram Bonné" <brambonne@google.com>,
"Casey Schaufler" <casey@schaufler-ca.com>,
"Canfeng Guo" <guocanfeng@uniontech.com>,
"GUO Zihua" <guozihua@huawei.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selinux: support wildcard network interface names
Date: Fri, 07 Mar 2025 15:11:09 -0500 [thread overview]
Message-ID: <c53b73fccbc24586776e9240a14dc6b3@paul-moore.com> (raw)
In-Reply-To: <20250302154100.104746-1-cgoettsche@seltendoof.de>
On Mar 2, 2025 =?UTF-8?q?Christian=20G=C3=B6ttsche?= <cgoettsche@seltendoof.de> wrote:
>
> Add support for wildcard matching of network interface names. This is
> useful for auto-generated interfaces, for example podman creates network
> interfaces for containers with the naming scheme podman0, podman1,
> podman2, ...
>
> To maintain backward compatibility guard this feature with a new policy
> capability 'netif_wildcard'.
>
> Netifcon definitions are compared against in the order given by the
> policy, so userspace tools should sort them in a reasonable order.
>
> Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
> ---
> v2: add policy capability netif_wildcard
> ---
> security/selinux/include/policycap.h | 1 +
> security/selinux/include/policycap_names.h | 1 +
> security/selinux/include/security.h | 8 +++++++-
> security/selinux/ss/services.c | 16 +++++++++++++---
> 4 files changed, 22 insertions(+), 4 deletions(-)
Looks good, merged into selinux/dev, thanks!
--
paul-moore.com
prev parent reply other threads:[~2025-03-07 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 15:40 Christian Göttsche
2025-03-07 20:11 ` Paul Moore [this message]
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=c53b73fccbc24586776e9240a14dc6b3@paul-moore.com \
--to=paul@paul-moore.com \
--cc=brambonne@google.com \
--cc=casey@schaufler-ca.com \
--cc=cgoettsche@seltendoof.de \
--cc=cgzones@googlemail.com \
--cc=guocanfeng@uniontech.com \
--cc=guozihua@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=tweek@google.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®