From: Paul Moore <paul@paul-moore.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: <selinux@vger.kernel.org>,
<linux-security-module@vger.kernel.org>,
Roberto Sassu <roberto.sassu@huawei.com>,
initramfs <initramfs@vger.kernel.org>
Subject: Re: [GIT PULL] SELinux patches for v5.5
Date: Mon, 02 Dec 2019 21:14:53 -0500 [thread overview]
Message-ID: <16ec989f948.27df.85c95baa4474aabc7814e68940a78392@paul-moore.com> (raw)
In-Reply-To: <1575338427.4793.486.camel@linux.ibm.com>
On December 2, 2019 9:00:35 PM Mimi Zohar <zohar@linux.ibm.com> wrote:
> On Mon, 2019-12-02 at 15:04 -0500, Paul Moore wrote:
>> On Mon, Dec 2, 2019 at 10:58 AM Mimi Zohar <zohar@linux.ibm.com> wrote:
>>> [Truncated Cc list, adding Roberto and the initramfs mailing list]
>>>
>>> Hi Paul,
>>>
>>> On Tue, 2019-11-26 at 16:24 -0500, Paul Moore wrote:
>>>
>>>> - Allow file labeling before the policy is loaded. This should ease
>>>> some of the burden when the policy is initially loaded (no need to
>>>> relabel files), but it should also help enable some new system
>>>> concepts which dynamically create the root filesystem in the initrd.
>>>
>>> Any chance you're planning on using Roberto's patches for including
>>> security xattrs in the initramfs?[1]
>>> [1] https://www.spinics.net/lists/linux-initramfs/msg04771.html
>>
>> I'm assuming you're not asking about me personally? ;)
>
> No, of course not. I was wondering if "help enable some new system
> concepts which dynamically create the root filesystem in the initrd"
> adds SELinux labels on the root filesystem.
Once again, that is more of a distro specific question.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2019-12-03 2:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 21:24 [GIT PULL] SELinux patches for v5.5 Paul Moore
2019-12-01 1:40 ` pr-tracker-bot
2019-12-02 15:58 ` Mimi Zohar
2019-12-02 20:04 ` Paul Moore
2019-12-03 2:00 ` Mimi Zohar
2019-12-03 2:14 ` Paul Moore [this message]
2019-12-03 7:57 ` Roberto Sassu
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=16ec989f948.27df.85c95baa4474aabc7814e68940a78392@paul-moore.com \
--to=paul@paul-moore.com \
--cc=initramfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=selinux@vger.kernel.org \
--cc=zohar@linux.ibm.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).