From: paul.moore@hp.com (Paul Moore)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] network: Enable "network_peer_controls" and fix some remaining issues
Date: Mon, 2 Feb 2009 17:16:25 -0500 [thread overview]
Message-ID: <200902021716.25751.paul.moore@hp.com> (raw)
In-Reply-To: <1233326781.6143.9.camel@defiant.pebenito.net>
On Friday 30 January 2009 9:46:21 am you wrote:
> On Fri, 2009-01-16 at 17:08 -0500, Paul Moore wrote:
> > plain text document attachment (network-in_out_basic)
> > We added the network_peer_controls capability back in Linux Kernel
> > 2.6.25 but didn't activate the capability because more work was
> > needed to ensure a smooth transition to the new controls. This
> > patch enables the network_peer_controls capability and fixes a few
> > remaining issues with its use. With this patch applied to the
> > Fedora Rawhide SELinux policy (selinux-policy-3.6.1-4.fc11) I am
> > able to interact with the machine over the network without any new
> > AVC denials.
>
> Does it work without the legacy support rules? I'm thinking that for
> now we don't want the legacy support in these interfaces, since we're
> still not ready to dump all the compat_net support. Then its clear
> that its not supposed to be used for compat_net rules.
I'm testing it right now (it should work without the legacy bits). Once
I've verified the changes I'll repost.
--
paul moore
linux @ hp
prev parent reply other threads:[~2009-02-02 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 22:08 [refpolicy] network: Enable "network_peer_controls" and fix some remaining issues Paul Moore
[not found] ` <1233326781.6143.9.camel@defiant.pebenito.net>
2009-02-02 22:16 ` Paul Moore [this message]
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=200902021716.25751.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=refpolicy@oss.tresys.com \
/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.