From: Richard Haines <richard_c_haines@btinternet.com>
To: Paul Moore <paul@paul-moore.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: Sat, 23 Jan 2021 13:39:58 +0000 [thread overview]
Message-ID: <beff39b090e852de30059d8c9b3f8914011363ae.camel@btinternet.com> (raw)
In-Reply-To: <CAHC9VhRXyA-g929Z+eam-gmYpzD=LeJV2W548_3GkHRyrZY0vw@mail.gmail.com>
On Fri, 2021-01-22 at 17:20 -0500, Paul Moore wrote:
> 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.
>
No not yet. I plan to post new version on Monday after I've done a few
minor updates.
prev parent reply other threads:[~2021-01-23 13:40 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
2021-01-23 13:39 ` Richard Haines [this message]
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=beff39b090e852de30059d8c9b3f8914011363ae.camel@btinternet.com \
--to=richard_c_haines@btinternet.com \
--cc=dominick.grift@defensec.nl \
--cc=paul@paul-moore.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).