From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: James Morris <jmorris@redhat.com>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
<linux-kernel@vger.kernel.org>, <selinux@tycho.nsa.gov>,
<lksctp-developers@lists.sourceforge.net>
Subject: Re: [SELINUX] Add IPv6 support
Date: Sun, 04 Apr 2004 05:19:42 -0400 [thread overview]
Message-ID: <m31xn42j81.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <Xine.LNX.4.44.0404040107120.7220-100000@thoron.boston.redhat.com> (James Morris's message of "Sun, 4 Apr 2004 01:33:09 -0500 (EST)")
>>>>> JM == James Morris <jmorris@redhat.com> writes:
JM> send & receive TCP/UDP and raw IP packets
>From a scan through the patch, it looks like it does in fact only
handle those tcp, udp and raw.
Sctp also should be supported by these mechanisms, given that 2.6
has both in the main tree.
I'd expect many systems which will be installed in the next few
quarters and which could make good use of the selinux controls
will require sctp support.
-JimC
prev parent reply other threads:[~2004-04-04 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 6:33 James Morris
2004-04-04 9:19 ` James H. Cloos Jr. [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=m31xn42j81.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@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
all inboxes | Powered by JetHome®