Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jmorris@namei.org
Cc: netdev@vger.kernel.org, sds@tycho.nsa.gov, arnaldo.melo@gmail.com
Subject: Re: [PATCH] SELinux: Add support for DCCP
Date: Mon, 13 Nov 2006 16:10:14 -0800 (PST)	[thread overview]
Message-ID: <20061113.161014.35469494.davem@davemloft.net> (raw)
In-Reply-To: <XMMS.LNX.4.64.0611131612490.9577@d.namei>

From: James Morris <jmorris@namei.org>
Date: Mon, 13 Nov 2006 16:15:06 -0500 (EST)

> This patch implements SELinux kernel support for DCCP
> (http://linux-net.osdl.org/index.php/DCCP), which is similar in operation
> to TCP in terms of connected state between peers.
> 
> The SELinux support for DCCP is thus modeled on existing handling of TCP.
> 
> A new DCCP socket class is introduced, to allow protocol differentation.
> The permissions for this class inherit all of the socket permissions, as
> well as the current TCP permissions (node_bind, name_bind etc). IPv4 and
> IPv6 are supported, although labeled networking is not, at this stage.
> 
> Patches for SELinux userspace are at:
> http://people.redhat.com/jmorris/selinux/dccp/user/
> 
> I've performed some basic testing, and it seems to be working as expected.
> Adding policy support is similar to TCP, the only real difference being
> that it's a different protocol.
> 
> Please apply for 2.6.20.
> 
> Also available via git:
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/selinux-net-2.6.20.git
> 
> Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
> Signed-off-by: James Morris <jmorris@namei.org>

Applied to net-2.6.20, thanks.


      reply	other threads:[~2006-11-14  0:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13 21:15 [PATCH] SELinux: Add support for DCCP James Morris
2006-11-14  0:10 ` David Miller [this message]

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=20061113.161014.35469494.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=arnaldo.melo@gmail.com \
    --cc=jmorris@namei.org \
    --cc=netdev@vger.kernel.org \
    --cc=sds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox