From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: Yi Zhao <yi.zhao@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-selinux][PULL] refpolicy: update to 2.20190201 and git HEAD policies (2019-04-10 10:57:14 -0400)
Date: Fri, 12 Apr 2019 15:24:38 -0400 [thread overview]
Message-ID: <20190412192438.GE4054@mentor.com> (raw)
In-Reply-To: <c1864a11-0368-a0d0-85e0-f40a2436c033@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
Hi Yi,
[Re: [yocto] [meta-selinux][PULL] refpolicy: update to 2.20190201 and git HEAD policies (2019-04-10 10:57:14 -0400)] On 19.04.11 (Thu 16:19) Yi Zhao wrote:
> Hi Joe,
>
> Thank you for working on the refpolicy upgrade.
> I have a quick test with your patch. Here are the results:
>
> Machine: qemux86-64
> Image: core-image-selinux
> Init manager: systemd
> Boot command: runqemu qemux86-64 kvm nographic bootparams="selinux=1 enforcing=
> X" qemuparams="-m 1024"
>
> 1. All refpolicy type of git version can be built without problems.
>
> 2. With parameter selinux=1 & enforcing=0
> The qemu can boot up and login for all refpolicy types.
Perfect, that's what I had when testing on my reference hardware, so I'm
happy you were able to validate those results.
> 3. With parameter selinux=1 & enforcing=1
> Some of services failed to startup when booting. But this issue also exist on
> old refpolicy version (2.20170204)
Yeah, and given the scope of this change my goal was mainly parity with
the old policy but based on a version that's 2-ish years newer. So once
that's done I think we can reasonably work at enabling the additional
services in some structured way.
> 4. refpolicy stable version (2.20190201)
> I got an do_fetch error with refpolicy stable version.
> Seems the SRC_URI is not correct. It should be "https://github.com/
> SELinuxProject/refpolicy/releases/download/RELEASE_2_20190201/refpolicy-$
> {PV}.tar.bz2"
Thanks, good catch, I don't know how that slipped through. Corrected on
my end, I'll update it in a bit.
-J.
>
>
> Regards,
> Yi
--
-Joe MacDonald.
:wq
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]
next prev parent reply other threads:[~2019-04-12 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 15:53 [meta-selinux][PULL] refpolicy: update to 2.20190201 and git HEAD policies (2019-04-10 10:57:14 -0400) Joe MacDonald
2019-04-11 8:19 ` Yi Zhao
2019-04-12 19:24 ` Joe MacDonald [this message]
2019-04-14 16:26 ` Joe MacDonald
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=20190412192438.GE4054@mentor.com \
--to=joe_macdonald@mentor.com \
--cc=yi.zhao@windriver.com \
--cc=yocto@yoctoproject.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 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.