All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Weidner <klaus@atsec.com>
To: Paul Moore <paul.moore@hp.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: [PATCH RFC 0/2] stricter MLS policy constraints
Date: Wed, 13 Dec 2006 15:40:48 -0600	[thread overview]
Message-ID: <20061213214047.GC3362@w-m-p.com> (raw)
In-Reply-To: <458067B3.20107@hp.com>

On Wed, Dec 13, 2006 at 03:50:59PM -0500, Paul Moore wrote:
> I did a quick test using the refpolicy from SVN and your patches; the good news
> is that simple tests using netcat worked as expected and there did not appear to
> be any regressions.

Glad to hear that, thanks for testing!

> The bad news is that I realized we never added NetLabel receive permissions to
> any of the application domains (try to telnet into a machine with NetLabel);
> only the user domains have the NetLabel receive permissions.  As a result I
> wasn't able to try any more elaborate tests without fixing the policy.  It will
> probably take a little while to get a patch out to address this as there are a
> lot of domains which need to be changed; that said I'm probably about a third of
> the way through at this point.
> 
> In case anyone is interested, the policy changes boil down to the following:
> 
>  ifdef(`enable_mls',`
>         corenet_tcp_recv_netlabel(app_domain_t)
>         corenet_udp_recv_netlabel(app_domain_t)
>  ')

Have you considered adding those lines to the existing interfaces in
policy/modules/kernel/corenetwork.if.in instead? For example, telnetd
currently uses corenet_tcp_sendrecv_all_if(telnetd_t), and you could make
that interface provide the needed netlabel rights also.

Do we need something equivalent for labeled IPSEC?

-Klaus

--
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.

  reply	other threads:[~2006-12-13 21:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12  7:28 [PATCH RFC 0/2] stricter MLS policy constraints Klaus Weidner
2006-12-12  7:34 ` [PATCH RFC 1/2] " Klaus Weidner
2007-01-08 15:47   ` Christopher J. PeBenito
2007-01-09  4:43     ` Klaus Weidner
2006-12-12  7:38 ` [PATCH RFC 0/2] " Klaus Weidner
2006-12-12  7:40 ` [PATCH RFC 2/2] " Klaus Weidner
2006-12-12 15:26 ` [PATCH RFC 3/2] " Klaus Weidner
2006-12-13 20:50 ` [PATCH RFC 0/2] " Paul Moore
2006-12-13 21:40   ` Klaus Weidner [this message]
2006-12-13 21:50     ` Paul Moore
2006-12-14 15:48       ` Joy Latten
2007-01-08 16:02       ` Christopher J. PeBenito

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=20061213214047.GC3362@w-m-p.com \
    --to=klaus@atsec.com \
    --cc=paul.moore@hp.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.