lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 10 Feb 2012 19:14:14 +0100
From:	Lennart Poettering <mzerqung@...inter.de>
To:	Roberto Sassu <roberto.sassu@...ito.it>
Cc:	Mimi Zohar <zohar@...ux.vnet.ibm.com>,
	selinux@...ts.fedoraproject.org, initramfs@...r.kernel.org,
	systemd-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	Harald Hoyer <harald@...hat.com>
Subject: Re: [systemd-devel] dracut: ordering of modules

On Fri, 10.02.12 16:31, Roberto Sassu (roberto.sassu@...ito.it) wrote:

> 
> Hi Mimi
> 
> i'm CCing the systemd and Fedora SELinux mailing lists.
> 
> Unfortunately, the SELinux policy initialization (at least
> in Fedora 16) has been moved to systemd, so, now, loading an
> IMA policy cannot be done in the initial ramdisk.
> 
> Further, the SELinux policy loading code is not in a unit file
> but embedded in the main binary, which means that the new code for
> loading IMA policies must be added just after that point.
> 
> I already wrote a patch for this. I need some time to test it
> and will post in the systemd mailing list at the beginning of
> the next week.

Hmm, what is this about? You need a place to load additional security
policies into the kernel at early boot? For SELinux that indeed takes
place from within PID 1 now in systemd. I'd expect that other security
technologies like AppArmor should work the same.

If you want to hack on this basing your work on selinux-setup.c in the
systemd tree should be fairly easy.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ