From: Ted <txtoth@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: [RFC 3/7] NetLabel: CIPSOv4 engine
Date: Fri, 23 Jun 2006 15:34:17 -0500 [thread overview]
Message-ID: <1151094857.2669.51.camel@localhost.localdomain> (raw)
In-Reply-To: <20060623.131512.21593290.davem@davemloft.net>
On Fri, 2006-06-23 at 13:15 -0700, David Miller wrote:
> From: Ted <txtoth@gmail.com>
> Date: Fri, 23 Jun 2006 13:48:01 -0500
>
> > Realistically customers most likely to adopt use of SELinux are
> > going to be ones that currently use other trusted OSs such as TSOL
> > and HP-UX CMW.
>
> Every single user who installs a modern distribution these days likely
> gets SELINUX enabled by default, and are therefore adopters of
> SELINUX. That's a lot of people.
>
> The number of people with existing CIPSO infrastructure are miniscule
> in comparison.
>
I think that except those who currently use and understand trusted OSs
users will change SELinux to permissive mode because they won't have the
expertise to deal with policy issues.
> Please do not even imply that CIPSO use is anything but fringe in the
> grand scheme of things. It most certainly is. And it will be
> replaced by IPSEC based labelling, that is a fact. If people cannot
> move over to IPSEC labelling simply because their HPUX/TSOL doesn't
> support it, I'm perfectly happy for those users to stick with HPUX and
> TSOL. A lot of people think Linux should try to be everything for
> everybody, I'm not one of those people :-)
>
I can guarantee that initially SELinux adoption will be by those running
trusted OSs and they will want their systems to be able to interoperate
at level. The idea that IPSEC will fill this need in the near term is
just not realistic.
> For CIPSO we eat a non-trivial maintainence and bloat cost in order to
> support legacy stuff for this relatively tiny group of potential
> users.
>
> I'd rather pay the bloat and development costs on something forward
> thinking like IPSEC labelling. Something people will actually be
> using years from now, rather than a dying technology that few people
> (relatively speaking) use as it is.
>
> Finally, even if CIPSO is something we want to put in, don't worry
> about it as there's still time to discuss things. A couple days
> before the merge window of 2.6.18 development closes is not the time
> to be submitting half-finished work and expecting it to be integrated.
> If 2.6.18 integration is what the submitter desires, they should have
> finished their work and started this review process weeks if not
> months ago.
next prev parent reply other threads:[~2006-06-23 20:34 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
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 [this message]
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=1151094857.2669.51.camel@localhost.localdomain \
--to=txtoth@gmail.com \
--cc=netdev@vger.kernel.org \
/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).