All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] services_hal.patch
Date: Mon, 27 Jul 2009 10:44:12 -0400	[thread overview]
Message-ID: <4A6DBD3C.3030801@redhat.com> (raw)
In-Reply-To: <1248704344.13158.155.camel@gorn>

On 07/27/2009 10:19 AM, Christopher J. PeBenito wrote:
> On Mon, 2009-06-08 at 20:37 -0400, Daniel J Walsh wrote:
>> http://people.fedoraproject.org/~dwalsh/SELinux/F11/services_hal.patch
>>
>> Add policy for hal-dccm
>>
>> Lots of new interfaces
>>
>> Manages dos/fusefs files
> 
> Why?
I would guess it opens files/directories for read/write.  Perhaps some kind of config file.
> 
>> Starts dhcpc
>>
>> Interfacts with ppp and uses policykit
>>
>>
>>
>> Hald acl gets and sets fixed disk attributes
>>
> 
> Renamed hal_create_log() to hal_manage_log() to match up the permissions
> allowed.
> 
>  ########################################
>  ## <summary>
> +##	Allo read/write	to a hal unix datagram socket.
> +## </summary>
> +## <param name="domain">
> +##	<summary>
> +##	Domain allowed access.
> +##	</summary>
> +## </param>
> +#
> +interface(`hal_rw_dgram_sockets',`
> +	gen_require(`
> +		type hald_t;
> +	')
> +
> +	dontaudit $1 hald_t:unix_dgram_socket { read write };
> +')
> +
> 
> Is this supposed to be allow or dontaudit? the interface name and
> implementation conflict.
> 
I would say it is supposed to be dontaudit, since it looks like a leak.
> Otherwise merged.
> 

  reply	other threads:[~2009-07-27 14:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09  0:37 [refpolicy] services_hal.patch Daniel J Walsh
2009-07-27 14:19 ` Christopher J. PeBenito
2009-07-27 14:44   ` Daniel J Walsh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-26 21:19 Daniel J Walsh
2010-02-23 20:15 Daniel J Walsh
2009-11-12 21:34 Daniel J Walsh
2010-02-11 13:44 ` Christopher J. PeBenito
2009-03-24 13:36 Daniel J Walsh
2008-10-14 20:36 Daniel J Walsh
2008-11-19 15:35 ` Christopher J. PeBenito

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=4A6DBD3C.3030801@redhat.com \
    --to=dwalsh@redhat.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.