From: Richard Haines <richard_c_haines@btinternet.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: selinux@tycho.nsa.gov, linux-sctp@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] kernel: Add SELinux SCTP protocol support
Date: Fri, 16 Dec 2016 13:31:53 +0000 [thread overview]
Message-ID: <1481895113.5152.5.camel@btinternet.com> (raw)
In-Reply-To: <78b647ff-2c25-8207-f1cc-4c13dbed53fd@schaufler-ca.com>
On Wed, 2016-12-14 at 09:02 -0800, Casey Schaufler wrote:
> On 12/14/2016 5:39 AM, Richard Haines wrote:
> > Add SELinux support for the SCTP protocol. The SELinux-sctp.txt
> > document
> > describes how the patch has been implemented with an example policy
> > and
> > tests using lkstcp-tools.
>
> Please separate the LSM support from the SELinux support
> into patches 1/2 and 2/2 respectively. The documentation
> needs to be separated along the same lines as well. While
> I am only mildly concerned about the SELinux implementation
> I am very concerned about the LSM side.
>
>
Thanks for your comments. I do not see a problem with
resolving them all in the next RFC patch.
next prev parent reply other threads:[~2016-12-16 13:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 13:39 [RFC PATCH 1/1] kernel: Add SELinux SCTP protocol support Richard Haines
2016-12-14 13:39 ` Richard Haines
2016-12-14 14:01 ` David Laight
2016-12-16 13:40 ` Marcelo Ricardo Leitner
2016-12-16 13:40 ` Marcelo Ricardo Leitner
2016-12-21 12:26 ` Richard Haines
2016-12-14 17:02 ` Casey Schaufler
2016-12-14 17:02 ` Casey Schaufler
2016-12-16 13:31 ` Richard Haines [this message]
2016-12-14 18:34 ` Stephen Smalley
2016-12-14 18:34 ` Stephen Smalley
2017-01-23 13:19 ` Richard Haines
2017-01-23 13:19 ` Richard Haines
2017-01-23 18:58 ` marcelo.leitner
2017-01-23 18:58 ` marcelo.leitner
2016-12-21 16:09 ` Marcelo Ricardo Leitner
2016-12-21 16:09 ` Marcelo Ricardo Leitner
2017-02-06 14:30 ` Richard Haines
2017-02-06 14:30 ` 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=1481895113.5152.5.camel@btinternet.com \
--to=richard_c_haines@btinternet.com \
--cc=casey@schaufler-ca.com \
--cc=linux-sctp@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@tycho.nsa.gov \
/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.