From: Linda Knippers <linda.knippers@hp.com>
To: Chad Hanson <dahchanson@gmail.com>
Cc: Paul Moore <paul@paul-moore.com>,
"Langland, Blake" <blangland@integrity-apps.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: SELinux network labeling
Date: Thu, 14 Mar 2013 11:25:05 -0400 [thread overview]
Message-ID: <5141EBD1.5050005@hp.com> (raw)
In-Reply-To: <CAOFCXeeoEdMkWze354_Fn=9=3Vv8L_t9sn0vRXY-qGLhvMb2DQ@mail.gmail.com>
Chad Hanson wrote:
>
> On Wed, Mar 13, 2013 at 1:55 PM, Paul Moore <paul@paul-moore.com
> <mailto:paul@paul-moore.com>> wrote:
>
> On Wednesday, March 13, 2013 05:29:47 PM Langland, Blake wrote:twork
> traffic
>
> > The reason I ruled that out IPSec labeling is that we are using
> Openswan for
> > IPSec and it is my understanding after talking with Josh Brindle that
> > labeling is not supported in Openswan. Are there any plans to
> bring labeled
> > associations to Openswan?
>
> I haven't tested it lately but my understanding is that the version of
> Openswan shipped with RHEL6 supports labeled IPsec. I am unsure
> about other
> distributions.
>
>
> Openswan supports labeling in RHEL 6, although it looks like there may
> have been a policy issue which was probably resolved by RHEL 6.3 from
> looking at this Red Hat Bugzilla report:
> https://bugzilla.redhat.com/show_bug.cgi?id=748971
Openswan was used for labeled IPsec in the CC evaluation of RHEL6.2. There were
a handful of bug fixes that landed in RHEL6.3. I don't recall that one
specifically but it doesn't surprise me.
-- ljk
--
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.
next prev parent reply other threads:[~2013-03-14 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 20:55 SELinux network labeling Langland, Blake
2013-03-13 1:35 ` Paul Moore
2013-03-13 13:36 ` Stephen Smalley
2013-03-13 14:02 ` Paul Moore
2013-03-13 17:29 ` Langland, Blake
2013-03-13 17:41 ` Stephen Smalley
2013-03-13 17:55 ` Paul Moore
2013-03-13 21:52 ` Chad Hanson
2013-03-14 15:25 ` Linda Knippers [this message]
2013-03-14 15:37 ` Langland, Blake
2013-03-14 16:24 ` Linda Knippers
2013-03-14 16:45 ` Richard Haines
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=5141EBD1.5050005@hp.com \
--to=linda.knippers@hp.com \
--cc=blangland@integrity-apps.com \
--cc=dahchanson@gmail.com \
--cc=paul@paul-moore.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.