mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Colin Guthrie <gmane-D409yXkIzt2rnn0nCzrM/w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: why not install selinux with systemd being used
Date: Fri, 24 May 2013 12:21:19 +0800	[thread overview]
Message-ID: <519EEABF.7070401@redhat.com> (raw)
In-Reply-To: <knldi6$b78$1@ger.gmane.org>

On 05/23/2013 11:45 PM, Colin Guthrie wrote:
> '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 did not see initramfs related selinux policy loading in systemd code.

Under rd.break=pre-pivot:
pre-pivot:/# /sysroot/usr/sbin/sestatus
SELinux status: disabled

> 
> (I would reply-all but replying via gmane which mangles email addresses
> so I can't easily do so).
> 
> Col
> 
> 


-- 
Thanks
Dave


  reply	other threads:[~2013-05-24  4:21 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
2013-05-24  4:21         ` Dave Young [this message]
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=519EEABF.7070401@redhat.com \
    --to=dyoung-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=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