From: Colin Guthrie <gmane-D409yXkIzt2rnn0nCzrM/w@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: why not install selinux with systemd being used
Date: Thu, 23 May 2013 16:45:16 +0100 [thread overview]
Message-ID: <knldi6$b78$1@ger.gmane.org> (raw)
In-Reply-To: <519C9A7C.7080904-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
'Twas brillig, and Dave Young at 22/05/13 11:14 did gyre and gimble:
> On 05/22/2013 06:13 PM, Dave Young wrote:
>> Hi, Harald
>>
>> I have a question about selinux module.
>>
>> In dracut.spec there's below code:
>>
>> %if %{defined _unitdir}
>> # with systemd IMA and selinux modules do not make sense
>> rm -fr $RPM_BUILD_ROOT/%{dracutlibdir}/modules.d/96securityfs
>> rm -fr $RPM_BUILD_ROOT/%{dracutlibdir}/modules.d/97masterkey
>> rm -fr $RPM_BUILD_ROOT/%{dracutlibdir}/modules.d/98integrity
>> rm -fr $RPM_BUILD_ROOT/%{dracutlibdir}/modules.d/98selinux
>> %endif
>>
>> I'm confused why they are excluded for systemd?
>>
>> And how can we load selinux policy in initramfs without 98selinux now?
>>
>>
> CC Vivek and Baoquan
Harald is on vacation just now I believe.
However, assuming the systemd module is being used in dracut than I
suspect that the selinux support in systemd itself is what will be used
in the initrd to ensure selinux stuff is supported.
(I would reply-all but replying via gmane which mangles email addresses
so I can't easily do so).
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited http://www.tribalogic.net/
Open Source:
Mageia Contributor http://www.mageia.org/
PulseAudio Hacker http://www.pulseaudio.org/
Trac Hacker http://trac.edgewall.org/
next prev parent reply other threads:[~2013-05-23 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 10:13 why not install selinux with systemd being used Dave Young
[not found] ` <519C9A2E.2080100-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-05-22 10:14 ` Dave Young
[not found] ` <519C9A7C.7080904-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-05-23 15:45 ` Colin Guthrie [this message]
2013-05-24 4:21 ` Dave Young
2013-05-27 11:40 ` Harald Hoyer
[not found] ` <51A34632.8040901-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-05-28 2:18 ` Dave Young
[not found] ` <51A413F4.40806-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-05-28 12:25 ` Harald Hoyer
[not found] ` <51A4A228.9000507-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-05-28 13:21 ` Vivek Goyal
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='knldi6$b78$1@ger.gmane.org' \
--to=gmane-d409yxkizt2rnn0nczrm/w@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox