From: Paul Moore <paul@paul-moore.com>
To: "Langland, Blake" <blangland@integrity-apps.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: SELinux network labeling
Date: Wed, 13 Mar 2013 10:02:54 -0400 [thread overview]
Message-ID: <2547229.Czz0AkDGmt@sifl> (raw)
In-Reply-To: <514080E7.8020602@tycho.nsa.gov>
On Wednesday, March 13, 2013 09:36:39 AM Stephen Smalley wrote:
> netlabel vs labeled ipsec: netlabel only supports passing MLS labels
> via CIPSO, no user:role:type preservation. labeled ipsec supports
> passing the entire security context, including user:role:type.
Just one quick comment, and a word of caution, that the differences between
CIPSO and labeled IPsec are much greater than what is described above.
>From a SELinux policy perspective Stephen does touch on the main point: CIPSO
labeled traffic will look like system_u:object_r:netlabel_peer_t:{MLS-LABEL}
to SELinux regardless of the user:role:type of the sender (only the "MLS-
LABEL" information is passed over the wire) while labeled IPsec will pass the
full context over the wire. However, stepping back just the SELinux policy
there are other differences between the two protocols that need to be
considered when building a full solution.
--
paul moore
www.paul-moore.com
--
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-13 14:02 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 [this message]
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
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=2547229.Czz0AkDGmt@sifl \
--to=paul@paul-moore.com \
--cc=blangland@integrity-apps.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.