All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [REVIEW REQUEST] Changes to the gnome policy module
Date: Tue, 9 Oct 2012 10:02:25 -0400	[thread overview]
Message-ID: <50742E71.1010601@tresys.com> (raw)
In-Reply-To: <1349790756.30521.17.camel@d30.localdomain>

On 10/09/12 09:52, Dominick Grift wrote:
> 
> 
> On Tue, 2012-10-09 at 09:44 -0400, Christopher J. PeBenito wrote:
>> On 10/04/12 11:24, Dominick Grift wrote:
>>>
>>>
>>> On Thu, 2012-10-04 at 10:53 -0400, Daniel J Walsh wrote:
>>>
>>>> That is fine, and something we can try out in Fedora 19.
>>>
>>> I think we should should extend the userdomain policy module to reflect
>>> the freedesktop changes
>>>
>>> That means deal appropriately with /run/user/UID, $HOME/.cache
>>> $HOME/.config and $HOME/.local/share in the userdomain policy module
>>
>> My understanding is that freedesktop is oriented towards X desktops, so it would seem that enhancing xserver_role() would be more appropriate.
>>
> 
> More (or less) specifically "free desktops"
> 
> The problem is that for example the XDG runtime dir, is always created,
> whether you have xserver installed or not.
> 
> So then you will depend on the xserver policy for proper labeling
> 
> That is assuming that we implement a user_runtime_t. Which is another
> thing we need to consider:
> 
> What to label /run/user and /run/user/UID? ( fedora has /run/user(/.*)?
> user_tmp_t )
 
user_tmp_t, as I said in my other email in this thread.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

      reply	other threads:[~2012-10-09 14:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 15:12 [refpolicy] [REVIEW REQUEST] Changes to the gnome policy module Dominick Grift
2012-10-03 15:28 ` Dominick Grift
2012-10-03 15:52 ` Dominick Grift
2012-10-03 18:16 ` Sven Vermeulen
2012-10-03 22:05   ` Daniel J Walsh
2012-10-04 11:01   ` Dominick Grift
2012-10-04 14:53     ` Daniel J Walsh
2012-10-04 15:24       ` Dominick Grift
2012-10-04 17:19         ` Daniel J Walsh
2012-10-04 17:39           ` Dominick Grift
2012-10-04 17:46             ` Dominick Grift
2012-10-04 19:04               ` Daniel J Walsh
2012-10-04 19:30                 ` Dominick Grift
2012-10-04 21:14                   ` Dominick Grift
2012-10-09 13:42                     ` Christopher J. PeBenito
2012-10-09 13:44         ` Christopher J. PeBenito
2012-10-09 13:52           ` Dominick Grift
2012-10-09 14:02             ` Christopher J. PeBenito [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=50742E71.1010601@tresys.com \
    --to=cpebenito@tresys.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.