Received-SPF: pass (google.com: domain of selinux-refpolicy-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210119105747.9680-1-richard_c_haines@btinternet.com>
 <20210119105747.9680-2-richard_c_haines@btinternet.com> <ypjleeihm5e0.fsf@defensec.nl>
 <8776cbb2687a09ed5b4e5b3cf0c50ade6c018fa6.camel@btinternet.com>
In-Reply-To: <8776cbb2687a09ed5b4e5b3cf0c50ade6c018fa6.camel@btinternet.com>
From:   Paul Moore <paul@paul-moore.com>
Date:   Fri, 22 Jan 2021 17:20:59 -0500
Message-ID: <CAHC9VhRXyA-g929Z+eam-gmYpzD=LeJV2W548_3GkHRyrZY0vw@mail.gmail.com>
Subject: Re: [RFC PATCH 1/1] selinux-notebook: Add new section for Embedded Systems
To:     Richard Haines <richard_c_haines@btinternet.com>
Cc:     Dominick Grift <dominick.grift@defensec.nl>,
        selinux@vger.kernel.org, selinux-refpolicy@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, Jan 20, 2021 at 7:37 AM Richard Haines
<richard_c_haines@btinternet.com> wrote:
> On Tue, 2021-01-19 at 14:18 +0100, Dominick Grift wrote:
> > Richard Haines <richard_c_haines@btinternet.com> writes:
> >
> > > Add a new section and supporting examples for embedded systems.
> >
> > Nice initiative, thanks. Looks pretty solid for a first iteration.
> >
> > I wrote a document for OpenWrt here [1]. Basically the instructions
> > needed
> > to assemble OpenWrt from modules applicable to a particular system,
> > but also how
> > to build on top of it, or now to just fork it so that you can use it
> > as
> > a base for your own policy.
> >
> > [1]
> > https://github.com/doverride/openwrt-selinux-policy/blob/master/README.md
> >
> > I am currently pretty happy with the results so far (its a work in
> > progress, and there are known loose ends)
> >
> > One of the differences compared with android is that SELinux is not
> > tightly integrated in OpenWrt, and so most of the tough aspects are
> > addressed in policy
> > rather than adding selinux-awareness all over. SELinux in OpenWrt is
> > therefore
> > fairly self-contained and considering the challenges fairly robust.
> >
>
> Thanks, I've worked these comments into the next version.

I just wanted to check and make sure this next version hasn't been
posted to the list yet?  Sometimes the list eats things and I wanted
to make sure that wasn't the case here.

-- 
paul moore
www.paul-moore.com