From: Stephen Hemminger <shemminger@osdl.org>
To: Paul Moore <paul.moore@hp.com>
Cc: netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
selinux@tycho.nsa.gov, James Morris <jmorris@redhat.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [RFC 0/4] NetLabel
Date: Thu, 25 May 2006 13:58:46 -0700 [thread overview]
Message-ID: <20060525135846.44791440@localhost.localdomain> (raw)
In-Reply-To: <44760E29.4070407@hp.com>
On Thu, 25 May 2006 16:06:01 -0400
Paul Moore <paul.moore@hp.com> wrote:
> This patch introduces a new kernel feature designed to support labeled
> networking protocols such as RIPSO and CIPSO. These protocols are required to
> interoperate with existing "trusted" operating systems such as Trusted Solaris.
> I am posting the patch now not because I feel it is ready for inclusion into
> any of the main kernel trees but because it is usable and I would like to
> solicit comments from the community sooner rather than later.
>
> I know there has been at least one previous effort to get CIPSO support into
> the kernel and that was rejected. I have tried to take the feedback from that
> patch into consideration with this patch and create a new mechanism which
> treads as lightly as possible on the core networking stack. I have also
> worked to make the new patch LSM agnostic so that this code can be shared
> amongst multiple LSMs; while I am only providing a patch for SELinux at this
> point I do understand that there is at least one other LSM that is interested
> in making use of this new mechanism.
>
> I understand that there will probably need to be a lengthy review period due
> to the size and complexity of this patch. I also understand that my relative
> inexperience with submitting patches to the Linux kernel will not do much to
> help my cause but I appreciate your patience and any comments you may have.
>
> There is a more information as well as a basic userspace tool for configuration
> of the NetLabel subsystem here:
>
> * http://free.linux.hp.com/~pmoore/projects/linux_cipso
>
Maybe this would be easier and better done via existing netfilter infrastructure?
next prev parent reply other threads:[~2006-05-25 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 20:06 [RFC 0/4] NetLabel Paul Moore
2006-05-25 20:58 ` Stephen Hemminger [this message]
2006-05-25 21:14 ` Paul Moore
2006-05-26 0:06 ` James Morris
2006-05-26 15:30 ` Paul Moore
2006-05-26 16:02 ` James Morris
2006-05-26 16:34 ` Paul Moore
2006-05-26 18:56 ` James Morris
2006-05-26 16:09 ` Mikel L. Matthews
2006-05-26 16:15 ` Paul Moore
2006-05-26 16:20 ` Mikel L. Matthews
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=20060525135846.44791440@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=jmorris@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=sds@tycho.nsa.gov \
--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;
as well as URLs for NNTP newsgroup(s).