From: Stephen Smalley <sds@tycho.nsa.gov>
To: Nigel Rumens <wooky@btconnect.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
SE Linux <selinux@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
James Morris <jmorris@namei.org>
Subject: Re: selinux and sctp
Date: Tue, 26 May 2009 10:40:52 -0400 [thread overview]
Message-ID: <1243348852.19066.9.camel@localhost.localdomain> (raw)
In-Reply-To: <4A1A96BD.5050500@btconnect.com>
On Mon, 2009-05-25 at 14:01 +0100, Nigel Rumens wrote:
> Thanks. I will do just that.
>
> In the meantime though would it be possible to create a local policy
> module to allow this access? (with audit2allow?) Maybe even limiting it
> to just a particular set of processes by creating a new label and
> labeling the relevant executables?
Yes, you should be able to do that.
Prior discussions of sctp and selinux:
http://marc.info/?l=fedora-selinux-list&w=2&r=1&s=sctp&q=b
I don't see sctp support on the selinux kernel todo list.
--
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.
next prev parent reply other threads:[~2009-05-26 14:40 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 [this message]
2009-05-26 22:32 ` Paul Moore
2009-05-27 12:12 ` Stephen Smalley
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=1243348852.19066.9.camel@localhost.localdomain \
--to=sds@tycho.nsa.gov \
--cc=dwalsh@redhat.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--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.