All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Joe Nall <joe@nall.com>, David Miller <davem@davemloft.net>,
	jmorris@redhat.com, Stephen Smalley <sds@epoch.ncsc.mil>,
	RedHat LSPP <redhat-lspp@redhat.com>,
	linux-security-module@vger.kernel.org,
	SELinux List <selinux@tycho.nsa.gov>,
	netdev@vger.kernel.org, Steve Grubb <sgrubb@redhat.com>
Subject: Re: [redhat-lspp] Re: [RFC 3/7] NetLabel: CIPSOv4 engine
Date: Mon, 26 Jun 2006 22:45:02 -0400	[thread overview]
Message-ID: <200606262245.03628.paul.moore@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606262031010.26545@d.namei>

On Monday 26 June 2006 8:33 pm, James Morris wrote:
> On Mon, 26 Jun 2006, Joe Nall wrote:
> > For all of the EAL4 LSPP Linux evaluation work is being done by Red
> > Hat/IBM/HP/atsec and others to be useful to integrators, there has to be
> > basic (e.g. CIPSO) multilevel network interoperability with existing
> > multilevel systems and good (e.g IPSec) multilevel networking between
> > SELinux systems.
>
> Just to be clear, my understanding is that the native xfrm labeling is
> suitable for LSPP evaluation, as distinct from CIPSO being desired by
> system integrators from an interoperability point of view.
>

True, but I believe the point Joe was trying to make was that providing 
support for only one labeling mechanism would limit the usefulness of the 
evaluated configuration.  What good is a Common Criteria evaluation if it 
doesn't contain the features that user's require?

-- 
paul moore
linux security @ hp

--
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.

WARNING: multiple messages have this Message-ID (diff)
From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Joe Nall <joe@nall.com>, David Miller <davem@davemloft.net>,
	jmorris@redhat.com, Stephen Smalley <sds@epoch.ncsc.mil>,
	RedHat LSPP <redhat-lspp@redhat.com>,
	linux-security-module@vger.kernel.org,
	SELinux List <selinux@tycho.nsa.gov>,
	netdev@vger.kernel.org, Steve Grubb <sgrubb@redhat.com>
Subject: Re: [redhat-lspp] Re: [RFC 3/7] NetLabel: CIPSOv4 engine
Date: Mon, 26 Jun 2006 22:45:02 -0400	[thread overview]
Message-ID: <200606262245.03628.paul.moore@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606262031010.26545@d.namei>

On Monday 26 June 2006 8:33 pm, James Morris wrote:
> On Mon, 26 Jun 2006, Joe Nall wrote:
> > For all of the EAL4 LSPP Linux evaluation work is being done by Red
> > Hat/IBM/HP/atsec and others to be useful to integrators, there has to be
> > basic (e.g. CIPSO) multilevel network interoperability with existing
> > multilevel systems and good (e.g IPSec) multilevel networking between
> > SELinux systems.
>
> Just to be clear, my understanding is that the native xfrm labeling is
> suitable for LSPP evaluation, as distinct from CIPSO being desired by
> system integrators from an interoperability point of view.
>

True, but I believe the point Joe was trying to make was that providing 
support for only one labeling mechanism would limit the usefulness of the 
evaluated configuration.  What good is a Common Criteria evaluation if it 
doesn't contain the features that user's require?

-- 
paul moore
linux security @ hp

  reply	other threads:[~2006-06-27  2:45 UTC|newest]

Thread overview: 45+ 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 ` paul.moore
2006-06-21 19:42 ` [RFC 1/7] NetLabel: documentation paul.moore
2006-06-21 19:42   ` paul.moore
2006-06-21 19:42 ` [RFC 2/7] NetLabel: core network changes paul.moore
2006-06-21 19:42   ` paul.moore
2006-06-22  9:00   ` David Miller
2006-06-22 15:05     ` Steve Grubb
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-22 13:20       ` Paul Moore
2006-06-21 19:42 ` [RFC 3/7] NetLabel: CIPSOv4 engine paul.moore
2006-06-21 19:42   ` paul.moore
2006-06-22  9:12   ` David Miller
2006-06-22 13:43     ` Paul Moore
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-26 23:14       ` Joe Nall
2006-06-27  0:33       ` James Morris
2006-06-27  0:33         ` James Morris
2006-06-27  2:45         ` Paul Moore [this message]
2006-06-27  2:45           ` Paul Moore
2006-06-27 19:41         ` Klaus Weidner
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   ` paul.moore
2006-06-21 21:15   ` Steve Grubb
2006-06-21 21:24     ` [redhat-lspp] " Paul Moore
2006-06-21 21:26       ` Steve Grubb
2006-06-21 19:42 ` [RFC 5/7] NetLabel: SELinux support paul.moore
2006-06-21 19:42   ` paul.moore
2006-06-21 19:42 ` [RFC 6/7] NetLabel: CIPSOv4 integration paul.moore
2006-06-21 19:42   ` paul.moore
2006-06-21 19:42 ` [RFC 7/7] NetLabel: unlabeled packet handling paul.moore
2006-06-21 19:42   ` 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=200606262245.03628.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=jmorris@redhat.com \
    --cc=joe@nall.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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 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.