From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC 14/19]: patch set to update the git reference policy
Date: Mon, 24 Jan 2011 16:49:24 +0100 [thread overview]
Message-ID: <1295884164.1547.8.camel@tesla.lan> (raw)
In-Reply-To: <4D3D8387.6010003@gmail.com>
On Mon, 24/01/2011 at 14.49 +0100, Dominick Grift wrote:
> On 01/24/2011 01:44 AM, Guido Trentalancia wrote:
> > diff -pruN -x .git -x booleans.conf -x corenetwork.if -x corenetwork.te -x modules.conf refpolicy-git-18012011/policy/modules/system/logging.te refpolicy-git-18012011-new/policy/modules/system/logging.te
> > --- refpolicy-git-18012011/policy/modules/system/logging.te 2011-01-08 19:07:21.356759360 +0100
> > +++ refpolicy-git-18012011-new/policy/modules/system/logging.te 2011-01-18 23:13:49.813854998 +0100
> > @@ -223,6 +223,8 @@ allow audisp_t self:unix_dgram_socket cr
> >
> > allow audisp_t auditd_t:unix_stream_socket rw_socket_perms;
> >
> > +allow audisp_t proc_t:file read_file_perms;
>
> usage of proc_t is not allowed here. use:
>
> kernel_read_system_state(audisp_t)
Ok, it will be changed accordingly. Wasn't aware of that restriction, is
it the style guidelines thing ? Of course, proc_t is not defined
there...
There were other comments to other pieces of the set. Will check the
rest later this evening or tomorrow as it requires a bit more time.
Thanks very much for your comments.
Regards,
Guido
next prev parent reply other threads:[~2011-01-24 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 0:44 [refpolicy] [PATCH/RFC 14/19]: patch set to update the git reference policy Guido Trentalancia
2011-01-24 13:49 ` Dominick Grift
2011-01-24 15:49 ` Guido Trentalancia [this message]
2011-01-24 15:55 ` Dominick Grift
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=1295884164.1547.8.camel@tesla.lan \
--to=guido@trentalancia.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.