All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 28/34]: patch to allow reading hal pid files from ifconfig_t
Date: Mon, 28 Feb 2011 19:26:43 +0100	[thread overview]
Message-ID: <1298917603.3123.2.camel@tesla.lan> (raw)
In-Reply-To: <4D6BB59C.30105@tresys.com>

On Mon, 28/02/2011 at 09.47 -0500, Christopher J. PeBenito wrote:
> On 02/16/11 01:34, Guido Trentalancia wrote:
> > This patch allows to read hal pid files from the ifconfig_t
> > context.
> > 
> > diff -pruN refpolicy-git-15022011-new-before-modification/policy/modules/system/sysnetwork.te refpolicy-git-15022011-new-modified/policy/modules/system/sysnetwork.te
> > --- refpolicy-git-15022011-new-before-modification/policy/modules/system/sysnetwork.te	2011-01-08 19:07:21.363760466 +0100
> > +++ refpolicy-git-15022011-new-modified/policy/modules/system/sysnetwork.te	2011-02-15 23:28:42.843164809 +0100
> > @@ -327,6 +327,7 @@ ifdef(`hide_broken_symptoms',`
> >  optional_policy(`
> >  	hal_dontaudit_rw_pipes(ifconfig_t)
> >  	hal_dontaudit_rw_dgram_sockets(ifconfig_t)
> > +	hal_read_pid_files(ifconfig_t)
> >  ')
> >  
> >  optional_policy(`
> 
> Why would this be necessary?  Are you sure its not another leak
> (especially considering the other dontaudits)?

Yes, that is not strictly necessary. What do you mean exactly for a
leak ?

Regards,

Guido

  parent reply	other threads:[~2011-02-28 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16  6:34 [refpolicy] [PATCH 28/34]: patch to allow reading hal pid files from ifconfig_t Guido Trentalancia
2011-02-28 14:47 ` Christopher J. PeBenito
2011-02-28 15:52   ` Miroslav Grepl
2011-02-28 18:26   ` Guido Trentalancia [this message]
2011-02-28 18:39     ` Daniel J Walsh

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