From: james.l.morris@oracle.com (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [RFC PATCH 1/5] security: Add support for SCTP security hooks
Date: Fri, 20 Oct 2017 15:53:03 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1710201551200.4174@t440> (raw)
In-Reply-To: <20171017140247.4604-1-richard_c_haines@btinternet.com>
On Tue, 17 Oct 2017, Richard Haines wrote:
> The SCTP security hooks are explained in:
> Documentation/security/LSM-sctp.txt
>
> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
> ---
> Documentation/security/LSM-sctp.txt | 212 ++++++++++++++++++++++++++++++++++++
> include/linux/lsm_hooks.h | 37 +++++++
> include/linux/security.h | 27 +++++
> security/security.c | 23 ++++
> 4 files changed, 299 insertions(+)
> create mode 100644 Documentation/security/LSM-sctp.txt
This looks ok from an LSM API pov, but note that I'm not an expert on
SCTP. It would be good to see more review from networking folk.
Reviewed-by: James Morris <james.l.morris@oracle.com>
--
James Morris
<james.l.morris@oracle.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <james.l.morris@oracle.com>
To: linux-security-module@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] security: Add support for SCTP security hooks
Date: Fri, 20 Oct 2017 04:53:03 +0000 [thread overview]
Message-ID: <alpine.LFD.2.20.1710201551200.4174@t440> (raw)
In-Reply-To: <20171017140247.4604-1-richard_c_haines@btinternet.com>
On Tue, 17 Oct 2017, Richard Haines wrote:
> The SCTP security hooks are explained in:
> Documentation/security/LSM-sctp.txt
>
> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
> ---
> Documentation/security/LSM-sctp.txt | 212 ++++++++++++++++++++++++++++++++++++
> include/linux/lsm_hooks.h | 37 +++++++
> include/linux/security.h | 27 +++++
> security/security.c | 23 ++++
> 4 files changed, 299 insertions(+)
> create mode 100644 Documentation/security/LSM-sctp.txt
This looks ok from an LSM API pov, but note that I'm not an expert on
SCTP. It would be good to see more review from networking folk.
Reviewed-by: James Morris <james.l.morris@oracle.com>
--
James Morris
<james.l.morris@oracle.com>
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <james.l.morris@oracle.com>
To: Richard Haines <richard_c_haines@btinternet.com>
Cc: selinux@tycho.nsa.gov, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org,
linux-security-module@vger.kernel.org, paul@paul-moore.com,
vyasevich@gmail.com, nhorman@tuxdriver.com, sds@tycho.nsa.gov,
eparis@parisplace.org, marcelo.leitner@gmail.com
Subject: Re: [RFC PATCH 1/5] security: Add support for SCTP security hooks
Date: Fri, 20 Oct 2017 15:53:03 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1710201551200.4174@t440> (raw)
In-Reply-To: <20171017140247.4604-1-richard_c_haines@btinternet.com>
On Tue, 17 Oct 2017, Richard Haines wrote:
> The SCTP security hooks are explained in:
> Documentation/security/LSM-sctp.txt
>
> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
> ---
> Documentation/security/LSM-sctp.txt | 212 ++++++++++++++++++++++++++++++++++++
> include/linux/lsm_hooks.h | 37 +++++++
> include/linux/security.h | 27 +++++
> security/security.c | 23 ++++
> 4 files changed, 299 insertions(+)
> create mode 100644 Documentation/security/LSM-sctp.txt
This looks ok from an LSM API pov, but note that I'm not an expert on
SCTP. It would be good to see more review from networking folk.
Reviewed-by: James Morris <james.l.morris@oracle.com>
--
James Morris
<james.l.morris@oracle.com>
next prev parent reply other threads:[~2017-10-20 4:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 14:02 [RFC PATCH 1/5] security: Add support for SCTP security hooks Richard Haines
2017-10-17 14:02 ` Richard Haines
2017-10-17 14:02 ` Richard Haines
2017-10-20 4:53 ` James Morris [this message]
2017-10-20 4:53 ` James Morris
2017-10-20 4:53 ` James Morris
2017-10-31 16:41 ` Marcelo Ricardo Leitner
2017-10-31 16:41 ` Marcelo Ricardo Leitner
2017-10-31 16:41 ` Marcelo Ricardo Leitner
2017-11-01 21:38 ` Richard Haines
2017-11-01 21:38 ` Richard Haines
2017-11-01 21:38 ` Richard Haines
2017-11-06 22:35 ` Paul Moore
2017-11-06 22:35 ` Paul Moore
2017-11-06 22:35 ` 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=alpine.LFD.2.20.1710201551200.4174@t440 \
--to=james.l.morris@oracle.com \
--cc=linux-security-module@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 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.