From: Paul Moore <paul.moore@hp.com>
To: dccp@vger.kernel.org
Subject: Re: [PATCH RFC] SELinux support for DCCP
Date: Mon, 13 Nov 2006 20:54:13 +0000 [thread overview]
Message-ID: <4558DB75.9020608@hp.com> (raw)
In-Reply-To: <XMMS.LNX.4.64.0611110203540.25507@d.namei>
Paul Moore wrote:
> Based on my simple understanding of DCCP it looks okay to me, i.e. all the
> relevant things we do for TCP seem to be done now for DCCP. Also, I don't think
> adding labeled networking support should be all that difficult; basically we
> would need to do the following (can anyone think of anything else?):
>
> 1. Add the security_inet_conn_established() hook to the DCCP code path (if it
> isn't there already, need to check) so that the last part of the DCCP handshake
> is caught by the LSM.
Sorry, forgot to mention that we would also need to check the other related LSM
connection based hooks like inet_conn_request() and inet_csk_clone().
--
paul moore
linux security @ hp
WARNING: multiple messages have this Message-ID (diff)
From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
dccp@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [PATCH RFC] SELinux support for DCCP
Date: Mon, 13 Nov 2006 15:54:13 -0500 [thread overview]
Message-ID: <4558DB75.9020608@hp.com> (raw)
In-Reply-To: <4558D93B.9030003@hp.com>
Paul Moore wrote:
> Based on my simple understanding of DCCP it looks okay to me, i.e. all the
> relevant things we do for TCP seem to be done now for DCCP. Also, I don't think
> adding labeled networking support should be all that difficult; basically we
> would need to do the following (can anyone think of anything else?):
>
> 1. Add the security_inet_conn_established() hook to the DCCP code path (if it
> isn't there already, need to check) so that the last part of the DCCP handshake
> is caught by the LSM.
Sorry, forgot to mention that we would also need to check the other related LSM
connection based hooks like inet_conn_request() and inet_csk_clone().
--
paul moore
linux security @ hp
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-11-13 20:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 7:16 [PATCH RFC] SELinux support for DCCP James Morris
2006-11-11 7:16 ` James Morris
2006-11-11 15:46 ` Eric Paris
2006-11-11 15:46 ` Eric Paris
2006-11-11 15:56 ` Joshua Brindle
2006-11-11 15:56 ` Joshua Brindle
2006-11-11 17:46 ` James Morris
2006-11-11 17:46 ` James Morris
2006-11-11 17:47 ` James Morris
2006-11-11 17:47 ` James Morris
2006-11-11 17:49 ` Joshua Brindle
2006-11-11 17:49 ` Joshua Brindle
2006-11-11 18:03 ` James Morris
2006-11-11 18:03 ` James Morris
2006-11-13 13:28 ` Flask headers (Was: RE: [PATCH RFC] SELinux support for DCCP) Stephen Smalley
2006-11-13 16:30 ` Christopher J. PeBenito
2006-11-13 16:38 ` Stephen Smalley
2006-11-13 16:43 ` James Morris
2006-11-11 18:11 ` [PATCH RFC] SELinux support for DCCP James Morris
2006-11-11 18:11 ` James Morris
2006-11-11 18:22 ` Joshua Brindle
2006-11-11 18:22 ` Joshua Brindle
2006-11-12 0:36 ` Arnaldo Carvalho de Melo
2006-11-13 20:44 ` Paul Moore
2006-11-13 20:44 ` Paul Moore
2006-11-13 20:54 ` Paul Moore [this message]
2006-11-13 20:54 ` Paul Moore
2006-11-13 21:18 ` James Morris
2006-11-13 21:18 ` James Morris
2006-11-29 22:57 ` Gerrit Renker
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=4558DB75.9020608@hp.com \
--to=paul.moore@hp.com \
--cc=dccp@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.