From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/xen: explicitly disable checkpolicy logic
Date: Tue, 21 Jan 2020 22:45:41 +0100 [thread overview]
Message-ID: <8736c8zdoa.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <564b6b88-967f-f541-1368-2a515fc881af@mind.be> (Arnout Vandecappelle's message of "Tue, 21 Jan 2020 22:29:32 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> On 19/01/2020 18:03, Peter Korsgaard wrote:
>> Fixes:
>> http://autobuild.buildroot.net/results/14af2dc3219847a92c6ec2db14ba387159b61fde
>>
>> The Xen build system builds and embeds a default XSM FLASK (Flux Advanced
>> Security Kernel) security policy if it detects SELinux checkpolicy on the
>> build machine.
>>
>> If enabled, a gen-policy.py python script is used to convert the binary
>> FLASK policy to a C array initialization list to embed it in the Xen binary.
>> Depending on the python version and locale available on the host, this fails
> The more appropriate thing to do would be to:
> - set this XEN_HAS_CHECKPOLICY=n if selinux is disabled;
> - do not set it when selinux is enabled, and depend on host-checkpolicy
Yes, that can be done in the future by someone interested in xen with
XSM/selinux support.
> - depend on host-python
> - set LC_ALL=C
Hmm, where are we setting LC_ALL=C in the package build step?
> However, the latter two are already done. So except for incorrectly detecting
> checkpolicy installed on the system, I wonder what is really triggering this
> issue...
I was also unable to reproduce the issue locally, but given the > 255
byte values I assume it is related to locale. Looking at the issue I
noticed the invalid checkpolicy logic and that disabling it would get
rid of the entire code path.
But I am fine with people sending patches to improve it. I don't use Xen
myself, I only looked at the build issues while doing security support
and noticed they have been occuring for quite a long time.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-01-21 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 17:03 [Buildroot] [PATCH 1/3] package/xen: explicitly disable checkpolicy logic Peter Korsgaard
2020-01-19 17:03 ` [Buildroot] [PATCH 2/3] package/xen: security bump to version 4.12.2 Peter Korsgaard
2020-01-20 0:26 ` Alistair Francis
2020-01-20 7:39 ` Peter Korsgaard
2020-03-05 20:25 ` Peter Korsgaard
2020-01-19 17:03 ` [Buildroot] [PATCH 3/3] package/xen: add upstream security fix for XSA-312 Peter Korsgaard
2020-01-20 0:28 ` Alistair Francis
2020-01-20 7:39 ` Peter Korsgaard
2020-03-05 20:25 ` Peter Korsgaard
2020-01-20 0:23 ` [Buildroot] [PATCH 1/3] package/xen: explicitly disable checkpolicy logic Alistair Francis
2020-01-20 7:39 ` Peter Korsgaard
2020-01-21 21:29 ` Arnout Vandecappelle
2020-01-21 21:45 ` Peter Korsgaard [this message]
2020-01-22 7:57 ` Arnout Vandecappelle
2020-03-05 20:21 ` Peter Korsgaard
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=8736c8zdoa.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.