From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] audit2allow BR support
Date: Thu, 16 Jul 2020 11:05:24 +0200 [thread overview]
Message-ID: <20200716110524.5214d23a@windsurf.home> (raw)
In-Reply-To: <159488904315.3198.6229972988341724924@kwain>
On Thu, 16 Jul 2020 10:44:03 +0200
Antoine Tenart <antoine.tenart@bootlin.com> wrote:
> > Which Python version have you chosen ? Python 3.x or Python 2.x, i.e
> > BR2_PACKAGE_PYTHON=y or BR2_PACKAGE_PYTHON3=y ?
>
> I did not encounter such an issue, but I only used versions 3.0+. If I
> think about something, I'll let you know.
Hm, I see that package/selinux-python/Config.in has:
depends on !BR2_PACKAGE_PYTHON
select BR2_PACKAGE_PYTHON3
so anyway, this is all only Python 3.x.
So yeah, I'm not sure how Tomas got into this build issue. Tomas: could
share the Buildroot .config being used ?
> > > 2- /var/lib/selinux directory missing
> > > $ semodule -llibsemanage.semanage_create_store: Could not create module store at /var/lib/selinux/targeted. (No such file or directory).libsemanage.semanage_direct_connect: could not establish direct connection (No such file or directory).semodule: Could not connect to policy handler
> > > ls /var/lib/selinuxls: /var/lib/selinux: No such file or directory
> > > ==> looks like the directory can just be added
> >
> > On this one, I'm not sure, would need testing. I don't immediately see
> > anything creating /var/lib/selinux in Buildroot, so if it's not done by
> > the build system of one the SELinux packages, indeed /var/lib/selinux
> > will be missing.
> >
> > Antoine: you are working on building systems with SELinux supports, did
> > you face the /var/lib/selinux missing problem ? Or perhaps because
> > you're testing with systemd, the situation is different ?
>
> Using a modular policy at runtime isn't supported by the current
> refpolicy support in BR. When playing with it, I had similar issues with
> directories missing. Also, I don't think adding those directories alone
> will make it working, there's probably more work to do.
How could have Tomas encountered this with the current Buildroot, where
we don't even have the logic to build a modular policy ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-07-16 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5696376.2474933.1594878993118.ref@mail.yahoo.com>
2020-07-16 5:56 ` [Buildroot] audit2allow BR support Tomas V. Arredondo
2020-07-16 7:45 ` Thomas Petazzoni
2020-07-16 8:44 ` Antoine Tenart
2020-07-16 9:05 ` Thomas Petazzoni [this message]
2020-07-16 9:20 ` Tomas V. Arredondo
2020-07-16 10:45 ` Tomas V. Arredondo
2020-07-16 12:26 ` Antoine Tenart
2020-07-16 20:49 ` Tomas V. Arredondo
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=20200716110524.5214d23a@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.