selinux-refpolicy.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Richard Haines <richard_c_haines@btinternet.com>
Cc: selinux@vger.kernel.org, selinux-refpolicy@vger.kernel.org
Subject: Re: [PATCH] selinux-notebook: Add new section for Embedded Systems
Date: Wed, 27 Jan 2021 22:25:17 -0500	[thread overview]
Message-ID: <CAHC9VhSkuL2eUaBQYQBHEmy3OPP+vSmEVT9Eh0PTx8t4DZ5nJA@mail.gmail.com> (raw)
In-Reply-To: <20210127153303.135235-1-richard_c_haines@btinternet.com>

On Wed, Jan 27, 2021 at 10:33 AM Richard Haines
<richard_c_haines@btinternet.com> wrote:
>
> Add a new section and supporting examples for embedded systems.
>
> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
> ---
> Changes from RFC version: Added comments from Dominick, minor text updates
> and rework example Makefiles.
>
>  src/embedded_systems.md                       | 546 ++++++++++++++++++
>  src/implementing_seaware_apps.md              |   2 +-
>  .../embedded-policy/android-policy/README.md  |  34 ++
>  .../android-policy/android-10/Makefile        |  42 ++
>  .../android-policy/android-4/Makefile         |  31 +
>  .../android-policy/brillo-device/Makefile     |  46 ++
>  .../android-policy/brillo/Makefile            |  38 ++
>  .../reference-policy/README.md                |   6 +
>  .../reference-policy/build.conf               |  84 +++
>  .../reference-policy/modules.conf             | 236 ++++++++
>  src/seandroid.md                              |  12 +-
>  src/section_list.txt                          |   1 +
>  src/toc.md                                    |   1 +
>  13 files changed, 1074 insertions(+), 5 deletions(-)
>  create mode 100644 src/embedded_systems.md
>  create mode 100644 src/notebook-examples/embedded-policy/android-policy/README.md
>  create mode 100644 src/notebook-examples/embedded-policy/android-policy/android-10/Makefile
>  create mode 100644 src/notebook-examples/embedded-policy/android-policy/android-4/Makefile
>  create mode 100644 src/notebook-examples/embedded-policy/android-policy/brillo-device/Makefile
>  create mode 100644 src/notebook-examples/embedded-policy/android-policy/brillo/Makefile
>  create mode 100644 src/notebook-examples/embedded-policy/reference-policy/README.md
>  create mode 100644 src/notebook-examples/embedded-policy/reference-policy/build.conf
>  create mode 100644 src/notebook-examples/embedded-policy/reference-policy/modules.conf

This is great guys - thank you!

-- 
paul moore
www.paul-moore.com

  reply	other threads:[~2021-01-28  3:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 15:33 [PATCH] selinux-notebook: Add new section for Embedded Systems Richard Haines
2021-01-28  3:25 ` Paul Moore [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-25 11:24 Richard Haines
2021-02-09 17:38 ` Dominick Grift
2021-02-10 15:01   ` Richard Haines
2021-02-11  0:30     ` Paul Moore

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=CAHC9VhSkuL2eUaBQYQBHEmy3OPP+vSmEVT9Eh0PTx8t4DZ5nJA@mail.gmail.com \
    --to=paul@paul-moore.com \
    --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).