From: Eric Paris <eparis@redhat.com>
To: Paul Moore <paul.moore@hp.com>
Cc: selinux <selinux@tycho.nsa.gov>, sds@tycho.nsa.gov, jmorris@namei.org
Subject: Re: [PATCH] SELinux: create new open permission
Date: Thu, 28 Feb 2008 12:22:45 -0500 [thread overview]
Message-ID: <1204219365.3206.76.camel@localhost.localdomain> (raw)
In-Reply-To: <200802281215.45063.paul.moore@hp.com>
On Thu, 2008-02-28 at 12:15 -0500, Paul Moore wrote:
> On Thursday 28 February 2008 10:09:51 am Eric Paris wrote:
> > diff --git a/security/selinux/selinuxfs.c
> > b/security/selinux/selinuxfs.c index 0341567..6e31ce6 100644
> > --- a/security/selinux/selinuxfs.c
> > +++ b/security/selinux/selinuxfs.c
> > @@ -43,6 +43,7 @@
> > /* Policy capability filenames */
> > static char *policycap_names[] = {
> > "network_peer_controls"
> > + "open_perms"
> > };
>
> I think you're missing a comma here :)
>
> This is easy to test by simply checking the /selinux/policy_capabilities
> directory.
You mean its not supposed to look like this?
[root@sun-x8420-01 policy_capabilities]# ls
network_peer_controlsopen_permissions_checking unknown
fixed patch in 10 minutes. it would be faster but this machine takes
forever to reboot.
-Eric
--
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-28 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 15:09 [PATCH] SELinux: create new open permission Eric Paris
2008-02-28 16:27 ` Stephen Smalley
2008-02-28 17:15 ` Paul Moore
2008-02-28 17:22 ` Eric Paris [this message]
2008-02-28 18:46 ` 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=1204219365.3206.76.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=paul.moore@hp.com \
--cc=sds@tycho.nsa.gov \
--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.