All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Paul Moore <paul.moore@hp.com>
Cc: Nigel Rumens <wooky@btconnect.com>,
	Daniel J Walsh <dwalsh@redhat.com>,
	SE Linux <selinux@tycho.nsa.gov>,
	James Morris <jmorris@namei.org>,
	Eric Paris <eparis@parisplace.org>
Subject: Re: selinux and sctp
Date: Wed, 27 May 2009 08:12:05 -0400	[thread overview]
Message-ID: <1243426325.19066.30.camel@localhost.localdomain> (raw)
In-Reply-To: <200905261832.44705.paul.moore@hp.com>

On Tue, 2009-05-26 at 18:32 -0400, Paul Moore wrote:
> On Monday 25 May 2009 07:16:06 am Daniel J Walsh wrote:
> > On 05/24/2009 06:00 AM, Nigel Rumens wrote:
> > > Hi,
> > >
> > > Does selinux understand sctp?
> > >
> > > When I run (for example)
> > >
> > > sctp_darn -H 0 -P 9876 -l
> > >
> > > It results in an avc denial message which tells me the target object is
> > > of type None[rawip_socket]
> > >
> > > Also semanage port -l shows only udp and tcp
> > >
> > > Machine tested on was F11 (fully updated) - I also tried it F10 with the
> > > same results
> 
> Hi Nigel,
> 
> Can you send us the AVC denial messages?  If you are running a recent kernel 
> (F11/Rawhide should qualify and F10 will likely as well) there should only be 
> a handful of areas where you should be hitting transport protocol specific 
> code that isn't SCTP aware in the kernel, it would be nice to verify that so 
> we could better identify what work needs to be done.

- Need to define a sctp_socket class in the policy and kernel (presently
they get mapped to rawip_socket).
- Need to extend the node_bind/name_bind checking to handle multiple
address binding for SCTP.
- Need to extend the name_connect checking to support SCTP.
- Need to add getpeersec support (also missing for DCCP).
- Need to extend selinux_parse_skb* to handle it.
- Need to update libsepol/libsemanage, checkpolicy, and semanage to
support it.

-- 
Stephen Smalley
National Security Agency


--
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.

  reply	other threads:[~2009-05-27 12:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A191AAC.4000500@btconnect.com>
2009-05-25 11:16 ` selinux and sctp Daniel J Walsh
2009-05-25 13:01   ` Nigel Rumens
2009-05-26  0:18     ` Mark Webb
2009-05-27 16:25       ` Nigel Rumens
2009-05-26 11:38     ` Daniel J Walsh
2009-05-26 14:40     ` Stephen Smalley
2009-05-26 22:32   ` Paul Moore
2009-05-27 12:12     ` Stephen Smalley [this message]
2009-05-27 13:36       ` James Morris
2009-05-27 16:39     ` Nigel Rumens
2009-05-27 19:36       ` 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=1243426325.19066.30.camel@localhost.localdomain \
    --to=sds@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=paul.moore@hp.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=wooky@btconnect.com \
    /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.