From: Khem Raj <raj.khem@gmail.com>
To: akuster808 <akuster808@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 10:54:31 -0700 [thread overview]
Message-ID: <9B58E66E-926B-49F6-AB9F-43C24F45C0CC@gmail.com> (raw)
In-Reply-To: <a591d19f-7aac-c3f0-856c-3186d618efeb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
> On Oct 28, 2016, at 8:41 AM, akuster808 <akuster808@gmail.com> wrote:
>
>
>
> On 10/28/2016 04:20 AM, Patrick Ohly wrote:
>> 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.
> I start of with basic support and refine over time. Your statement can apply for many components within meta-secuirty. I recently started adding test images. Providing configurations or solutions for a niche area is outside the scope for this general layer, IMHO. I could be convinced otherwise. I tend not to wait for 100% solution before sending out bits for review.
its a good start. If you have some more patches on the way to complete
the solution, that would be good to share.
>
> thanks for your input.
>
> Regards,
> Armin
>>
>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-10-28 17:54 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
2016-10-28 15:41 ` akuster808
2016-10-28 17:54 ` Khem Raj [this message]
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=9B58E66E-926B-49F6-AB9F-43C24F45C0CC@gmail.com \
--to=raj.khem@gmail.com \
--cc=akuster808@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.