All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Venkat Yekkirala" <vyekkirala@TrustedCS.com>
To: "'Stephen Smalley'" <sds@tycho.nsa.gov>,
	"Paul Moore" <paul.moore@hp.com>
Cc: <netdev@vger.kernel.org>, <selinux@tycho.nsa.gov>, <jmorris@namei.org>
Subject: RE: [PATCH 3/3] mlsxfrm: Various fixes
Date: Wed, 8 Nov 2006 08:34:34 -0600	[thread overview]
Message-ID: <000601c70343$02fa9fe0$cc0a010a@tcssec.com> (raw)
In-Reply-To: <1162932520.3009.58.camel@moss-spartans.epoch.ncsc.mil>

> Such duplication can occur among the initial SIDs.

For some reason I thought that could happen between an initial SID
and a non-initial SID.

>  Not sure 
> though when
> that would apply here,

It could apply to xfrms if they happen to be using the context
represented by any of the initial SIDs.

> and it would only apply if both SIDs 
> were initial
> SIDs.

OK. Will narrow the full context comparison to just this case.

--
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: "Venkat Yekkirala" <vyekkirala@trustedcs.com>
To: "'Stephen Smalley'" <sds@tycho.nsa.gov>,
	"Paul Moore" <paul.moore@hp.com>
Cc: <netdev@vger.kernel.org>, <selinux@tycho.nsa.gov>, <jmorris@namei.org>
Subject: RE: [PATCH 3/3] mlsxfrm: Various fixes
Date: Wed, 8 Nov 2006 08:34:34 -0600	[thread overview]
Message-ID: <000601c70343$02fa9fe0$cc0a010a@tcssec.com> (raw)
In-Reply-To: <1162932520.3009.58.camel@moss-spartans.epoch.ncsc.mil>

> Such duplication can occur among the initial SIDs.

For some reason I thought that could happen between an initial SID
and a non-initial SID.

>  Not sure 
> though when
> that would apply here,

It could apply to xfrms if they happen to be using the context
represented by any of the initial SIDs.

> and it would only apply if both SIDs 
> were initial
> SIDs.

OK. Will narrow the full context comparison to just this case.

  reply	other threads:[~2006-11-08 14:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 17:17 [PATCH 3/3] mlsxfrm: Various fixes Venkat Yekkirala
2006-11-07 17:17 ` Venkat Yekkirala
2006-11-07 20:29 ` Paul Moore
2006-11-07 20:29   ` Paul Moore
2006-11-07 20:48   ` Stephen Smalley
2006-11-07 20:48     ` Stephen Smalley
2006-11-08 14:34     ` Venkat Yekkirala [this message]
2006-11-08 14:34       ` Venkat Yekkirala
2006-11-08 17:34       ` Stephen Smalley
2006-11-08 17:34         ` Stephen Smalley
2006-11-08 19:17         ` Venkat Yekkirala
2006-11-08 19:17           ` Venkat Yekkirala
2006-11-08 21:57           ` Stephen Smalley
2006-11-08 21:57             ` Stephen Smalley

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='000601c70343$02fa9fe0$cc0a010a@tcssec.com' \
    --to=vyekkirala@trustedcs.com \
    --cc=jmorris@namei.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 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.