From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Joshua Brindle <method@gentoo.org>,
Venkat Yekkirala <vyekkirala@TrustedCS.com>,
netdev@vger.kernel.org, selinux@tycho.nsa.gov,
kmacmillan@mentalrootkit.com
Subject: Re: [PATCH 7/7] secid reconciliation-v03: Enforcement for SELinux
Date: Fri, 29 Sep 2006 12:15:46 -0400 [thread overview]
Message-ID: <451D46B2.9010906@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609291209150.5698@d.namei>
James Morris wrote:
> On Fri, 29 Sep 2006, Paul Moore wrote:
>
>
>>Unless I'm confusing something, there still may be a need for transitions
>>if we want to support both IPsec and NetLabel labeling on the same
>>connection.
>
> I'd prefer not to support this, as it's too complicated, and CIPSO is a
> legacy protocol.
>
> Normal IPsec protection applied to CIPSO: yes, but not IPsec labeling and
> CIPSO labeling on the same connection.
I tend to agree, I just can't see it being all that useful in the real
world. However, each time it comes up (including the conference call
earlier this week) it seems that people would prefer to use both at the
same time.
The good news is that it sounds like there is a reasonable solution (see
the last email exchance between Venkat and myself).
--
paul moore
linux security @ hp
next prev parent reply other threads:[~2006-09-29 16:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 2:33 [PATCH 7/7] secid reconciliation-v03: Enforcement for SELinux Venkat Yekkirala
2006-09-29 3:52 ` Joshua Brindle
2006-09-29 12:59 ` Stephen Smalley
2006-09-29 14:00 ` Joshua Brindle
2006-09-29 14:28 ` Stephen Smalley
2006-09-29 14:33 ` James Morris
2006-09-29 14:39 ` Stephen Smalley
2006-09-29 16:06 ` Paul Moore
2006-09-29 16:10 ` James Morris
2006-09-29 16:15 ` Paul Moore [this message]
2006-09-29 16:39 ` Paul Moore
-- strict thread matches above, loose matches on Subject: below --
2006-09-29 16:09 Venkat Yekkirala
2006-09-29 16:13 ` Paul Moore
2006-09-29 16:17 Venkat Yekkirala
2006-09-29 16:22 Venkat Yekkirala
2006-09-29 16:27 Venkat Yekkirala
2006-09-29 16:31 ` Paul Moore
2006-09-29 16:50 ` James Morris
2006-09-29 17:32 ` James Morris
2006-09-29 17:50 ` Paul Moore
2006-09-29 17:43 ` Paul Moore
2006-09-29 18:41 ` James Morris
2006-09-29 19:06 ` Paul Moore
2006-09-29 19:33 ` James Morris
2006-09-29 19:51 ` Paul Moore
2006-09-29 20:04 ` James Morris
2006-09-29 20:09 ` Paul Moore
2006-09-29 17:27 Venkat Yekkirala
2006-09-29 17:38 ` Paul Moore
2006-09-29 18:50 Venkat Yekkirala
2006-09-29 19:13 ` Paul Moore
2006-09-29 21:54 Venkat Yekkirala
2006-09-29 22:10 Venkat Yekkirala
2006-10-01 21:30 Venkat Yekkirala
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=451D46B2.9010906@hp.com \
--to=paul.moore@hp.com \
--cc=jmorris@namei.org \
--cc=kmacmillan@mentalrootkit.com \
--cc=method@gentoo.org \
--cc=netdev@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=vyekkirala@TrustedCS.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).