From: Paul Moore <paul@paul-moore.com>
To: Richard Haines <richard_c_haines@btinternet.com>
Cc: Dominick Grift <dominick.grift@defensec.nl>,
selinux@vger.kernel.org, selinux-refpolicy@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] selinux-notebook: Add new section for Embedded Systems
Date: Fri, 22 Jan 2021 17:20:59 -0500 [thread overview]
Message-ID: <CAHC9VhRXyA-g929Z+eam-gmYpzD=LeJV2W548_3GkHRyrZY0vw@mail.gmail.com> (raw)
In-Reply-To: <8776cbb2687a09ed5b4e5b3cf0c50ade6c018fa6.camel@btinternet.com>
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
next prev parent reply other threads:[~2021-01-22 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 10:57 [RFC PATCH 0/1] selinux-notebook: Add new section for Embedded Systems Richard Haines
2021-01-19 10:57 ` [RFC PATCH 1/1] " Richard Haines
2021-01-19 13:18 ` Dominick Grift
2021-01-20 11:55 ` Richard Haines
2021-01-22 22:20 ` Paul Moore [this message]
2021-01-23 13:39 ` Richard Haines
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='CAHC9VhRXyA-g929Z+eam-gmYpzD=LeJV2W548_3GkHRyrZY0vw@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=dominick.grift@defensec.nl \
--cc=richard_c_haines@btinternet.com \
--cc=selinux-refpolicy@vger.kernel.org \
--cc=selinux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).