From: Patrick Ohly <patrick.ohly@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-security][PATCH 2/2] smack kernel: add smack kernel config fragments
Date: Fri, 28 Oct 2016 13:20:25 +0200 [thread overview]
Message-ID: <1477653625.13356.24.camel@intel.com> (raw)
In-Reply-To: <92CF3B90-4DED-4513-BDD0-9BB116E476B8@gmail.com>
On Thu, 2016-10-27 at 19:32 -0700, Khem Raj wrote:
> > On Oct 27, 2016, at 12:22 AM, Patrick Ohly <patrick.ohly@intel.com> wrote:
> > Can you say a bit more about your plans regarding Smack support in
> > meta-security? A recipe for the userspace tool and the kernel config is
> > a start, but for a fully functional Smack-enabled image, the rootfs also
> > needs to be set up a bit differently.
>
> FWIW meta-security seems to be right place for smack related infra.
I don't disagree :-) But it would be good to know more about the rest of
the infrastructure before adding (or reviewing) bits and pieces that by
themselves don't do much.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2016-10-28 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 15:00 [meta-security][PATCH 1/2] smack: Add new package Armin Kuster
2016-10-26 15:00 ` [meta-security][PATCH 2/2] smack kernel: add smack kernel config fragments Armin Kuster
2016-10-27 7:22 ` Patrick Ohly
2016-10-28 2:32 ` Khem Raj
2016-10-28 11:20 ` Patrick Ohly [this message]
2016-10-28 15:41 ` akuster808
2016-10-28 17:54 ` Khem Raj
2016-10-28 2:29 ` [meta-security][PATCH 1/2] smack: Add new package Khem Raj
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=1477653625.13356.24.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=raj.khem@gmail.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.