From: Paul Moore <paul.moore@hp.com>
To: "Clarkson, Mike R (US SSA)" <mike.clarkson@baesystems.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Brindle example of labeled IPSec
Date: Fri, 15 Feb 2008 18:42:53 -0500 [thread overview]
Message-ID: <200802151842.53403.paul.moore@hp.com> (raw)
In-Reply-To: <FB39F4E77226B448BC1388D3BE4E00CD02AF9741@blums0008.bluelnk.net>
On Friday 15 February 2008 6:25:45 pm Clarkson, Mike R (US SSA) wrote:
> I understand why there is no labeling after doing "setkey -FP". That
> was expected.
I'm sorry, I mis-read your original question.
> My question is why does the labeling work in enforcing mode, even
> though my policy does not provide the following rules:
> allow brindle_client_t ipsec_spd_t:association polmatch;
> allow brindle_client_t brindle_server_t:association recvfrom;
>
> With labeled IPSec over the loopback, I did not have to provide any
> rules in my brindle_client module or my brindle_server module with
> respect to the association object class. Without the association
> rules, the policy doesn't have any way of enforcing MLS constraints,
> or TE on the client server connections, which is the reason that I
> set up labeled IPSec over loopback in the first place.
That is interesting isn't it? I don't have an answer off the top of my
head which means I need to go and dig through the kernel and policy to
try and piece together what is going on. What kernel version and
policy version are you running?
--
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.
next prev parent reply other threads:[~2008-02-15 23:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 20:15 Brindle example of labeled IPSec Clarkson, Mike R (US SSA)
2008-02-15 21:40 ` Paul Moore
2008-02-15 23:25 ` Clarkson, Mike R (US SSA)
2008-02-15 23:42 ` Paul Moore [this message]
2008-02-15 23:47 ` Clarkson, Mike R (US SSA)
2008-02-15 23:50 ` Clarkson, Mike R (US SSA)
2008-02-16 0:26 ` Joshua Brindle
2008-02-16 1:11 ` Clarkson, Mike R (US SSA)
2008-02-16 1:19 ` Joshua Brindle
2008-02-16 1:28 ` Clarkson, Mike R (US SSA)
2008-02-16 1:38 ` Joshua Brindle
-- strict thread matches above, loose matches on Subject: below --
2008-02-16 0:27 Joy Latten
2008-02-16 1:20 ` Clarkson, Mike R (US SSA)
2008-02-16 1:40 Joy Latten
2008-02-16 1:48 ` Clarkson, Mike R (US SSA)
2008-02-16 2:00 ` Clarkson, Mike R (US SSA)
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=200802151842.53403.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=mike.clarkson@baesystems.com \
--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.