All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC] Add support for the skype_t domain
Date: Wed, 3 Aug 2011 13:48:20 -0400	[thread overview]
Message-ID: <4E3989E4.3000906@tresys.com> (raw)
In-Reply-To: <4E395374.6040105@redhat.com>

On 08/03/11 09:56, Daniel J Walsh wrote:
> On 08/03/2011 09:42 AM, Sven Vermeulen wrote:
>> On Fri, Jul 29, 2011 at 08:59:33AM -0400, Christopher J. PeBenito
>> wrote:
>>> On 07/24/11 11:38, Sven Vermeulen wrote:
>>>> The skype application is a popular voice and video chat
>>>> application. This patch adds preliminary support for skype on
>>>> SELinux.
>> [...]
>>>> +userdom_manage_user_home_content_dirs(skype_t) 
>>>> +userdom_manage_user_home_content_files(skype_t)
>>>
>>> Is this really necessary since there is skype_home_t?
> 
>> Depends on the use case, but Skype can be used to send and receive
>> files, so skype_t needs to be able to manage the users' home
>> directory content.
> 
>> Not that I'm happy with that, but it seems to be how most
>> applications handle this. I personally prefer a specific type for
>> interacting with the "outside" world (user_download_t or so) and have
>> the apps be able to manage that type rather than user_home_t. But
>> that does make it more difficult to explain to users (not really
>> userfriendly).
> 
>> Thanks for the feedback (also on the other RFC mail)!
> 
> Can skype work fine without this ability?  I would think you could add a
> boolean and for most people who only do Video or phone calls would not
> need the ability to read/write user_home_t.

Agreed.  I'd prefer it this way, if possible.

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

  reply	other threads:[~2011-08-03 17:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-24 15:38 [refpolicy] [PATCH/RFC] Add support for the skype_t domain Sven Vermeulen
2011-07-29 12:59 ` Christopher J. PeBenito
2011-08-03 13:42   ` Sven Vermeulen
2011-08-03 13:56     ` Daniel J Walsh
2011-08-03 17:48       ` Christopher J. PeBenito [this message]
2011-08-03 14:04     ` Dominick Grift
2011-08-03 23:04       ` Russell Coker
2011-08-04  8:41         ` Dominick Grift
2011-08-04  9:00           ` Russell Coker
2011-08-04  9:34             ` Dominick Grift
2011-08-04 14:22               ` 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=4E3989E4.3000906@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.