From: Paul Moore <paul@paul-moore.com>
To: Igor Baranov <igor.baranov@huawei.com>
Cc: hw.likun@huawei.com, jamorris@linux.microsoft.com,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
stephen.smalley.work@gmail.com, xiujianfeng@huawei.com,
alexander.kozhevnikov@huawei.com, yusongping@huawei.com,
artem.kuzin@huawei.com
Subject: Re: [RFC PATCH 0/1] SELinux-namespaces
Date: Wed, 16 Feb 2022 15:47:27 -0500 [thread overview]
Message-ID: <CAHC9VhTDu1GDxJwFg5gAMWhuMKUWEU5eXuTr_6eG=tGwiGsMTw@mail.gmail.com> (raw)
In-Reply-To: <20220216125206.20975-1-igor.baranov@huawei.com>
On Wed, Feb 16, 2022 at 7:52 AM Igor Baranov <igor.baranov@huawei.com> wrote:
>
> Hi all!
> Our team at Huawei decided to revive the work on SELinux namespaces.
> We took https://github.com/stephensmalley/selinux-kernel/tree/working-selinuxns
> as a basis with some patches from selinuxns-xattr.
Hello!
For reference there is a *slightly* more recent forward port of those
patches in the main SELinux repo under the working-selinuxns branch.
I haven't forward ported those patches since v5.10-rc1 as there are
some rather significant technical hurdles around persistent object
labeling which I don't believe have been adequately resolved yet. The
prefixed/namespaces xattr approach that you mention above may work for
a limited number of namespaces, but I worry there is a scalability
issue that needs to be resolved; we can't simply keep adding xattrs to
inodes.
* https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
Also, are there rest of your patches online anywhere? Patch 1/1 isn't
very interesting on its own.
--
paul-moore.com
next prev parent reply other threads:[~2022-02-16 20:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22c0d7a1-b658-64ce-f099-0b3617ef8e38@huawei.com>
[not found] ` <CAEjxPJ5-w83HMRGuDHHqMthkju3bxT0gZ-EiiTE=t5UhQqQ_ug@mail.gmail.com>
2021-07-19 13:54 ` issues about selinux namespace xiujianfeng
2021-07-20 2:56 ` Paul Moore
2021-07-21 13:12 ` xiujianfeng
2022-02-16 12:52 ` [RFC PATCH 0/1] SELinux-namespaces Igor Baranov
2022-02-16 12:52 ` [RFC PATCH 1/1] selinuxns: Replace state pointer with namespace id Igor Baranov
2022-02-16 17:08 ` [RFC PATCH 0/1] SELinux-namespaces Casey Schaufler
2022-02-16 20:47 ` Paul Moore [this message]
2022-04-18 9:45 ` [RFC PATCH 0/7] SELinux-namespace Alexander Kozhevnikov
2022-04-18 9:45 ` [RFC PATCH 1/7] LSM: Infrastructure management of the superblock Alexander Kozhevnikov
2022-04-18 9:45 ` [RFC PATCH 2/7] selinux: support per-namespace superblock security structures Alexander Kozhevnikov
2022-04-18 9:45 ` [RFC PATCH 3/7] SELINUXNS: Fix initilization of the superblock security under spinlock Alexander Kozhevnikov
2022-04-18 9:45 ` [RFC PATCH 4/7] SELINUXNS: Namespacing for xattrs Alexander Kozhevnikov
2022-04-18 9:45 ` [RFC PATCH 5/7] SELINUXNS: Migrate all open files and all vma to new namespace Alexander Kozhevnikov
2022-04-18 9:45 ` [RFC PATCH 6/7] SELINUXNS: Fixing superblock security structure memory leakage Alexander Kozhevnikov
2022-04-18 9:45 ` [RFC PATCH 7/7] SELINUXNS: Fixing concurrency issues Alexander Kozhevnikov
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='CAHC9VhTDu1GDxJwFg5gAMWhuMKUWEU5eXuTr_6eG=tGwiGsMTw@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=alexander.kozhevnikov@huawei.com \
--cc=artem.kuzin@huawei.com \
--cc=hw.likun@huawei.com \
--cc=igor.baranov@huawei.com \
--cc=jamorris@linux.microsoft.com \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=xiujianfeng@huawei.com \
--cc=yusongping@huawei.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;
as well as URLs for NNTP newsgroup(s).