All of lore.kernel.org
 help / color / mirror / Atom feed
From: paul.moore@hp.com
To: selinux@tycho.nsa.gov
Cc: cpebenito@tresys.com
Subject: [PATCH 0/4] NetLabel and MLS fixes for Reference Policy
Date: Thu, 14 Dec 2006 14:24:14 -0500	[thread overview]
Message-ID: <20061214192414.551708000@hp.com> (raw)

This patchset addresses a few problems with the reference policy in SVN.  The first is that when I sent the original NetLabel policy patches I forgot to actually assign NetLabel receive access to any of the application domains - oops.  The other issues involve MLS socket overrides and their use in the inetd_t domain.

Most of the changes should have little impact on the policy and I've done some quick testing and everything looks okay to me.  One note, telnet seem to be broken when used in strict-mls under the current policy (broken without this patchset) and I'm currently looking into that, I'll push another patch when I have that fixed.

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

             reply	other threads:[~2006-12-14 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14 19:24 paul.moore [this message]
2006-12-14 19:24 ` [PATCH 1/4] Policy patches to add NetLabel to support to various domains paul.moore
2006-12-14 19:24 ` [PATCH 2/4] Policy patches to add NetLabel support for Raw IP sockets paul.moore
2006-12-14 19:24 ` [PATCH 3/4] Policy patches to add a MLS socket write-to-clearance interface paul.moore
2006-12-14 19:24 ` [PATCH 4/4] Policy patches to add MLS read/write-to-clearance access to inetd_t paul.moore
2006-12-20 16:13 ` [PATCH 0/4] NetLabel and MLS fixes for Reference Policy Paul Moore

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=20061214192414.551708000@hp.com \
    --to=paul.moore@hp.com \
    --cc=cpebenito@tresys.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.