netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: paul.moore@hp.com
Cc: redhat-lspp@redhat.com, selinux@tycho.nsa.gov,
	linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
	sds@epoch.ncsc.mil, jmorris@redhat.com, sgrubb@redhat.com
Subject: Re: [RFC 3/7] NetLabel: CIPSOv4 engine
Date: Thu, 22 Jun 2006 02:12:23 -0700 (PDT)	[thread overview]
Message-ID: <20060622.021223.125894633.davem@davemloft.net> (raw)
In-Reply-To: <20060621200031.589235000@flek.zko.hp.com>

From: paul.moore@hp.com
Date: Wed, 21 Jun 2006 15:42:38 -0400

> Add support for the Commercial IP Security Option (CIPSO) to the
> IPv4 network stack.  CIPSO has become a de-facto standard for
> trusted/labeled networking amongst existing Trusted Operating
> Systems such as Trusted Solaris, HP-UX CMW, etc.  This
> implementation is designed to be used with the NetLabel subsystem to
> provide explicit packet labeling to LSM developers.

The thing that concerns me most about CIPSO is that even once users
migrate to a more SELINUX native approach from this CIPSO stuff, the
CIPSO code, it's bloat, and it's maintainence burdon will remain.

It's easy to put stuff it, it's impossible to take stuff out even
once it's largely unused by even it's original target audience.

And that's what I see happening here.

This is why, to be perfectly honest with you, I'd much rather
something like this stay out-of-tree and people are strongly
encouraged to use the more native stuff under Linux.

  reply	other threads:[~2006-06-22  9:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 19:42 [RFC 0/7] Updated NetLabel patch paul.moore
2006-06-21 19:42 ` [RFC 1/7] NetLabel: documentation paul.moore
2006-06-21 19:42 ` [RFC 2/7] NetLabel: core network changes paul.moore
2006-06-22  9:00   ` David Miller
2006-06-22 15:05     ` Steve Grubb
2006-06-22 18:58       ` James Morris
2006-06-22 21:32       ` David Miller
2006-06-22  9:07   ` David Miller
2006-06-22 13:20     ` Paul Moore
2006-06-21 19:42 ` [RFC 3/7] NetLabel: CIPSOv4 engine paul.moore
2006-06-22  9:12   ` David Miller [this message]
2006-06-22 13:43     ` Paul Moore
2006-06-22 15:57       ` Ryan Pratt
2006-06-23 18:48     ` Ted
2006-06-23 20:15       ` David Miller
2006-06-23 20:34         ` Ted
2006-06-23 23:24           ` James Morris
2006-06-23 23:45             ` Paul Moore
2006-06-26 15:32               ` James Morris
2006-06-26 23:14     ` [redhat-lspp] " Joe Nall
2006-06-27  0:33       ` James Morris
2006-06-27  2:45         ` Paul Moore
2006-06-27 19:41         ` Klaus Weidner
2006-06-21 19:42 ` [RFC 4/7] NetLabel: core NetLabel subsystem paul.moore
2006-06-21 19:42 ` [RFC 5/7] NetLabel: SELinux support paul.moore
2006-06-21 19:42 ` [RFC 6/7] NetLabel: CIPSOv4 integration paul.moore
2006-06-21 19:42 ` [RFC 7/7] NetLabel: unlabeled packet handling 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=20060622.021223.125894633.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jmorris@redhat.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul.moore@hp.com \
    --cc=redhat-lspp@redhat.com \
    --cc=sds@epoch.ncsc.mil \
    --cc=selinux@tycho.nsa.gov \
    --cc=sgrubb@redhat.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 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).