All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] apps_wine.patch
Date: Mon, 12 Jul 2010 10:22:30 -0400	[thread overview]
Message-ID: <4C3B2526.4030706@redhat.com> (raw)
In-Reply-To: <4C334EEB.3090507@tresys.com>

On 07/06/2010 11:42 AM, Christopher J. PeBenito wrote:
> On 06/02/10 16:16, Daniel J Walsh wrote:
>> http://people.fedoraproject.org/~dwalsh/SELinux/F14/apps_wine.patch
>>
>> Picasa ships wine execs.
>>
>> wine changes fro domain_mmap_low
> 
> This last part confuses me.  I thought mmap_low was intrinsically
> required for wine.  Neglecting that question, there seems to be an error
> in the .if:
> 
It is only required by wine if you run old DOS 16 bit apps or badly
written ones. Newer Windows apps should not require this.
>> +    tunable_policy(`wine_mmap_zero_ignore',`
>> +        allow $1_wine_t self:memprotect mmap_zero;
>> +    ')
> 
> Shouldn't this be dontaudited?
> 
Yes.
> This doesn't seem to make sense.  Aren't the subject and object
> reversed?  Also it seems odd, since wine is running Windows programs,
> which wouldn't really inherit things from the Linux environment:
> 
>> +    # Unrestricted inheritance from the caller.
>> +    allow $2 wine_t:process { noatsecure siginh rlimitinh };
> 
> 

I have no idea why this was added.   I guess we can remove it and see if
it is rereported.

  reply	other threads:[~2010-07-12 14:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 20:16 [refpolicy] apps_wine.patch Daniel J Walsh
2010-07-06 15:42 ` Christopher J. PeBenito
2010-07-12 14:22   ` Daniel J Walsh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-26 22:44 Daniel J Walsh
2009-11-12 20:55 Daniel J Walsh
2010-02-19 14:18 ` Christopher J. PeBenito
2009-08-28 20:18 Daniel J Walsh
2009-05-21 15:11 Daniel J Walsh
2009-03-24 13:22 Daniel J Walsh
2009-03-05 16:19 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=4C3B2526.4030706@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.