From: Stephen Smalley <sds@tycho.nsa.gov>
To: "Langland, Blake" <blangland@integrity-apps.com>
Cc: "selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: MLS over loopback interface
Date: Thu, 10 Oct 2013 15:02:44 -0400 [thread overview]
Message-ID: <5256F9D4.6080901@tycho.nsa.gov> (raw)
In-Reply-To: <DA8D339A60101247B36E202899B1C93AA91986@CHUNEX01.integrity-apps.com>
On 10/10/2013 01:12 PM, Langland, Blake wrote:
> All,
>
> I have two web servers running on an SELinux machine, one running at s2 and one at s3. Both webservers have two webapps each that are attempting to communicate over the loopback interface. The communication is strictly s2 <-> s2 and s3 <-> s3. The problem I am having is setting the MLS level of the loopback interface. If I have it set below s3, the s3 webapps cannot send over the interface; If I have it set higher than s2, the s2 webapps cannot receive over the interface. Any suggestions?
Can you clarify exactly what avc denials you are getting?
Kernel version?
network_peer_controls enabled or disabled?
I don't see a mlstrustedobject-like exemption in the netif constraints
in refpolicy/policy/mls, so you can't just make the loopback netif type
a mlstrustedobject to exempt it.
I do however see that if you apply mls_net_write_within_range() to the
web server domains and if you put a range on the interface that covers
both levels, then it should pass the mls constraint in policy/mls.
--
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-10-10 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 17:12 MLS over loopback interface Langland, Blake
2013-10-10 17:21 ` Daniel J Walsh
2013-10-10 17:31 ` William Roberts
2013-10-10 18:51 ` Stephen Smalley
2013-10-10 19:02 ` Stephen Smalley [this message]
2013-10-10 20:34 ` Langland, Blake
2013-10-10 20:40 ` 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=5256F9D4.6080901@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=blangland@integrity-apps.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.